duttish

We got those giant books here too.

Around me everything is at least hybrid, with nobody complaining if you want full time on-site. More and more companies are moving back to on-site full time.

50% office politics 30% stakeholder and expectations management 10% design/development

30% is surprising, did you dig into it at all? Sounds like a bunch of active polling or something?

They mentioned this on the podcast, the problem is that since they're development tools the networking stack is still scaled for a full rack with pretty beefy switches.

Either they need to support a whole second network stack with firmware etc which they don't want to do now, or a racklette would cost way too much and almost nobody would pay the price.

Hm, that doesn't make sense to me.

The difference between intent and implementation seems like a very common source of bugs?

If intent and implementation was the same thing programmers as a profession would have been left behind 20 years ago.

"Hi, this is AWS Support. Your backup disk usage is over limit. Please remove all backups or we'll need to close your account.

Feel free to reach out if you have any questions."

Hm, what guard rails are needed for agents that aren't needed for humans if you want to handle insider risk properly?

Yea this.

Agents doesn't cause new problems, they reveal existing weaknesses.

Proper working backups. Proper IAM setup. With agents things can go wrong so much faster, the margins for allowed systemic/tech debt are shrinking.

This has become my approach as well. Create a work tree per larger thing / batch of things and manually review everything in small commits, then squash merge the whole tree to keep the history manageable and clean.

Every time I stop reviewing the code from Claude I later find janky crap. Not every review finds janky crap, but often enough that I can't stop reviewing everything.

This is my disconnect with this kind of speed, how are they avoiding the janky crap? Or are they just accepting it and hoping it won't be too crappy or be found soon enough?

I don't have any insight into Anthropic but it seems like that's the case which is just depressing.

I have no clue where the author is working but...

We've lost 75% of the team over the last year.

We write code faster. It's not getting merged faster because we usually find something janky.

Decisions aren't made faster.

Understanding doesn't come faster.

Code doesn't have value. A well working system has value, the bottleneck is now between having code and having a working system, rather than producing the code.

Whenever I've tried skipping code review I've later found janky crap or weird decisions made.

Agents allow me to build cool stuff but atm they're far from good enough to not review the code.

Whenever I stop reviewing code I later find yanky shit or a small but important misunderstanding in the plan or...

Claude has let me build really cool things but so far I'm not letting it run on it's own.