One way hand coding is productive is it gives you detailed intimate knowledge of the code. We’ve all seen someone that really knows a system hear about a bug and say “Aha!” and take 5 minutes to pump out a fix. A well setup Claude Code, with good guardrails and feedback, could possibly do this (we’ve seen examples of it for sure). But it also might loop idiotically not finding the issue.
Can you link to any examples of Claude quickly debugging a codebase it didn't write using a nontechnical description of a bug from a real user?
Coding is when we're least productive
41–50 of 59 posts
Re: Coding is when we're least productive
#42Re: Coding is when we're least productive
#43I don't care how easy it is, I'm not fixing something worth millions when I won't see a penny of that. It's on the business to double check their shit.
Re: Coding is when we're least productive
#44Re: Coding is when we're least productive
#45The myriad of "nocode" aka i dont want to deal with the whole complexity solutions tells you what its really all about.
How do you get a caste todo its job when all they do is refuse the call to adventure, smear responsibility over hierarchy and then demand tools to shirk the job they refused todo in the first place?
Re: Coding is when we're least productive
#46Coding is when we carefully write down our solution to a problem. (Manager pushes paper, pen and a list of problems in front of you and demands, “Now write, just write! And fast!”)
And if you find yourself going in circles while you're typing in code, you probably didn't complete the plan phase.
Re: Coding is when we're least productive
#47E.W. Dijkstra: "Measuring programming progress by lines of code is like measuring aircraft building progress by weight". Personally, I think, much of the art of programming is to do as much as possible with as few lines of code as possible.
There’s more to it than that though. The solution using the least possible lines is often inscrutable and brittle. The art is in finding the right level of abstraction which can deliver the performance required while being sufficiently legible. Depending on the specific problem you have to weight your solution accordingly, if performance is critical you must often forfeit legibility. The art is in recognising and dea…
Re: Coding is when we're least productive
#48„Managers aim to maximise the amount of code their dev teams produce, and so they maximise the time devs spend writing code.„ Never seen that happen. Do not know anyone who experienced this. Where and who are those managers?
I will say this. After all the thinking and discussion is done, code is the means by which the desired value is realised, so if you're an engineer and you never write any at all there is a chance you might not be as involved in delivering that value as you might like to think. Plenty of situations where that's not true, of course, but it's definitely one of those things that can be a smell.
Re: Coding is when we're least productive
#49The problem is not with code, its with management having no real perception of the problemspace they inhabitate and how they damage and polute said space. The myriad of "nocode" aka i dont want to deal with the whole complexity solutions tells you what its really all about. How do you get a caste todo its job when all they do is refuse the call to adventure, smear responsibility over hierarchy and then demand tools t…
Re: Coding is when we're least productive
#50The problem is not with code, its with management having no real perception of the problemspace they inhabitate and how they damage and polute said space. The myriad of "nocode" aka i dont want to deal with the whole complexity solutions tells you what its really all about. How do you get a caste todo its job when all they do is refuse the call to adventure, smear responsibility over hierarchy and then demand tools t…
especially if you include the total refusal of that caste to take responsibility - e.g. compliance - hence looking for any possibility to outsource that, be it M$ or AWS or (now new kid on da blok) "AI"