News for hackers. Stuff that matters.
Re:Appearing productive in the workplace by groos on Wednesday May 06, 2026 @08:42PM (#48043979)
As I am continually amazed at how well Claude 4.7 deals with highly complicated C++ code, I am also becoming painfully aware of the developing situation mentioned in this article: I no longer completely understand the code it is editing, not because I'm incapable of doing it, but because I have not authored the changes. I am trading throughput for understanding, and, eventually, judgment.
Re:Appearing productive in the workplace by danaw on Thursday May 07, 2026 @01:36AM (#48045775)
nail on the head. the loss in understanding, learning and context is often not worth the increase in volume of output
Re:Appearing productive in the workplace by lowbloodsugar on Thursday May 07, 2026 @02:01AM (#48045953)
That’s entirely on you. You can take the time to understand it before moving on to the next task. I say this with sympathy and understanding.
Re:Appearing productive in the workplace by groos on Thursday May 07, 2026 @09:52AM (#48049482)
You missed the point - understanding comes from working through the code, not just reading it. This is nothing new: nobody has learned or done new mathematics or physics or whatever by just reading a textbook.
Re:Appearing productive in the workplace by lowbloodsugar on Thursday May 07, 2026 @11:39AM (#48050737)
Sure. But it’s a lot easier to learn nonlinear mathematics or quantum theory with a textbook than without. In this case you’re not learning about “what is a for loop”. You’re learning “why a OnceLock here rather than a RwLock”.

Many of us work on teams so we already have to deal with the majority of code being written by someone else. I’ve got code that’s more than a decade old, written by people I’ve never met.

Re:Appearing productive in the workplace by groos on Thursday May 07, 2026 @02:25PM (#48052930)
Again, note that I said "work through" and not "read". Reading code is shallow. Debugging it, modifying it, inserting diagnostic code, etc. is not.