In the USA at least, people in the normal cars aren't "sharing their experiences". They're playing garbage music from their iPhone speakers (technically not allowed - happens anyway), trying to subdue their giggling/crying/screaming children, loudly conversing amongst themselves, etc. It's a zoo.

Not trying to pick apart your post, I liked reading it in general.

> The diagram below shows the rule: within each business domain (e.g. App Settings), code can only depend “forward” through a fixed set of layers (Types → Config → Repo → Service → Runtime → UI). Cross-cutting concerns (auth, connectors, telemetry, feature flags) enter through a single explicit interface: Providers.

This sounds so much like CQRS/hexagonal/DDD/other stuff. This is like the stuff that real world software teams actually struggle to execute on. This is the stuff people want solved. I don't think anyone doubts that if you can nail some sort of rigid, well-defined architecture and tooling workflow, agents can fly on filling in implementation. But it's the first part that needs solving.

You've never tried to compile NextJS slop, have you? It absolutely can take that much. All those junkdevs have 64GB in their MBPs for a reason. NodeJS max heap is now dynamic because of this.

Have you ever run a business?

My total lifetime "ate it" figure is only $2k, and even that one the client kind of eventually offered to pay, but I just let it be because I wanted to put as much distance between myself and them for other reasons.

Best advice in the article? "Trust your gut". If something feels vaguely off, I walk away immediately. I can see those non-paying incubators coming a mile away. Biggest indicator beyond gut: do they have existing contractors who seem happy? Ask them pointblank if they're getting paid. Easy as that. And of course, if they are paying you, but then stop paying you, or delay paying you, then stop work immediately.

Agree, YC founders are the worst type of person.

Employment?

Managers understand that metrics are meaningless. The idea is to have something to point at to scare engineers into jumping higher.

Prescribed workflows apply solutions from the wrong direction.

Determine what's impeding your organization, devise a solution.

The last guy I encountered who evangelized something like this had smart frames and a Lovecraft anthology prominently perched in the background of his Zoom shot.

In my direct experience, this isn't true if you're running something even vaguely mission-critical for your customers. Your customer's workers just know that they can't do their job for the day, and your customer's management just knows that the solution they shepherded through their organization is failing.