21

When the department’s large plotter printer broke down, the users demanded they still be able to execute their large reports. The area manager understood reality, if we are waiting on parts, not a lot we can do, but one developer decided to re-write the report/application as a web/.asp application. Mind you, he wasn’t a web developer, mostly VB experience, so the ‘report’ executed the same queries and filled up simple html tables. Did it work? Sort of. The output had none of the specialized formatting like headers, grouping, summary calculations, etc. Since the users could see the data in the web browser and scroll left/right, they were OK with the temporary fix. When I heard this:
Me: “You do know the application could output the report in HTML exactly the way it prints to the printer. All we would have to do enable that feature in the application.”
Dev: “Yea, but I thought it would be cool to do it as a web app.”
Me: “OK, but we should just update the app.”
Dev: “Um...that is going to be difficult, the boss liked my idea so much, he wanted the report replaced with my asp application. I deleted the application from source control and from the network. Sorry.”
Me: “OMFG!…tell me you make a backup!”
Dev: “Ha!...no…boss said you would fight innovation. Web is the future.”
Me: ”What is going to happen when the printer is fixed!? Users are going to flip”
Dev: “Oh, we didn’t think of that. Oh well, that’s your problem now.”
Me: “WTF? My problem?”
Dev: “Yea, you are moving to the team responsible for those legacy applications, since innovation really isn’t your thing. I just got promoted to senior developer.”

Comments
  • 3
    If that happened for real you need to find a new job and quick
  • 1
    @tomwolters Event was over a couple week period, but yea. Good piece was 6 months later the new senior dev was fired for some unethical behavior. I got the open spot.
  • 0
    Yikes. 😒
  • 0
    HTML sounds like the best solution. The plotter seems to be a critical single point of failure so maybe plan and document for when the plotter fails again. It will fail again, I promise.

    A simple plan will make recovery faster and easier next time. Good luck!!
  • 1
    @Jumpshot44 The report was moved to ReportingServices and the users now export to Excel. Funny after a few questions, users didn't use the paper report anyway.
  • 0
    Wow, what an awful situation. I would've put in my two weeks notice that day.
Add Comment