Hacker News new | past | comments | ask | show | jobs | submit login

I am wondering how you effectively start from the edge cases. To deal with errors, in particular complicated ones, you need the main skeleton coded and a central case working.

Are the 20% left (btw a fifth of stuff missing feels huge) really “edge cases” to them ? If these are behaviors they personaly can’t accept in a shipping product I’d totaly see devs ignoring arbitrary deadlines.

For instance I don’t think most people woud want to ship potentially data destroying code, even with a PO on their back pestering for a release of the rest. And a defense mechanism for that would be to cripple pieces of the main scenario until the critical cases are covered, if they can’t otherwise negociate that.

I am basing that on the fact that it’s a recurring event and from specific devs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: