ltlian188428dOver the years I've come to realize that part of my job is to make customers put in a bit of work for stuff like this. I've grown a superhero tier sense for when the order is basically "make this different", and without any specs you make some proposals which they aren't interested in because "idk man you figure it out", which always leads to "not like that tho" - either from people who weren't involved in the process or the very person who wanted the change. Usually the latter.
I'm trying to think of exceptions and if I'd need an "almost always", but I can't think of any.
One day: oh we need this shit implemented asap!
*shit was implemented*
Week later: we've dropped the requirement for that. We don't need this thing.
nitr0xis211. Customer wants X. 2. Developer delivers X. 3. Customer wants developer to change X to Y for free. 4. Develo...
blt9503If doctors were treated like web developers!
M-Arcus18Never let customers define the priority levels. It will end in: - Normal (never used) - High (used for small...