3 ms·
> Usually the output and behavior of a program is well specified enough that we should have a checkbox (test?) for it I've literally never worked in a project
by icebraining 7y ago
> Usually the output and behavior of a program is well specified enough that we should have a checkbox (test?) for it
I've literally never worked in a project like this. It's always "here's some general idea of what we want, with a couple of hard constraints. Build it however it makes sense to you, and we'll change anything we don't like after we see it." The only exception I can think of is data import from a known file format or API.
- viklove 7y agoIt's very easy to explain to someone why blowing a hole in their bedroom wall to put an extension cord through it is a bad idea. On the other hand, try explaining to your product team that building a certain feature in 2 weeks will require doing the equivalent of that, and they won't see any issues with it. This is the problem with building software. It's intangible and non-developers have a very hard time understanding the tradeoff of doing something "hacky" vs doing it right.