[noisy_boy]

> I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media.

2026 is just when it picks up - it'll get exponentially worse.

I think 2026 is the year of Business Analysts who were unable to code. Now CC et all are good enough that they can realize the vision as long as one knows exactly the requirements (software design not that important). Programmers who didn't know business could get by so far. Not anymore, because with these tools, the guy who knows business can now code fairly well.

[sponaugle]

"I think 2026 is the year of Business Analysts who were unable to code." This is interesting - I have seen far more BAs losing jobs as a result of the 'work' they did being replaced by tools (both AI and AI-generated). I logically see the connection from AI tools giving BAs far more direct ability to produce something, but I don't see it actually happening. It is possible it is too early in the AI curve for the quality of a BA built product to be sufficient. CC and Opus45 are relatively new.

It could also be BAs being lazy and not jumping ahead of the train that is coming towards them. It feels like in this race the engineer who is willing to learn business will still have an advantage over the business person who learns tech. At least for a little while.

[HugoDz]

Agree here, the code barrier (creating software) was hiding the real mountain: creating software business. The two are very different beasts.

[jazzpote]

Software engineers were never paid to "create software business". That's the job of business ppl, and a thin minority of software engineers.

[kitd]

with these tools, the guy who knows business can now code fairly well.

... until CC doesn't get it quite right and the guy who knows business doesn't know code.

[rubzah]

The future of the programmer profession: This AI-generated mess of a codebase does 80% of what I want. Now fix the last 20%, should be easy, right?