38

So a consulting company was hired to write stored procedures for us. I don't know where they found these guys, but the code was horrible and took ages to run.

We other devs weren't happy at all, but management forbade us to rewrite the code, cause the consultants would've gotten money for nothing then. As a "fix", these guys just reduced batch sizes to a very low amount of rows and management was happy that the procedures were so much faster now and gave their ok.

Fast forward a few weeks (to now). Obviously a reduced batch size means the procedures will run faster, but more often and it will take weeks to load all the data we need.

Result: Management ordered us to rewrite the SPs and we're all torn between laughing and crying.

Comments
  • 15
    Sometimes mngmnt fails to comprehend simple thing: trust your devs. It's annoying but it is what it is
  • 1
    I am always tempted to take advantage of stupid Management, by getting very active on my side-projects. That being said @codingTripledad s nick suggests there are other forces at play preventing action on non-family side-projects.
  • 1
    @Wolle Let's say yes and no ;) I have my small side projects for these cases indeed. Can never acquire too much knowledge, so I'm always making sure that I book some overtime while I test new features or new ways of doing things. This inflates the costs to correct shitty code even more, so maybe they'll learn one day.

    Spoiler: they won't
  • 2
    This is actually a good outcome. Most often these smells stay with the product forever unless someone "finds a bug" and "fixes it" which is a code for rewriting from scratch without telling anyone higher up.
Add Comment