3 ms·
If you make a working and functional bad code, and put it on maintenance mode, it can keep churning for decades with no major issues. Everything depends on con
by tokioyoyo 7mo ago
If you make a working and functional bad code, and put it on maintenance mode, it can keep churning for decades with no major issues.
Everything depends on context. Most code written by humans is indeed, garbage.
- lucketone 7mo agoI define maintenance mode as: given over to different team, so not my problem anymore.
- bsder 7mo ago> Most code written by humans is indeed, garbage. I think that this is the problem, actually. It's similar to writing. Most people suck at writing so badly that the LLM/AI writing is almost always better when writing is "output". Code is similar. Most programmers suck at programming so badly that LLM/AI production IS better than 90+% (possibly 99%+). Remember, a huge number of programmers couldn't pass FizzBuzz. So, if you demand "output", Claude is probably better than most of your (especially enterprise) programming team. The problem is that the Claude usage flood is simply identifying the fact that things that work do so because there is a competent human somewhere in the review pipeline who has been rejecting the vast majority of "output" from your programming team. And he is now overwhelmed.
- thesz 7mo ago> Most programmers suck at programming so badly that LLM/AI production IS better than 90+% (possibly 99%+). How do you know?
- bsder 7mo agoBecause of just how many programmersI've interviewed who can't pass FizzBuzz? I also taught upper level CS and my first assignment was always "You have 10 days. Here is a 10 line program on this sheet of paper. Type it in, check it into source control, and make the automated tests go green. Warning: start today." 1/3 of the class couldn't finish that task and would drop.