Hacker News Reader

So having clear requirements, a focused purpose for software, and a clear boundary of software responsibility makes for a software development task that can be accomplished?

If only people had figured out at some point that the same thing applies when communicating to human software engineers.

View on HN

If human software engineers refused to work unless those conditions were met, what a wonderful world it would be.

They do implicitly: you can only be accidentally productive without those preconditions.

Explicitly failing fast is needed I think.

Failing slowly and producing months of unhappy results is too slow of a feedback cycle.

Reply on news.ycombinator.com