2017-Jun-13, Tuesday

dorchadas: (Office Space)
So on Friday last week, I arrived at work, booted up our database program, got to work, and immediately received a "number precision too large" error. So I fired off an email to support and waited. I heard nothing, but I was only there for a half-day since it was [personal profile] schoolpsychnerd and my ten year wedding anniversary. I figured they'd work on it and I'd come back on Monday and it'd be fixed.

Narrator voice: It was not fixed. Shaking fist emoji

It is now Tuesday, and I've gotten two emails, one of which asked me if it worked now (it did not), and the other saying they had escalated the problem up the ladder. It still does not work. This is pretty much confirming my preconceptions about corporate projects, where the new database was six months late, has a terrible UI, is less efficient than the 19-year-old internal software it replaced...and currently doesn't work. Good job. Congratulations all around.

And of course, all the people who originally pushed this project have left the organization. They made their dramatic mark, but deal with the aftermath? Pfft.

We'll see how long our new fancy database software doesn't work. Will it be down for a week? Tune in later and find out!

Profile

dorchadas: (Default)
dorchadas

August 2017

M T W T F S S
  12 3 45 6
7 89 10 11 12 13
1415 1617 1819 20
21 222324252627
28293031   

Expand Cut Tags

No cut tags