Win win!

A robot civilization? Because last I checked, humans were passed off said biosphere.

Forever wars, the Patriot Act and a financial crises that took years to recover from under another president?

Also, don’t feed them to dogs especially small dogs.

Highly unlikely to be a problem but people die from water poisoning so…

One of those things is true…

If you constantly have to push back against the eager puppy jr dev who’s 1000% sure their vibe slop is prod ready and has proudly told the admiring crowd of stake holders it’s ready to go, wtf kind of life is that? Now the senior/lead is the bad guy and is in the no win scenario.

Yuck.

Reviewing 100 lines of Junior dev slop was bad enough. Now 1000 lines of misguided jr dev ai slop?

Ugh.

“If we build like Google, we become Google”

I don’t know why a small company would want Google’s engineering problems.

He links here as some kind of damning proof that ORMs are default bad.

https://openai.com/index/scaling-postgresql/

“It’s a poor craftsmen who blames their tools.”

My ORM rule of thumb: ORM for CRUD not Reports

If you are joining 12 tables for operational data, you have a design flaw. That’s a reporting query pattern.

Often temp tables, CTEs etc are needed as an immediate fix with redesign as a long term fix. The query planner simply can’t optimize that in a reasonable time or it’s beyond there scope if what it can optimize. Also their solution to “joining in memory” is common.

My DB query rule of thumb: If the query is hard for you to understand, it’s hard for the planner to understand.

Default to small fast simple queries and pipeline them together.

What did Bob ever ship that gives him any gravitas or authority in this area?

What a muddled bunch of gibberish.

Is the most non-sensical thing I've seen. So of course the junior dev parade thinks it's the gospel.

Had a terrible manger who would swear by this book but couldn't code his way out of a paper bag.

Feature, bug or emergent property?

I don’t think the distinction matters as much as the reality.

We’re being locked into using the AI tooling bc the code was generated with AI tooling.

These giant files of doom were being generated by humans anyway and were very hard to work with. With LLMs it’s at last manageable or feasible to edit, refactor etc.

I honestly think LLMs are going to save us from ourselves as the codebases became too large and “messy” for humans to comprehend. (Mono repos of doom)

On a personal level these giant files are abhorrent but that’s just personal taste and I don’t think any of the Martin Fowler refactor/cleanup stuff is going to matter at all anymore. Kinda sad on some level.

If one can easily swap in the next new js engine du jour…

Theater to keep Mad King Trump off their back.

This is inportant in DBs in general to avoid deadlocks by two requests taking locks in different order.

It's a recipe for deadlocks and even live locks.

That's a reason industry moved away from this. Bc when it works it's magic. But when the problems start it's pure hell.