Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

And this is exactly the problem when these devs are in charge of creating systems that actually do matter. They will not support edge cases, problems in a process, etc.


I mean.. can you show anyone piece of software or hardware or for that matter any man made creation that solves for all edge cases?


But it’s just simple things, like allowing an override of a status field.

Or using a status field to check something is ok or not, instead of always checking the data itself.

People make wrong assumptions, and requirements change. Don’t make it all rigid that you always need to implement every case


Everything is a “simple thing” unless you’re the one implementing it. Things that seem simple on the surface rarely are, especially long-term.


I’d say it has to do with not willing to duplicate data. On paper forms, it is simple. Why can’t it be in a digital form?


https://www.quora.com/Why-are-software-development-task-esti...


That article means: inexperience and unprofessional. Sounds about right.


If you’ve never written software that needed to be used by tens of thousands or hundreds of thousands of people, then sure, it could seem that way.




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

Search: