I consult for large bureaucracies where this kind of thing is occasionally enforced.
There’s nothing more fun than a carefully thought out cohesive design that takes into account all business and technical constraints being randomly “improved” by a too-busy senior manager who’s been “off the tools” for decades.
“You should switch to NoSQL.” — a nearly verbatim quote from a meeting just last week. No justification or elaboration, just… abandon a relational database platform with two decades of built up business value on a whim.
I used to work for a chief exec like that. They’d see something on someone’s screen and demand changes, destroying months of carefully planned work with a single comment.
In the end, we’d build in ‘breakpoints’ - things that we knew they’d pick up on and want to change so they felt like they’d had some input without damaging anything important. This worked very well.
There’s nothing more fun than a carefully thought out cohesive design that takes into account all business and technical constraints being randomly “improved” by a too-busy senior manager who’s been “off the tools” for decades.
“You should switch to NoSQL.” — a nearly verbatim quote from a meeting just last week. No justification or elaboration, just… abandon a relational database platform with two decades of built up business value on a whim.
“Rejoice! For you have been managed!”