This is the best response to the article, IMO. We've kept our tech stack down, and lean heavily on postgres in a lot of cases. But having Redis able to handle scale independently of postgres has been a life saver, and saved us a lot of money vs what kind of postgres instance we'd need to match what it's doing.

Small scale, small app, You Just Need Postgres is on point. Funneling all of your scaling issues into Postgres, which isn't always the easiest to scale horizontally, can start to be a problem.

> I see Europe eventually coming to this same conclusion when enough damage has been done.

I'm curious about this sentence -- to what are you referring, and where specifically in Europe?

Portugal decriminalize d all drugs a little while ago

And they have very low drug mortality rates. Opiates are prescribed _way_ less than in the US. This really feels like a strawman comparison.

Notice the word „decriminalize“, not „legalize“. It’s about not throwing people already struggling with addiction in jail but rather offering safe alternatives (counseling, safer use, etc.).

The government‘s not passing out drugs in the street, like US media likes to suggest.

Nobody is writing a "project structure" section by hand, and listing out the directory structure with _every file_.

on that one i'm guilty, not gonna lie

I agree in your basic framing but not your conclusion. Met plenty of do-ers before thinkers that are self-aware enough to also maintain software longterm.

Is the Next.js API surface worth reimplementing?

It's not a point and click code machine, but it's laughably wrong to say they just churn out laughably wrong code.

Latest developer surveys (StackOverflow, DORA, DX, Pragmatic Engineer, etc.) show AI adoption up to 85 - 90%. Can you incorporate that into the venn diagram? ;-)

minor correction: they say AI produces code that is 'mostly' amazing.

You’re saying that AI is already good enough to replace 50% of developers. Sounds like you agree it will be very important.

He's saying the good half of developers have to deal with the increased slop output of the bad half. Probably will be overwhelmed by it, in the end.

It _can_ produce slop if people stop thinking. I've also seen it do just fine, when people know when, where and how to use it. That's the part that frightens me, not the code it makes itself.

I will have to bring out the Venn diagram.

Go ahead!

Stopped using autopilot because of the phantom braking.

It's also recently gotten much worse at lane departure sensing, often confused by snow or slightly faded road markers. Not pleasant to have the alarms go off while calmly and safely driving.

My Tesla can't even tell if it should turn the wipers on consistently or correctly. Let alone drive in the rain.

Seriously. Why do people think a company that can't do automatic wipers could possibly do automatic driving?

The same people that seriously thought we’d have a mars base by now.

A feature that is bulletproof in other cars with a very boring and industry standard sensor (it's not even expensive), while Tesla insisted they could do it with just normal cameras.

Do we know that it needs 10 chips to run the model? Or are the servers for the API and chatbot just specced with 10 boards to distribute user load?

If you etch the bits into silicon, you then have to accommodate the bits by physical area, which is the transistor density for whatever modern process they use. This will give you a lower bound for the size of the wafers.

Been incredibly happy with the speed, featureset, and pace of new (good) features in Linear. Our team has adopted it quite happily and it gets a ton of good use. Can fully recommend.