zlacker

[return to "Tldraw pauses external contributions due to AI slop"]
1. sbonda+p5[view] [source] 2026-01-16 00:15:31
>>pranav+(OP)
Seems like reading the code is now the real work. AI writes PRs instantly but reviewing them still takes time. Everything flipped. Expect more projects to follow - maintainers can just use ai themselves without needing external contributions.
◧◩
2. bigstr+ci[view] [source] 2026-01-16 02:05:59
>>sbonda+p5
Understanding (not necessarily reading) always was the real work. AI makes people less productive because it's speeding up the thing that wasn't hard (generating code), while generating additional burden on the thing that was hard (understanding the code).
◧◩◪
3. corndo+2n[view] [source] 2026-01-16 02:54:53
>>bigstr+ci
There are many cases in which I already understand the code before it is written. In these cases AI writing the code is pure gain. I do not need to spend 30 minutes learning how to hold the bazel rule. I do not need to spend 30 minutes to write client boilerplate. List goes on. All broad claims about AI's effects on productivity have counterexamples. It is situational. I think most competent engineers quietly using AI understand this.
◧◩◪◨
4. em-bee+lS[view] [source] 2026-01-16 08:44:34
>>corndo+2n
In these cases AI writing the code is pure gain.

no, it isn't. unless the generated code is just a few lines long, and all you are doing is effectively autocompletion, you have to go through the generated code with a fine toothed comb to be sure it actually does what you think it should do and there are no typos. if you don't, you are fooling yourself.

◧◩◪◨⬒
5. pixl97+dj2[view] [source] 2026-01-16 18:24:24
>>em-bee+lS
> with a fine toothed comb to be sure it actually does what you think it should do and there are no typos. if you don't, you are fooling yourself

so the exact same thing you should be doing in code reviews anyway?

◧◩◪◨⬒⬓
6. em-bee+Q34[view] [source] 2026-01-17 09:35:25
>>pixl97+dj2
kind of, except that when i review a code submission to my project i can eventually learn to trust the submitter, once i realize they write good code. a code review is to develop that trust. AI code should never earn that trust, and any code review should always be treated like it it is from a first time submitter that i have never met before. the risk is that does not happen, and that we believe AI code submissions will develop like those of a real human. they won't. we'll develop a false sense of security, a false sense of trust. instead we should always be on guard.

and as i wrote in my other comment, reviewing the code of a junior developer includes the satisfaction of helping that developer grow through my feedback. AI will never grow. there is no satisfaction in reviewing its code. instead it feels like a sisyphusian task, because the AI will make the same mistakes over and over again, and make mistakes a human would be very unlikely to make. unlike human code with AI code you have to expect the unexpected.

[go to top]