Mofpofjis

A commit that was "co-authored-by" 6+ people and has three thousand lines of code: this is a total wreck of a development workflow. This feature should have been implemented with a series of about 20 patches. Awful.

quick, the address of a burn clinic

next level: use AI agents in their dating apps on both sides to decide if they want to hook up

> I make a wall with bricks, even if it will be covered with coating i will do my best to have regular joints and pacing.

Absolutely. This is at the core of it.

> Why would anyone rather read and fix someone else code rather than writing the code themselves?

Because their own review standards are low (so they find reviewing "easy"), and/or because they can't appreciate the emotional & mental fulfillment that coding provides.

Strongly agreed. And, your wording is excellent.

For me, the electric bike analogy works differently: it enables people to ride, regularly, who would not be able to do that with traditional bikes. That's totally fine. But electric bikes don't threaten to take away our normal bikes.

There are things that "modulate" this. Violating copyright is never right, of course, some questions are however scale, and purpose. Taking others' creative output, unlicensed, for large-scale commercial gain, is about the worst.

Agreed. Smartphones are portable, mobile computers that suck at every single aspect of being, and working as, a computer, except for mobility. They are not powerful, they are not general purpose, they are not ergonimic, they do not respect user freedom or privacy. Use such a mobile device only when you can't avoid it (i.e., when you are on the road -- when mobility is the single most important priority), and at no other time.

> I got into programming because I like programming, not because I like asking others to write code on my behalf and review what they come up with

oh finally someone else who didn't enter programming because, as 7-10 year old child, they were into SOLVING PRACTICAL PROBLEMS FOR PEOPLE.

> But the last fucking thing I want to do is delegate all the code writing to someone or something else

Thank God there is at least one other person that understands that the ratio between creative and reactive work is crucial for wellbeing at the job.

For crying out loud.

> but if I ever get to the point that I feel like I spend my entire day in virtual meetings with AI agents, then I'm changing careers

so am I.

> but at least I guess I got a couple of good decades out of it

Thanks for this perspective. Yes, at least we've got our memories, and the code locations and commits we recall from memory, from a distance of 10 or more years.

>. If this is what the job turns into, I'll have to find something else to do with my remaining years

Me too.

OMG I didn't notice. Way to burn down a huge amount of respect stemming from past cryptography work in just one blog post.

> I am finding the most destructive aspect of LLM assistance to be the loss of flow state.

Finally someone else mentions Flow!

Wrong.

I do pay my general contractor for the unseen quality that goes into the structure of my home. Programs should be built the same way.

"regular" code review is indeed a total theater, a travesty, a farce.

Real, meticulous code review takes absolutely forever.

then you are a terribly sloppy reviewer