enjo

>The 5% of the codebase the agent shouldn’t touch unsupervised.

This jumped off the page to me and it's an assumption that underlies everything else in the article. For the record I agree with the author that if it is true that 95% of the codebase should be unsupervised, the how layer does indeed become very small.

But my experience has given me little reason to believe that it's true. Code doesn't conveniently break in the 5% you choose to care about. Systems fail in seemingly random places very often in the seemingly uninteresting parts of the system. The macro and micro decisions that make code actually work have to be of high quality everywhere. They have to be fixable in the worst case by a human and that still very much requires a human to review nearly everything the agents generate.

As always there's a risk-management question here. You can choose to take on a lot of risk by increasing the amount of code that only agents touch. And maybe I am still too in the oughts with a belief that code should be secure, do what it says, and do it reliably. Turning over your code to unsupervised agents in such large quantities amps that risk level up to a place that I (at least) am not comfortable with it.

So ya I think the author is right in their model. Why, what, how is a great way to think about orgs. I agree that the output of the how layer has been pretty turbocharged and I agree that the how layer is going to shrink but I think I disagree with them by how much.

My wife’s grades are due tomorrow. She was in the middle of finishing exams when it happened. She can’t even access the exams to grade by hand. Total mess.

AWS was gutted by layoffs over the last couple of years. None of this is surprising.

Yep my experience has been pretty bad. As in Claude with Opus can rarely produce even compiling code in my particular project (a year old, mid-complexity one). This is with adhering to best practices including a robust Claude.md and detailed PRD's.

This is more or less my experience with Go right now.

For a bunch of reasons I want to avoid the standard React, Typescript, and Node stack but the sheer velocity that might enable from the LLM side might make it worth it.

Two axis globe is best globe.

It's Scala all over again.

I mean there are many distinct styles of American pizza. And Italy itself is home to several different distinct styles of pizza. Is Pizza al Taglio "authentic"? What about Sicilian Pizza? Is Pizza Fritta "authentic"?

>I do have to wonder whether it's really worth it to go through all this rigmarole to get the official Neapolitan pizza seal of approval.

In my neighborhood in Denver I have several Neapolitan pizza options. One is fully Vero certified. I go there often because it truly does give me the taste of Napoli from my childhood.

The best option, however, is recognizable as Neapolitan pizza but is much better than anything I have ever had in Italy (at least to my taste buds).

I feel like both really have their place and both restaurants have been around for quite awhile at this point so it seems to work for both.

That said I do appreciate the places that have are fully Vero certified because when I travel if I see that sticker in the window I know I am gonna have a pretty good pizza.

Yep but this time is different because it's going to completely displace what is left of the middle class and this time the people being fucked have six figures of college debt.

TP-Link comes with a healthy dose of worry about the Chinese governments surveillance practices tho.

I feel like we'll get a good feel for this if hiring domestic engineers picks back up without an influx of foreign folks who are not receiving the positive tax treatment.