3 ms·
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 proce
by jbverschoor 2y ago
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.
- vharish 2y agoI mean.. can you show anyone piece of software or hardware or for that matter any man made creation that solves for all edge cases?
- jbverschoor 2y agoBut 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
- borski 2y agoEverything is a “simple thing” unless you’re the one implementing it. Things that seem simple on the surface rarely are, especially long-term.
- jbverschoor 2y agoI’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?
- borski 2y agohttps://www.quora.com/Why-are-software-development-task-estimations-regularly-off-by-a-factor-of-2-3/answer/Michael-Wolfe https://www.quora.com/Why-are-software-development-task-esti...
- jbverschoor 2y agoThat article means: inexperience and unprofessional. Sounds about right.
- borski 2y agoIf 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.