Hacker News

Favorites Setup
Comment by f1shy | original | A family tree of software job titles
[−]f1shy · 2026-11-15 Sun 12:25 UTC · link
> 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! (How much is going to cost?)

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"