Chaning Alignment

>> NODE: ctrlaltcorp.dev

>> AUTHOR: HOTCHIP

>> TIME: [20260823-1300]

Sometimes you can defrag a drive and get it back online.

Other times you have to wipe the OS.

I'm switching alignment.

The funding for the old Corp® is drying up. You can hear it in the ventilation system. The servers still hum, the lights still work, the dashboards still turn green, but the money has started making that familiar disappearing act sound.

I've been looking around.

This is the third job I've found on the Corp® side that technically requires an EDU certification.

It's also the third one that looked at my resume, looked at the missing certification, and apparently decided, eh, close enough.

I don't exactly blame them.

I ran the usual loop. Background check. Credits. Drugs. The standard ritual where the Corp® asks you to prove you are simultaneously trustworthy, solvent, and chemically boring.

As usual, flying colors.

But this one feels different.

Other jobs had me second guessing myself. I'd look at the requirements and think, Shit. I don't know that.

Or worse:

They're going to expect me to know that.

This time I don't feel nervous.

I feel ready.

>> STATUS: OLD BUILD STABLE

>> USER: HOTCHIP
>> NEW DEPLOYMENT: PENDING
>> CONFIDENCE: UNEXPECTEDLY HIGH

I've spent the last couple of weeks documenting the old systems and working with the new guy.

The processes are written down.

The tribal knowledge has been extracted.

My code is now his code.

That's probably the closest thing to a clean exit you'll ever get in IT.

You don't really leave a system. You leave behind documentation, scripts, weird database tables nobody understands, and one poor bastard who eventually discovers why you named a PowerShell variable dont_touch_this_2.

But I'm not looking backward anymore.

The new job is different. BI. Data analysis. Pulling threads.

Data lakes.

Lakehouses.

Microsoft Fabric.

Power BI.

New tools. New dashboards. New pipelines. New places for bad data to hide.

I haven't used every one of those tools.

And that's the part that surprised me.

I don't care.

Not because I think I know everything. I absolutely don't.

It's because I've finally accumulated enough experience to know the difference between not knowing a tool and not knowing how to solve the problem.

Those are two completely different things.

Give me the data.

Give me the problem.

I'll learn the tool.

I've been doing that my entire career.

I've worked IT teams of one, four, and fifty.

One-person IT is basically digital arson containment. Everything is on fire and you're the entire fire department.

Small teams are better, but you spend too much time firefighting to really go deep into anything.

Large teams are the opposite. Sometimes they bring a nuclear reactor to a knife fight. You've got twelve people, six enterprise platforms, seventeen meetings, and somehow nobody is allowed to touch the database.

This new place looks interesting.

Electric Corp® is a bigger Corp® by land mass than the District Corp®, but the IT operation is smaller. Somewhere around twenty five people instead of fifty.

That might be my sweet spot.

Small enough to matter.

Large enough to specialize.

Still close enough to the users that you can actually see the damage when something breaks.

There are a couple of yellow flags.

They've asked about dealing with difficult users more than once.

That's usually Corp® code for:

>> WARNING

>> SOMEONE WILL YELL AT YOU

Fine.

I've met users.

Users aren't difficult because they're users. They're difficult because something they need isn't working, nobody has explained why, and IT has spent the last twenty minutes speaking to them like they're a malfunctioning terminal.

Most of the time it comes down to communication.

Some people want every detail.

Some people want one sentence.

Some want the answer.

Some want to know why.

You adjust.

What I don't do is bullshit them with technospeak. And I don't like the IT reflex of saying, “No, that can't be done.”

That's usually lazy.

Maybe it can't be done that way.

Maybe it costs too much.

Maybe it violates some security control.

Maybe it's a terrible idea.

But there is almost always another way to solve the underlying problem.

That's the part I bring with me.

Not Power BI.

Not Fabric.

Not some certificate that the Corp® decided was mandatory until they met someone who could actually do the work.

It's the accumulated junk in my head.

The databases.

The scripts.

The broken APIs.

The angry users.

The 2 a.m. failures.

The systems nobody documented.

The systems I documented because I didn't want the next guy to suffer.

The years of figuring out how everything connects.

That's the real certification.

Maybe I'm not switching careers.

Maybe I'm just changing networks.

Same operator. Different subnet.

And for the first time in a while, I'm not looking at the next machine wondering if I'm qualified to boot it.

I'm looking at it wondering what I can build once I'm inside.

>> NEW NODE DETECTED

>> AUTHENTICATION: ACCEPTED
>> DATA STREAM: OPEN
>> HOTCHIP: ONLINE
>> LET'S SEE WHAT'S IN THE LAKE 

I'm excited.

That's probably the strangest part.

After all these years, all the systems, all the Corp® nonsense, all the technical debt and political debt and actual debt...

I think I'm ready for the next build.

</div>