> the hard bit of being a developer is deciding in precise, pedantic, utterly exact detail on what needs building to solve the business problem The process see

> the hard bit of being a developer is deciding in precise, pedantic, utterly exact detail on what needs building to solve the business problem The process seemed to involve have a test suite to write against. So, essentially, you had some/most of your "business problem" defined by acceptance tests (produce these outputs given these inputs). Some of that process may normally stretch out for days or weeks during meetings - condensed down, provided for you ahead of time takes some of that variability out. I was possibly a bit more surprised that less than 80% finished. Did they not commit code? Did they submit code but it didn't pass? Did they take too long? Was the 'did not finish' an explicit call on the dev side ("I'm done") or did they just stop taking input after X days?