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.
> 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.
Yes, absolutely do this.
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.