After My First Full Week of Being Laid Off

UCLA MCCS Hey folks! It’s schadenfreude time! (And it’s also a time for sincere sympathy—which I do appreciate with equal sincerity.) After almost ten years working IT for UCLA Healthcare, my time came to an end in a most dramatic way. This is an excerpt from my personal journal (that is so personal it can even be published here, in the rasx() context):

News helicopters swarmed in the skies around UCLA Medical Center as my furlough papers were served to me by…

That’s right! On the publicized date of Michael Jackson’s death, my show at UCLA came to an end. One question that hangs out there is, “Did you see it coming?” Here are some bullets for that one:

There was never any formal architectural solution to the problem of bridging this gulf. What this means is that the knowledge workers are forced into a bottleneck everyday—waiting for MCCS people to complete a myriad of data entry tasks on their behalf. This is tolerated for antiquated, provincial, cultural reasons that no official MCCS “architect” should be proud of—on the contrary: there should vocal, open declarations of shame on at least a weekly basis. To be honest, I considered my presence at UCLA the solution to this problem. IBM came with SOA and left. Microsoft consultants showed up to bring us SharePoint but we had no servers (and no populated Active Directory) waiting for them (this, by the way, was the last straw for me).

Okay the next question might be, “Dude, why didn’t you just leave!” More bullets:

It’s time to do something else. I’ve got less than 90 days to make a constructive change before the heavy stuff starts.

Related Links

rasx()