Hacker News Reader

>Meeting the acceptance criteria with guess and check isn’t hard.

Acceptance criteria often don't exist or are wrong. Incidentally, when someone says "business requirements are easy", that's a pretty big tell they have never worked on a complicated project.

> that's a pretty big tell they have never worked on a complicated project.

Even an 'easy' project, it's not easy. Edge cases, security, performance, dealing with error conditions, dealing with bad external vendor/data. "We'll just import data from vendor X". Yeah, that can never go wrong!

Hardest yet: apply professional rigor and be actually given time to do so because apparently just hacking something together that looks to work is the best thing ever (in the eyes of managers and business owners).

Software engineering is a well understood science in many cultures. Parsing acceptance criteria written by someone of another culture and domain experience can be difficult for some, and it’s not something learned in computer science courses.

Imagine having good ACs, or any ACs at all. Wouldn't be me!