As an incident responder who makes a killing in emergency contracts:

Yes, absolutely do this.

No, this is quite backwards. I find myself reading code more, to gain context and build the theory for the feature I'm working on. The time it takes to write the code is now trivial compared to designing a good idea. Reading/thinking about code absolutely dominates now that writing code is cheap.

2026 is the year I stop reading blogs with headers like “The big unlock:”

It is rude to share AI written text for others to read. You are violating a social norm that has existed implicitly forever, that you invested at least as much effort in producing some text as you are asking me to put in to reading it

Yeah I’m still going to read AND write code thanks.

> In software, the things that matter are durable artifacts: diffs, commits, PR conversations, failing tests, logs, benchmarks, small design notes, repro scripts, traces. That’s what you actually reason with.

No, the author utterly misses the point. What matters is the final product that the end users see. Everything in the list above are artifacts of a dev process that truly doesn't mean squat to the end users. Those were all developed to help human coders.

If you truly believe AI is the way forward, and you believe that people are going to move out of the loop, then nothing in that list matters for the AI-driven future. That is actually the list of tools that needs to be thrown in the garbage and replaced by something new that helps AI perform its function.

100% AI written according to Pangram, damn.

Get this ai writing slop outta here. People have zero shame anymore.

I wish there was a way to graffiti a website.

Well, stop reading AI generated code maybe ;)