5

My employer has an application for product ordering/maintenance. Sounds pretty normal. It's an Excel spreadsheet that uses VBA to do the work, with a ton of SQL functions for row validation and procedures for database functions.

The guy that wrote it was a contractor who left the company well over 5 years ago.

No one on my team knows VBA. Me being the new guy gets tasked with this shitty VBA application's upkeep. Any time one of the braindead users fat fingers a value and the form blows up, I'm responsible for telling them exactly why they are stupid and sometimes I have to fix it for them because of the protections on the spreadsheet.

I've been asking the business to back a project for my team to develop a replacement but there is already so much happening for IT at my workplace, and my team is so under staffed (3 devs? Really?) That we spend most of our time fixing broken old shit.

We get an intern next month. Hopefully things improve soon because this tucking time bomb application sucks for everyone involved.

Comments
  • 1
    Hopefully devrant is niche enough that none of my co-workers know about it :o)
  • 0
    I think you hide in the crowd. Every. Single. Company. I've worked at has a process like this at one point or another.
  • 0
    Let it slowly rot, then you can go to management and say that it should be replaced because it's burning developer hours and user hours.

    "Managed Decline"
Add Comment