what is the definition of bad design and flawed programming?
a primary (and standard!) way of telling if your code for ‘improvement’ is actually inherently flawed is a very simple one:
- does what used to take # of end user steps now require greater than # of end user steps? if the answer is yes, you are a bad programmer and need retraining (and those above you in your chain of command need to: 1) tell you to cut the crap; 2) refuse to implement that bad code)
of course, this is exactly what happened here
why?
I wish I knew why any company decides “hey! this bad code is exactly what we need to add to our product! let us get right on that!”
yet sadly this is so common that it has become quite typical (and occurs often enough that multiple articles have been written about one company or another taking such horribly flawed courses of action)
what malarkey