We Could Write Nearly Perfect Software but We Choose Not To (blog.inf.ed.ac.uk) 7 points by actually_a_dog 4y ago ↗ HN
[–] webmobdev 4y ago ↗ > Code Review Performed by a Separate TeamIt's a very good suggestion that intuitively feels right but I shudder at the extra work load and the distraction that this can be. [–] AnimalMuppet 4y ago ↗ Yeah. We could write much less nearly perfect software, but we choose to write much more somewhat flawed software.
[–] AnimalMuppet 4y ago ↗ Yeah. We could write much less nearly perfect software, but we choose to write much more somewhat flawed software.
[–] cafard 4y ago ↗ How about "We Could Write Nearly Perfect Software, but We Don't Have NASA's Budget or Well-Scoped Projects"? [–] chadcmulligan 4y ago ↗ > Well-Scoped ProjectsThis is a big part imho, in many ways engineering type stuff is easier because you know exactly (pretty well) what you have to do, in business systems, its a lot fluffier.
[–] chadcmulligan 4y ago ↗ > Well-Scoped ProjectsThis is a big part imho, in many ways engineering type stuff is easier because you know exactly (pretty well) what you have to do, in business systems, its a lot fluffier.
5 comments
[ 3.6 ms ] story [ 17.0 ms ] threadIt's a very good suggestion that intuitively feels right but I shudder at the extra work load and the distraction that this can be.
This is a big part imho, in many ways engineering type stuff is easier because you know exactly (pretty well) what you have to do, in business systems, its a lot fluffier.