I'm sure this exact topic has been argued hundreds of times already on HN, but I think I have a new "possibly agreeable to both sides" perspective on this after having lost man-years to retired corporate code aka "FAIAP, throwaway code"
replyLet LLMs write the corpo code, as it will be unlikely to still be running in 5-10 years. Frontier AI is already at the point where it writes fewer bugs per LOC than humans. By a lot.
Go ahead and do your bespoke coding on your side-project loves and core libraries... The stuff that will last, anyway.
But if you're working for a corpo and still doing bespoke... That's... not gonna last, I'm afraid. Well, either you remaining there, or that, as it were.
It's still the same thing, you can ask it to do a full on report give explanation and details be thorough and then go do something else, another task a lunch break whatever and it will be done when you're back
reply> another task a lunch break whatever and it will be done when you're back
replyAt 5 tokens per second and unknown prompt processing speed, you may need a very extra long lunch break depending on your codebase.
How do you maintain a flow state during a lunch break? I'm looping with Claude on a scale of minutes. While you're waiting, I'm iterating.
replyThis is like comparing a hammer to a screwdriver and feeling smug because you can hammer nails faster than someone else can drive screws.
replyThese are fundamentally different tools for entirely different applications. They only look similar to people who don't understand the tools or their purpose.
deleted
reply