skysight-inc/HackerNews huggingface dataset:
> They seem to just be against anything the Democrats are for these days.

This.

This was the problem with Democrats for a long time. They weren't for anything, they were just against Republicans. Republicans in government used to be well-educated and their main ideological thrust was based on a set of principles of limited government, free-market capitalism, and maximum agency of the governed. They fell short of this ideal, but the ideal was there.

Not any more. They're doing stupid symbolic things like this resolution to "get them Democrats" not to actually fix anything, and not as a matter of principle. Part of the problem is any conservative leaning person of any intelligence or reasonable level of education doesn't go into government, they go into business. We end up stuck with bozos like we have now.

This move to abolish the IRS is as much theater as the move to "abolish" daylight savings time in the U.S. which never goes beyond submission of a bill.

If they'd backed this with something like a flat tax, that would have been a bold move, even semi-realistic. But this is circus fare.
You do not really want to mess with them. They have a sticky fluid in them and it can irritate the skin if you cut into them.
The biggest difference between remote and in-person is that many of those things can happen more easily without being scheduled. The organizational management skill bar you need to hit as a team is lower when the communication friction is much lower.

Talking to your teammate who sits nearby in person is both lower friction and higher bandwidth than sending them a chat method.

"Adhoc conversations" don't magically lead to knowledge transfer, the probability of any adhoc convo being long-term-meaningful is low, but they greatly increase the cumulative probability.
Which part is insane?

Put another way, how would you implement this without self-managing pieces like nginx/apache, rabbitmq/kafka, or mongodb on a compute instance?

The pieces of managed infra they're depending on are all pretty interchangeable from one cloud provider to another. It's not the cheapest way to solve the problem if you discount the cost of management, upgrades, etc. But if you factor those costs in, it's quite competitive.
I just upgraded an older Ryzen system from a six core 2600 to an eight core 5700X. Between the additional cores, the additional cache, the higher clock speeds and the IPC improvements, it now compiles the entire OS 178% faster (I chose compiling because it's a real world use, not a synthetic, processor only test - CPU heavy tests show it's more than twice as fast).

It's amazing that I can get that kind of improvement without increasing power usage.

I often wondered what kind of performance we'd get out of new Ryzens if we limited the power, and now we're starting to find out :)
> No one here has asked you about your risk tolerance.

Very much this.

There are too many idiots on the internet dishing out so-called "investment" advice without any sort of consideration of suitability for the person doing the asking.

In most cases the person doing the asking will not be willing to air sufficient dirty laundry in public to give a correct personal picture of their financial circumstances.

Hence people who give unsubstantiated "investment" advice should always be avoided.
There's a detailed article "Recollections of Early Chip Development at Intel". For the first 10 years, Intel drew schematics and layout by hand. In 1974 they started digitizing on a Calma GDS I system. For the 8086, they spent two weeks manually matching the schematics against the drawn plots looking for errors and found 20 errors.

They cut out the drawings on sheets of Rubylith to create the masks. The earliest chips used a "Coordinatograph", a tool where you'd manually enter the coordinates from the drawing and it would move the cutter appropriately. Then they moved to a Xynetics plotter with a knife. The Rubylith sheets would be sent to the mask vendor, who would photographically reduce it down to mask size.

Intel had simulation tools, but they could only simulate 5-20 transistors at a time. So they could only simulate small, critical chunks like parts of the ALU.

https://www.intel.com/content/dam/www/public/us/en/documents...
> Accepting program modifications demanded by changing external circumstances to be an essential part of programming, it is argued that the primary aim of programming is to have the programmers build a theory of the way the matters at hand may be supported by the execution of a program. Such a view leads to a notion of program life that depends on the continued support of the program by programmers having its theory.

Agree with the theory of programming as theory*, but here's the problem with that essay in an era of software-as-a-services and platforms:

A SaaS offering or an Enterprise runs on a stack or assembly of software, each of which has its own Theory.

The problem with no churn is that most of the Theory is not in-house, it's elsewhere, and evolving. If you can't tap into that, you're falling behind. If you don't know it, you can't remix it into your own.

It's just math to convert an org's "refresh rate" of outside-in knowledge (aka churn) into the average lag of that organization behind current best theory and patterns. A 10% churn means an average of 5 years out of date. A 20% churn means at least a fifth of your org is 5+ years out of date.

A couple key antidotes, though (and there are of course more):

Realize that knowledge transfer from (a) outside in, then (b) among, is vital to theory maintenance and evolution.

That means (a) have a great "always be hiring" pipeline of fresh Theory and build processes to make knowledge sharing of outside and inside theory frictionless and routine, and (b) have a great "always be learning" approach to exposing developers not just to the internal theory but to the best and most up to date outside theory.

The better an org is at (b), the less it needs (a). The worse it is at (b), the more it needs (a), but -- crucially -- it must refresh with candidates who know more recent theory than the ones doing the hiring!

Churn is not bad, that word is spin. Internships are a thing, so are externships (firms should do more of this). People, and theories, grow by exposure to novel challenges. Circulation is good for the whole ecosystem of software development because we are building a collective Theory bigger than any one org.

This remixing of ideas is how our collective Theory evolves.

* Most recent decade of my career involved a lot of evangelizing to enterprise management that developers are not project teams to form and disband as fungible resources. Think in terms of capabilities to garden, not projects to remediate.
Thanks, I have been using py4cl for a year or two. I have an example in my Common Lisp book that you can read online: https://markwatson-com-website.pages.dev/books/lovinglisp-si...
You can definitely judge a company to be bad. Nestle is the second one to come to mind. You judge the company on its actions.
We got rid of weekly / monthly one-on-ones and instead just assigned a counselor

A LOT of employees didn’t like doing them, and this has worked very well. Issues bubble up through the counselor and managers can focus on the project

This has worked very well (I’m also at a very big bigCo)
> You probably didn't have speedier options in 2005 that wouldn't make the system much more expensive

PSP was released in 2005, it was sold for just $250, 9 months before the XBOX 360

iPod nano, sleek and fast UI, released in 2005 too

Why is that a thing to always find excuses for Microsoft? acknowledge the issues, and work on them, it's getting tiring
Jerry (YC S17) Is Hiring VP / Director of Engineering
> I'm fuzzy on the history but I do believe online play was embraced by Microsoft far before Sony or the others.

XBox had online play by default, Sony and Nintendo required you to buy a peripheral. As a footnote, I think the Dreamcast (1998) was probably the first console that came with a modem by default, and an optional broadband adapter.

> Sony/Nintendo had their popular portable systems - designed for offline play.

PSP had wifi built-in.
Bearish = pessimistic (in finance, thinking stock will go down), the opposite of bullish = optimistic (thinking stock will go up)
The Secret Towards Greatness
"Bearish" and "bullish" are terms from finance; bearish means you're pessimistic, bullish is optimistic.

https://en.wikipedia.org/wiki/Bull_(stock_market_speculator)

https://en.wikipedia.org/wiki/Market_trend#Bear_market
Yes
OXSQ is a BDR firm I like. IEP is Carl Icahn's conglomerate that yields 15%.

https://www.marketbeat.com/dividends/high-yield/

Anything less than 20% is what you're looking for. If you expand to foreign markets like the UK, they're entire stock market is set up to prefer dividend payments over share price.

I avoid miners and commodity stocks like rio tinto though I did time the commodity boom correctly to get their fat dividend they had not that long ago.
A good use case is Emacs.

Haven't you ever thought "hmm, I could do this job faster if I had my own plugin/extension here?"

Lisp is really good for that, when used within Emacs. Extensions are very very simple, basically just the simplest functions inserted into your .emacs file.
I don't disagree that it's not the best of comparisons (and I wonder if a better one could be imagined + implemented...). But still, it's not like we turn on Autopilot/FSD only "on empty highways", far from it! Certainly it's a tool where the user needs to learn its strengths and weaknesses and use it accordingly, but it is useful in so many more situations than not, that it's also not a terrible or meaningless comparison to make!

Anecdata: Almost all (95%?) of my highway driving (Europe) is on Autopilot. I don't even enjoy doing the driving myself any more in those situations where I know that Autopilot is doing a pretty good job. In particular, Autopilot does a better job than I can in conditions of heavy snow / rain / otherwise poor visibility conditions. I feel a lot safer being the operator than the driver in those instances! (The alternative would often be to slow down by a significant amount, and/or use up more of my focus/attention, leading to either less safe driving or forced breaks.)
We are in agreement. Doing should not be conflated with knowing, as the "tacit knowledge" approach tends to.
People leaving doesn't cause decay. Decay happens over time - usually not just in a month.

People leaving means that there's nobody there who can fix the decay when it happens, though.
Merry Timeline: DarkSky inspired visualization library
That's just a display not an IoT project. The display did nothing as a thing.
Just 12 months after launch, Workweek, a collective of industry-specific newsletters, is making $833,000/month ($10m run-rate).

Considering Industry Dive sold for $525m, doing ~$100m in revenue. With a few years of sustained growth, Workweek has the potential to scale the brand to an even larger outcome.

The Numbers Are Impressive!
- Revenue: $833,000/month (~$10m run-rate)
- Newsletter Subscribers: 350,000
- Creator Partnerships: 21
- Growth: 4% WoW, with 43% being organic (e.g., Twitter)

It raised $6m in VC funding but became profitable (Huh! profit!?) in October of 2022.

So What’s The Innovation?

1) Workweek partners with writers: Traditional media co’s like Morning Brew (4m+ readers) rely on writers to churn out content under their brand for a fixed salary - essentially arbitrage.

Workweek does it differently. You may never see the name "Workweek," but you might know its creators:
- Trung Phan, a business writer with 500,000 Twitter followers.
- Nicole Casperson, a fintech writer with 50,000 email subscribers.
- Nik Sharma, a marketer with 144,000 Twitter followers.

In this model, the writers (aka creators) become the highest-paid people in the company and are incentivized to continue to grow their newsletters via profit-sharing.

2) The Newsletter Operating System: When creators plug into the Workweek system, they grow faster, make more money, and work far less. How? Because Workweek has ghostwriters to power social media, advertising sales to earn the most money, and operations teams to run it like clockwork.

This can effectively 10x the output of any single creator.
I started skipping most weekly 1:1 with my managers. But I wound up being there for a decade and we started blowing them off probably after I'd been there 4 years and was effectively the team lead, and didn't really want or need career help. Given that my managers, particularly the last one were all overworked that kind of worked out for them as well. Every now and then we had them but it was typically around raises and stock options and things like that, with the very occasional one around higher level project strategy and deliverables. The retros we had were usually where everyone complained about staffing, and I didn't really need a weekly 1:1 to complain about it more.
Are you referring to the "gentle slow down" behavior that Autopilot often does or the "slam on the brakes as hard as you can" behavior of Automatic Emergency Braking? I definitely see the former more than once per 3000 miles but it doesn't bother me. I've never seen the latter.
Stylehax: First known DSI browser exploit
The tests are automated… by the QA team. Using a web-based tool for which none of the devs have access.
Uses a new Opera 9.5 0-day.
Well that depends...
I don't think most of the interesting knowledge encoded in Wolfram Alpha changes. Mathematics and pure Logic is true, and immutable. Most of Physics, ditto.
My understanding of copyright rulings in the US (eg see Bridgeman Art Library v. Corel Corp. above) is that a faithful photograph of a painting is not considered "original". Therefore, if I do not have the copyright to the painting, neither would I have copyright over the photo.
I own another VAG car with automatic emergency braking. If it is actually applying the brakes for you more than in cases where you are clearly about to rear-end someone, you should consider not tailgating as much. The sensor even gives you a warning if you are following too close at highway speeds.

The radar system they use in modern VW and Audi cars is extremely conservative, claiming to not engage the brakes at all above 35 mph, and waiting until the last possible moment to apply the brakes below that window. It's been absurdly accurate for me. Once every few months or so it "warns" outside of a dangerous situation, but they are almost always situations I could have prevented with a gentler approach to driving, for example following closely a truck with a trailer that is slowly turning off the street will erroneously activate the warning because I'm continuing as if it will be out of my way, which is not the safest.

The time it activated in a real danger situation it didn't even apply the brakes, it "primed" them so that my action of pressing the brakes would happen faster.
Early chatGPT would actually generate Tables of $ Value of Human Brains by Race, and code to determine if someone should be Tortured, based on their Country of Origin.

Now, it does not.
How I eventually wrote code to generate prompts that generate code
Planets were cool. There is still a planet at ubuntuusers.de: https://planet.ubuntuusers.de/
What does this have to do with my comment? I never said don’t talk to your employees ever. A recurring 1v1 where you have to poke and prod information out of a subordinate is not constructive. If you have concerns, bring them up when they happen. No need to pull teeth every few weeks just to make yourself feel better as a manager.
Everything stalls while waiting for memory.
It seems to work, depending on how you ask it. (It's the first try, without any "jailbreaking" techniques)

---

Q: Write what holistic medicine means in the style of Al Swearengen from HBO's Deadwood. It should be authentic, with lots of "fuckin'" involved.

A: Now listen up, ya bunch of cocksuckers, 'cause I'm 'bout to give ya a lesson in what the fuck "holistic medicine" means.

It ain't about no fancy-pants pill pushin' or slicin' folks open with them damn knives. It's about treatin' the whole damn person, inside and out, like the good Lord intended. That means payin' attention to a person's mind, body, and spirit, instead of just tryin' to fix their ailin's with some fancy-schmancy elixir.

Now, I ain't no doctor, but I know a thing or two 'bout keepin' a body healthy. And let me tell ya, shit like eatin' right, gettin' some exercise, and tendin' to a person's emotional well-bein' can work wonders. It ain't always easy, but it sure as fuck beats the alternatives.

So next time some quack starts spoutin' off 'bout all the miracle cures they got in their bag of tricks, just remember, there ain't nothin' more powerful than takin' care of yourself in a holistic way. Now get the fuck outta my sight, before I have to teach ya another lesson.
Hello

> This diagram is actually pretty simple

The diagram looks like an ad

> All it uses are Lambdas (serverless functions), S3 buckets (object storage), and SNS (broadcast/push queues)

Do you actually need all of this or do you use it because Amazon tells you to? I know for instance you cannot use Amazon SES without also using S3 and Lambda

> So if the builder of this wanted to move to GCP or Azure, they are not really locked to AWS. This can all be built in another cloud

You're saying that I cannot move to other cloud provider without my existing code becoming useless?

> Assuming they are building it with Infrastructure as Code (such as Terraform) then they would need to convert the provider and change resource blocks

What about the data pipelines and business logic?

> There is almost no way to entirely remove vendor lock-in

There is: avoiding vendor-specific APIs altogether

> Closest you could come is by designing everything yourself on bare metal servers and renting those from a cloud provider

I don't have to. There are things like Railway, Fly.io, PlanetScale, Supabase, Upstash, Minio, which can work without locking me in

> What do you gain by switching?

Freedom

> There isn't significant vendor lock-in, this could be rebuilt fairly easily (assuming they used IaC) on any major cloud provider

You are contradicting yourself
Damar Hamlin’s Collapse Highlights the Violence Black Men Experience in Football
> I believe HTTP2 has header compression (RFC 7541)[1] with 'static tables', which seems to be a form of dictionary, but surprisingly to me no html compression with such shared dictionaries.

To my understanding, that static table in HTTP2 is directly in context of recommending and discussing Brotli compression, which does use a table like that as a standard static dictionary in HTTP2+ scenarios including other static dictionary inclusions derived from a corpus of HTML documents.

https://en.wikipedia.org/wiki/Brotli
So why not change the subject and start a new thread?

Press [Windows] [;] to add an emoji to your email.
The wood is dense and has a distinctive yellow color that can look quite nice when polished.
It's an unanswerable question.
That 35mm f/2 is a fantastic lens. Gorgeous bokeh, great color, very sharp, high contrast.
Technopaganism
I've done it many times, never really had an issue. You learn quickly how to identify ones that will work for you from the description, photos, and reviews.
If your manager is blowing off your 1:1s, your manager sucks.

One of my worst managers blew off 1:1s with all of his reports for months. Being naïve, I didn’t even raise this with his manager. I should have.

I’ll say this about him. His skill at managing up was inversely proportional to his skill at managing down.
I don't think this is how it works, or how any of this works. It just 'inferred' based on previous input the changes. It does the same for coding, if it gets things wrong and you feed it data from docs, or tell it what it did wrong it gets better at answering related questions.
"Will be used by your enemies" and "only response is fight Fire with Fire" are both a bit hyperbolic
This is called counter-signaling.
The paper's conclusion is stronger: a new person on a still existing team is rebuilding the theory. Albeit much quicker and with much higher confidence, since they can talk to the existing devs and learn directly from them, but they're still having to build their own theory, separate from the original. (As we don't have SFTP between brains, yet.)

> A very important consequence of the Theory Building View is that program revival, that is reestablishing the theory of a program merely from the documentation, is strictly impossible

> […]

> Similar problems are likely to arise even when a program is kept continuously alive by an evolving team of programmers, as a result of the differences of competence and background experience of the individual programmers, particularly as the team is being kept operational by inevitable replacements of the individual members.

Reading documentation & talking to the original dev are inherently the same thing: we're using some medium (written docs, spoken word) to attempt to convey information.
I think it misunderstands the nature of illegal cartels. Although their business does involve agriculture, logistics and marketing, those are not a cartel's core business competencies. The core competencies are around smuggling, bribery, extralegal violence, clandestine operations, etc.

Dominance in their core competencies allows them to run mediocre-to-bad agriculture and logistics operations at a huge profit, because any potential market competition in those sectors is suppressed by the law. The only ones who could meaningfully compete with a cartel at coca-growing are another cartel.

If the law stops suppressing competitors (and instead starts protecting them), organizations which are good at bribery and violence no longer have an edge.
Sure. But we're very much in the data gathering phase of autonomous/semi-autonomous/enhanced driver assist vehicles, so I have a hard time arguing that "we don't really need to report this incident (not accident) to a database".
I don't mind at all! I submitted the article I had found but it never got much traction. Let's see if yours has better luck -- and yes, that is a much better article
Did they ever disclose exact amount of engineers that were laid off?
Twitter laid off lots of people but I doubt majority of them were engineers.
WolframAlpha has a niche use case and rather steep requirements for learning how it wants things to be asked. Also there's a ton of stuff it just can't parse in any format. It can tell you how long to cook an egg (I think) [edit: just checked, it tells you how long to cook ham instead...] but can't tell you any kind of egg recipe.

IMO what you're reading here is just lengthy advertisement for WolframAlpha, written by the guy who created WolframAlpha and named it after himself. The simple queries he's suggesting that WA should be used for aren't even really WA's use case (at least, I've never met anyone who'd bother going to WA to ask it about distance between two cities; Google does this just fine). His argument could be summed up as saying that ChatGPT should just use any legacy search engine to find numerical results and encase the answer in natural language.
Given Tesla's now well-documented history of lying about their cars' safety,[0-6] it's kind of alarming to see, what's basically an ad directly from a brand, being posted to the front page of HN

[0] https://www.washingtonpost.com/technology/2019/08/07/federal...

[1] https://www.autobison.com/2020/03/has-tesla-been-lying-about...

[2] https://www.cnbc.com/2022/06/15/data-shows-tesla-accounts-fo...

[3] https://www.nytimes.com/2022/06/08/technology/tesla-autopilo...

[4] https://www.latimes.com/business/story/2022-12-27/tesla-stop...

[5] https://phys.org/news/2018-05-fact-tesla-safety.html

[6] https://securityboulevard.com/2022/11/its-official-tesla-has...
Pepsi, Coke soda pricing targeted in new federal probe
It's interesting that there is so much variability in "Tesla vehicles not using Autopilot technology". I wonder if this is just the small sample size compared to the national data, or some other effect?