News for hackers. Stuff that matters.
Re:A Family Tree of Software Job Titles by dan_grec on Sunday November 15, 2026 @03:30AM (#50505120)
I remember a professor who used to say “If the requirements, design, test plan and acceptance criteria are done to a high enough standard, the code can be written by a monkey.”

Which is exactly what we’re seeing now with LLMs writing code.

Interestingly you’ll see the same building a mega bridge or skyscraper. As long as the plan has been done well, it can be assembled by relatively very unskilled labor.

Note the test plan and acceptance criteria could be one and the same, depending.

Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @07:19AM (#50506400)
> If [everything before coding] are done to a high enough standard

That "if" is doing an unrealistic amount of lifting, here, in practice, and that's probably why human coders have had a better run than monkeys.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @06:59PM (#50512260)
I'd disagree as we have counterexamples all over the place in the real world. For software there's LLMs - it is clearly possible to use them to implement large projects autonomously provided that your requirements are sufficiently well thought out. Zooming out to other disciplines any large construction project fits the bill. Clearly a "high enough" standard is achievable.
Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @07:15PM (#50512394)
Just talking about software engineering, I think that the places where requirements are strong enough to be implemented unambiguously, are few and far between. So, it's "clearly possible", but rare, in my universe, your mileage may vary.
Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @07:22PM (#50512446)
And yet somehow people are successfully leaving some projects almost entirely up to agents. Does that not run directly counter to what you're saying?

Also I will observe that something being rare is not in and of itself an indicator of whether or not it is reasonable. Many things are done a certain way because that's the conventional approach or it's more cost effective or due to some logistical concern.

In the case of software development it was previously cheaper not to exhaustively specify everything up front but I'd argue LLMs have upended that longstanding status quo within only the past year.

Re:A Family Tree of Software Job Titles by sverhagen on Sunday November 15, 2026 @08:02PM (#50512763)
I don't think that runs counter...

We had humans that were smarter than monkeys, dealing with imperfect requirements. Now we have LLMs that are smarter than monkeys, dealing with imperfect requirements.

LLMs don't work because of good requirements input, they work despite the poor requirements they're given.

Re:A Family Tree of Software Job Titles by fc417fc802 on Sunday November 15, 2026 @08:56PM (#50513102)
Okay but all you're arguing at that point is that it will continue to be rare because LLMs that exceed the capabilities of monkeys are readily available and not that much more expensive than their less capable cousins. Not that there's any inherent reason it's unrealistic to do so. With skyscrapers it's cheaper to make sure the specification is bulletproof and with software it's cheaper to kick it out the door while it still has more than a few holes in it.
Re:A Family Tree of Software Job Titles by f1shy on Sunday November 15, 2026 @07:25AM (#50506423)
> If the requirements, design, test plan and acceptance criteria are done to a high enough standard, the code can be written by a monkey.

Nice sentence. But it has 2 problems:

1) Define "high enough" - There is where good requirements start, make it measurable!

2) Related to "you’ll see the same building a mega bridge or skyscraper". I've seen enough cases where "unskilled labor" messed up building something. You will reply "that is why I said 'Acceptance Criteria'!". My take is: you are making it far more complicated than it should, taking totally unnecessary risks, and it will be invariably more expensive in the long run.

I mean, I've seen enough examples of cases where the acceptance criteria was not properly checked, because also the ones doing the test were "unskilled" and had received a "perfect plan". (Just look at any infrastructure disaster we have every year)

And even in the best case: you discover the poured cement does not meet the specifications. What now? Blow the thing and start over? Better to have skilled labor.

Again, my 2ct. experience: hire experienced people, who actually have done the work all the way down to the lowest level.

"If you think knowledge is expensive, try with ignorance"