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.

▲ LPisGood an hour ago | parent | next [-]

It is probably a good trade off if you sell cookies or if you vastly prefer eating cookies to making cookies.

	▲	bawolff an hour ago \| parent \| next [-]
		Sure, and that probably explains why companies (who sell software) love AI while hobbyists who just like to program hate it.
	▲	cocoa19 an hour ago \| parent \| prev \| next [-]
		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.
	▲	bigstrat2003 40 minutes ago \| parent \| prev [-]
		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.

▲ skydhash an hour ago | parent | prev | next [-]

> 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.

▲ juleiie an hour ago | parent | prev [-]

What you need from LLM is recipe making.

Main course is this this and this, 1. Do this 2. Plug this 3. Run this.. step by step plan.

So you get a precise top down construction plan. Then it’s easy to split the parts where the coding needs to be manual (smoothing walls) vs where it can be whateverz (laying concrete).

LLMs reward seeing forest instead of trees.

This way one person can implement a whole new hobby project instead of only writing a single specialized part in an existing project.

Good luck making a grand strategy game in two months holidays without an LLM. Now you can.

People focused on the trees will however lag behind as implementation details matter less and less.

Yes manual touch is still needed in some parts of the construction process but architecting the whole thing is the most important in 2026.

  ⢀⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀

⠀⠀⠀⢀⣼⣦⠀⠀⣠⣿⣿⣦⣀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣼⣆⠀⠀⠀⠀⠀ ⠀⠀⠒⣿⣿⣿⠓⠀⠀⠻⣿⣿⠀⢀⣴⣿⣦⡀⠀⢀⣾⣦⠘⢿⣿⣧⡀⠀⠀⠀ ⠀⢀⣴⣿⡿⠃⡄⠈⠻⣿⣟⣉⣀⠉⣽⡿⠋⠡⠴⣿⣿⣿⠓⠀⠙⢇⠀⠀⠀⠀ ⠀⠿⣿⠟⢁⣾⣿⣦⣀⠘⠿⠟⢁⣼⣿⣿⣷⠂⣴⣿⣿⣿⣆⠘⢶⣶⣿⠶⠤⠀ ⠀⣀⣀⡀⢉⣿⣿⣿⡍⠀⢀⣀⠙⢻⠿⢋⣤⣾⣿⣿⣿⣿⣿⣷⣄⠙⢿⣦⡀⠀ ⠀⠟⠋⣠⣾⣿⣿⣿⣿⣦⣌⠉⠠⣤⣤⣤⡌⢙⣿⣿⣿⣿⣿⣿⠛⠛⠂⢈⣙⠀ ⠀⠀⣉⡉⣹⣿⣿⣿⣿⣏⠉⣉⣀⣈⠙⠋⣠⣿⣿⣿⣿⣿⣿⣿⣆⠙⠛⠛⠛⠀ ⠀⠀⠋⣴⣿⣿⣿⣿⣿⣿⣷⣌⠉⢁⣴⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⣄⠀⠀⠀ ⠀⠴⢾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠦⠈⣙⠛⠛⠛⠛⠛⠛⠛⠛⣉⣉⠁⠀⠀⠀ ⠀⠀⣦⣤⡄⢉⣉⣉⣉⠉⣡⣤⠀⠀⠀⣿⣿⣷⠀⢰⣿⣿⡇⢸⣿⣿⠀⠀⠀⠀ ⠀⠀⣿⣿⡇⣸⣿⣿⣿⡄⢻⣿⠀⠀⠀⣿⣿⣿⠀⢸⣿⣿⡇⢸⣿⣿⠀⠀⠀⠀ ⠀⠀⣿⣿⠁⣿⣿⣿⣿⡇⠸⠿⠀⠀⠀⣿⣿⣿⠀⢸⣿⣿⣇⠸⣿⣿⠀⠀⠀⠀ ⠀⠀⠛⠛⠀⣿⣿⣿⣿⡇⠀⠀⠀⠀⠀⠉⠉⠉⠀⢸⣿⣿⣿⠀⠿⠿⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⠛⠛⠛⠛⠃⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠉⠉⠉⠀⠀⠀⠀⠀⠀⠀

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.

Specialists will be fed to the model weights, generalists will inherit the world.