Agree with this tactic, very useful when working in a team. I use a --dry-run=false approach.

Capital, both social and economic.

Also data, see https://news.ycombinator.com/item?id=46637328

"... how much ram has the system" is a typo or an ESL mistake, so not an LLM.

This is just for the web interface, the API is staying for now.

IME 5.2-codex (high) is not as good as Opus 4.5, xhigh is equivalent but also consumes quota at a higher rate (much like Opus).

In the future?

I think of it this way:

Is your goal for the software you write to need constant intervention, or would you say you'd aim for it to run smoothly with few bugs?

The team is akin to a piece of software architecture, only much more complex and comprised (partially) of humans.

You want someone to build that team and then have the team up and running, delivering value. When it breaks, or you want it to do new/different things, you need someone to step in to fix it or change it.

The fallacy there is that I am not merely "building a team," I am managing. Managing is a live, interactive skill that involves certain services. A perfect team still needs management to help create the environment in which that team can effectively operate.

I saw a wonderful interview with a former commander of an aircraft carrier. (https://www.youtube.com/watch?v=b9rGATwZRr0) Rear Admiral Mike "Nasty" Manazir speaks of his main job as being clearing away obstacles that no one underneath him could clear. That's a service that no "self-managing team" can do for itself. A good manager also serves as a focus for the strategy, and deals with conflicts that would otherwise become impasses.

They are basically the same, long black is water with espresso poured on top, americano is espresso with water poured on top.

Assuming that your observation is true, I would guess the average age of HNers has increased YoY, which is likely to have something to do with it.

Oh my god, I didn't even get to the bottom, I thought you were being hyperbolic with that quote. Insane.