Comment by bawolff
1 day ago
I think part of it though is that LLMs (especially in novice hands) create code that is more difficult to review and has subtler bugs. Code review is (for many) the least fun part of programming.
Like imagine if your hobby was cooking, but you hated the cleanup. If you buy a robot that automates the fun part at the cost of making twice the mess, that is not a good trade off no matter how many extra cookies you end up with.
Or imagine a club where everyone cooks together and then cleans dishes together. Then one day some people show up at a club meeting with cooking robots that create 10x the amount of dirty dishes and then don’t help clean up at all. I bet the other members wouldn’t be happy, even if the robots mostly cooked decent food.
Then robots begin cleaning dishes too. And the other members aren't happy, because what's the point, we are here not for the dishes, but for the process.
It is probably a good trade off if you sell cookies or if you vastly prefer eating cookies to making cookies.
I think that also hits what you see universally with every AI product trying to pass worse results off as a benefit: if you’re a business, the prospect of cutting your cost per cookie is really attractive as long as the decline in quality doesn’t cause people to stop buying and that’s going to get the focus of everyone who sees the financial reports more than they talk with customers. Anyone who’s going it because they care about cookies or take pride in your craft will have the opposite weighting.
We’re kind of at the fast food point: before LLMs, bring successful at all in software required some level of skill (witness all of the companies getting very expensive write-offs from off-shoring or big consultancies trying to save on payroll vs. staff), kind of like how the small cafe/bakery model needed to have at least some level of craft to have something people would buy before the option of making food at a factory and shipping it became an option.
Sure, and that probably explains why companies (who sell software) love AI while hobbyists who just like to program hate it.
For the owner/shareholders yes.
The workers will see the fun evaporate but now they have to clean 10x cookie trays in the same 8 hours.
It is, although in this case the cookie-making robot also makes 10% of its cookies with sand instead of flour. So it's still not a very good trade if you have any pride in your business or consequences for bad product.
> Code review is (for many) the least fun part of programming.
I'm lurking around the OpenBSD mailing list and it seems that code review is where collaboration starts. You send a patch, explain its purpose, people try it out and comment. If it's OK (various factors decide that), it's imported inside the codebase.
The main issue in corporate settings is that the author of the PR wants to browbeat you into accepting his/her changes. Either directly or by appealing to the manager. They don't want collaboration, they just see you as the blocker between them and the "Done" status on the ticket.
I used to work at a company that did in-person pair review. I wasn’t an engineer there but the engineers all legitimately enjoyed the process. They hired very capable people as a default, so it was watching two passionate and talented engineers debate.
[flagged]
> ADHD wins over autism in the immediate future. It was balanced in the past for development to need both but now it’s a total hyperactive victory of general knowledge, master of none.
That’s an interesting framing. I’m not sure I agree with your strong conclusion but that’s mostly because I think there’s a second axis about maintenance – you can make a grand strategy game in a couple months but it’s harder to make it balanced, fun, and to keep shipping updates which players like. A prototype or hobby experiment doesn’t have that problem nearly as much and I think that’s where we see such bimodal reactions where some people think it’s a huge productivity boost and others see modest or even negative results.
I think we’re on opposite sides but this is the first time I’ve seen someone in the wild share my suspicions that the LLM conflict is part of some vast ADHD vs autism hyperwar. At one point I was collecting posts I found where LLM boosters explicitly mentioned how it interacted with their ADHD.
The contest you described (people with ADHD vs. autism) would have an enormously negative effect. But there are reasons to think it's unlikely. FWIW at least 25% of ADHD adults manifest autistic traits. Hardly surprising, clinicians regard overlapping neurodevelopmental disorders as the rule and not the exception.
An online community works when participants learn and share knowledge gained. Contests, with self or others, disrupt learning and sharing, hence by definition constitute "bad behavior". If it exists, the hyperwar you allude to will harm communities more than all LLMs combined could do.
I'm pretty skeptical of people who are ADHD and claim to be getting boosted by LLMs.
It's hell for my ADHD, personally. It's an infinite rabbit hole generator and distraction machine. I have to use browser extensions to filter out stuff like Stack Exchange suggestions for interesting topics, too. I have had to block Wikipedia in the past to avoid rabbit holes there
I'm better now than I used to be but I am skeptical of people who claim to both be good at multi-tasking and also have ADHD. My experience with ADHD is that multi -tasking is not a strength, it's a sign of distraction
9 replies →
>At one point I was collecting posts I found where LLM boosters explicitly mentioned how it interacted with their ADHD.
Care to share it?
1 reply →
Autism should not be framed as being "opposted" to ADHD. The correct axis is "Autistic" (Neurosis) as opposed to Psychosis. Opposite poles but with a little bit of horseshoe theory dynamics
> This way one person can implement a whole new hobby project instead of only writing a single specialized part in an existing project.
I still do start from bottom up to refactor everything into workspace members and this way, parallelism is way easier
> LLMs reward seeing forest instead of trees.
Not just forest. LLMs reward seeing structures and designs, and it still requires a lot of creativity to design it well. I have to do a lot of architect works for that, like package layout, testing strategies (BDD vs TDD vs E2E), setting up access to platforms and digging out what strategies to apply...etc.
> People focused on the trees will however lag behind as implementation details matter less and less.
Trees like demonstrations and example code are even more important. This is because those are literally post-training materials for the LLMs
> Specialists will be fed to the model weights
I don't think so. New labor laws are certainly going to be introduced by the politicans to tackle this.
> generalists will inherit the world.
Now the problem is how far do you want to stretch the systemic thinking, and you also get burned out quicker.
Funny you should mention autism. I'm of the belief that if I really wanted to, my autism could help me become a very effective AI-assisted programmer, because autistic communication traits that actual humans find annoying (and which most people hence train out of themselves), like infodumping and using precise language, are things AI actually loves and produces better results with.
But I don't want to use AI to code, in large part because I iterate on ideas by working directly with code. Attempting to program through an LLM intermediary becomes like attempting to eat using soft silicone chopsticks.