What an absolute fucking disaster of a day. Strap in, folks; it's time for a bumpy ride!

I got a whole hour of work done today. The first hour of my morning because I went to work a bit early. Then people started complaining about Jenkins jobs failing on that one Jenkins server our team has been wanting to decom for two years but management won't let us force people to move to new servers. It's a single server with over four thousand projects, some of which run massive data processing jobs that last DAYS. The server was originally set up by people who have since quit, of course, and left it behind for my team to adopt with zero documentation.

Anyway, the 500GB disk is 100% full. The memory (all 64GB of it) is fully consumed by stuck jobs. We can't track down large old files to delete because du chokes on the workspace folder with thousands of subfolders with no Ram to spare. We decide to basically take a hacksaw to it, deleting the workspace for every job not currently in progress. This of course fucked up some really poorly-designed pipelines that relied on workspaces persisting between jobs, so we had to deal with complaints about that as well.

So we get the Jenkins server up and running again just in time for AWS to have a major incident affecting EC2 instance provisioning in our primary region. People keep bugging me to fix it, I keep telling them that it's Amazon's problem to solve, they wait a few minutes and ask me to fix it again. Emails flying back and forth until that was done.

Lunch time already. But the fun isn't over yet!

I get back to my desk to find out that new hires or people who got new Mac laptops recently can't even install our toolchain, because management has started handing out M1 Macs without telling us and all our tools are compiled solely for x86_64. That took some troubleshooting to even figure out what the problem was because the only error people got from homebrew was that the formula was empty when it clearly wasn't.

After figuring out that problem (but not fully solving it yet), one team starts complaining to us about a Github problem because we manage the github org. Except it's not a github problem and I already knew this because they are a Problem Team that uses some technical authoring software with Git integration but they only have even the barest understanding of what Git actually does. Turns out it's a Git problem. An update for Git was pushed out recently that patches a big bad vulnerability and the way it was patched causes problems because they're using Git wrong (multiple users accessing the same local repo on a samba share). It's a huge vulnerability so my entire conversation with them went sort of like:

"Please don't."
"We have to."
"Fine, here's a workaround, this will allow arbitrary code execution by anyone with physical or virtual access to this computer that you have sitting in an unlocked office somewhere."
"How do I run a Git command I don't use Git."

So that dealt with, I start taking a look at our toolchain, trying to figure out if I can easily just cross-compile it to arm64 for the M1 macbooks or if it will be a more involved fix. And I find all kinds of horrendous shit left behind by the people who wrote the tools that, naturally, they left for us to adopt when they quit over a year ago. I'm talking entire functions in a tool used by hundreds of people that were put in as a joke, poorly documented functions I am still trying to puzzle out, and exactly zero comments in the code and abbreviated function names like "gars", "snh", and "jgajawwawstai".

While I'm looking into that, the person from our team who is responsible for incident communication finally gets the AWS EC2 provisioning issue reported to IT Operations, who sent out an alert to affected users that should have gone out hours earlier.

Meanwhile, according to the health dashboard in AWS, the issue had already been resolved three hours before the communication went out and the ticket remains open at this moment, as far as I know.

VsCode.

I have been on a journey with editors, all the way back to using edit.exe in Windows 95, to notepad, MS FrontPage, Adobe Dreamweaver, PHPDesigner, vim, nano, then out to Eclipse, Atom, Brackets, notepad++, back to Atom, then VsCode.

And by far, vsCode has given me the most productivity and customisation of them all to not care about what project I open, what language it's written in, or what frameworks are working behind it. I can switch with workspaces and everything is setup to go, yes it's a pain in the ass to setup, but it's a ducking dream to just open and jump in.

Now being able to use VsCode for Salesforce has dropped any requirement for me to keep eclipse around.

Before 2012, I always worked in cubicles and had weekly status meetings. In 2012 I moved to a big city and learnt there was something worse than cubes: the open work plan. Marketed as a way to increase coloration, the open work space is really just the result of real estate prices being expensive in cities and how desks are cheaper than 3-cube walls.

Up until 2013, we'd usually just have the weekly status meeting. Here are your tasks for the week. I'd do them at my own pace. Some days fast, some days slow, but they'd all get done by the end of the week and I'd proudly go down my list of stuff I had done.

Since then, it's all been "agile" and "stand-ups" every. fucking. day. The work is endless. A Product Owner once told me that stand ups weren't suppose to be status meetings; that you were only suppose to say if you're blocked or need help. But in every place I've worked at, they're daily status reports. You have to preform every day.

I really hate IT today more than ever. I miss the cube. I miss the weekly status reports. Today things are so high stress and higher paced and the work is endless. You can't even really pace yourself anymore.

I want to pause my music so I can focus, but I have two co-workers right next to me who are working in a problem. I could take my laptop somewhere else, but I would rather they just shut the hell up, or go book a damn conference room.

I could just say that .. or just be lazy and post about it on dev rant. 😅

Also, fuck open workspaces. I never though I'd miss the cubical, but the open work space is a new level of hell.

Started up KiTTY to connect to my virtual test server per usual when I couldn't establish a connection.

Nothing too unusual so I do the typical troubleshooting I make sure host, port and authentication is all correct and it is. So now I open the display for the virtual server and start looking at ip info, host info, checking ports and everything is completely fine.

Now I'm getting frustrated so I start running things like configtest in apache, using systemctl to check the services status, even restarting virtualbox in my windows 10 devpc. Still cannot connect!

I start feeling hopeless and just shut everything down, the whole operating system.

*takes breath*

Computer boots up and I start my usual thing of creating workspaces, opening editors, starting servers, etc.

I open KiTTY again and launch my virtual test server..

konicm8ker@VM-UBUNTUSERVER:~$ _

Somethings you just can't fix without a reboot.

Music, but if it has words they need to be foreign. J-rock, deadmau5, gogo penguin, carrion... All are good.
Dark themes everywhere unless it's java, because it helps me compartmentalise my languages.
Second screen hooked up with the stuff I want to be viewable all the time, as it doesn't change when I switch workspaces. (bug or a feauture?)
Door shut to muffle sounds from the rest of the house, window slightly open so I don't suffocate.
Pomodoro timer on, but put phone into silent mode so no notifications disrupt my focus.
Drinks and bathroom breaks happen in the 5 minutes between pomodoro sprints. Food happens in the 15 minute breaks.
Extra RAM stick is in the mail so I lose less time waiting for android studio to exhale or whatever it's doing as it holds up the whole computer.
I might just do the java parts of my project in bluej if this ram stick doesn't alleviate my problems. I could go outside and drink mud through a metre long straw with a filter on the end sooner than android studio gets unstuck.
If anyone can add more sensible ideas I'd be happy :)

Why is there no feature to save your OS' state across reboots?

Like images or savestates you can load up any time.
Besides the fact dual booting is way more useful this way, you could have huge organized workspaces, leaving your current work open, clicks away.

Even in professional IT this would be a gamechanger.