Last month I mentioned a Commodore-64 designed out of Lego. Back then, it was just a design, but now it actually exists! There are two keyboards—one where a real Commodore-64 keyboard has the keycaps swapped out for Lego keycaps, and the second keyboard is a fully mechanical Lego design.
I think it would be possible to use the pure Lego keyboard on a real computer, but it would probably require a custom PCB to handle the different mechanical action. Size wise, it's a perfect fit though. And boy, does it have that sweet clicky sound of a mechanical keyboard.
It's been an interesting week, in the Chinese sense of “interesting.” First was the grueling deployment to production that ended at 6:00 am, followed by a mandatory all-day meeting starting at 11:00 am and that was just Tuesday! Today was another mandatory all-day meeting, followed by a trivial but show-stopping bug (read “rookie mistake” made by yours truly) being found in production and the subsequent six hours to get a patched version installed (it took less than 10 minutes to reproduce the bug, find the root cause, and fix it) because most of the operations team (who do the actual deployments) were flying back to The Corporation Headquarters in Seattle, having attended the said two-day mandatory meeting here at The Ft. Lauderdale Office of The Corporation.
Then my “self-review” (which was designed solely as some abstract HR process, despite the protestations of upper management of Our Corporate Overlords of the Corporation) was rejected as not being “meaty enough” (what ever that means) and I'm like … yeah … about that flair … (it only took Bunny two hours to talk some sense into me).
The process of our process is to process the process to ensure the process has processed the process
Bunny was helping me with my “self-review” since I was at a total loss of what to even say. “You aren't built for dealing with bureaucratic processes, are you?” she asked.
“No,” I said. “I'm not. I never have been. I remember back in fourth grade—”
“No! I don't want to hear it!”
“And then there was that time in middle school—”
“I'm not listening!”
“So I guess you don't want to hear about high school then?”
“La la la la la la la la la!”
Yeah, my rage against the bureaucratic process goes back a long time.
I mean, I understand that processes are at times required. There can be good reasons to have a process so everybody knows what to expect and get consistent results. But this “self-review” is just not one of them. I eventually spent over eight hours trying to say enough to avoid the “rejected due to cursory responses” (never mind them being “meaty enough” and I still don't know if I succeeded at it). And the weird thing is, the majority of the “goals” didn't even apply to what I do! They were more geared towards a manager than a programmer.
This is almost making me want to work with the Protocol Stack From Hell again.
Years ago in college, I worked in the auditorium as part of the stage crew and one of the many jobs was running the spot light during shows. There was one two hour show I worked where the spot light would only be used for about fifteen minutes about half-way through the show. This meant I had to sit next to the spot light for nearly an hour, do the fifteen minutes of work, then sit there for another hour until the show was over.
As I sat there waiting for my cue, my mind wandered. I'm about twenty to thirty feet above the audience, I thought. This platform is suspended from the ceiling and held into place with those four bolts. I wonder when was the last time they were checked? What would I do if they failed? Could I grab and hold onto something? What could I grab? What was that creak? Oh, part of the show, okay. How much does that spot light weigh? I sure hope these bolts hold for another 98 minutes …
I was reminded of this today as I sat in our daily, thrice-weekly standup scrum meeting. Our acting manager and a team leader from another team were going back and forth about an overscoped and time deficient schedule when my mind wandered again. Staring out the window, I was watching the sun behind a hazy layer of clouds. At our latitude, I thought, we're moving at 940 mph towards the east. The earth itself is moving at 67,000 mph around the sun, and the sun itself is moving our entire solar system at 514,000 mph. All of this is held together by the force of gravity, a force so weak that a kitchen magnet can overcome it. It's a wonder everything doesn't just fly apart. I sure hope those bolts hold for another— “Huh? What?”
“I asked what have you done in the past 48 hours since our last daily, thrice-weekly standup scrum meeting?”
“Oh, just pondering the ridiculous speed we're hurling through space as we're held together with four small bolts.”
“Are you okay, Sean?”
I changed the image on my homepage. Normally, I wouldn't comment on this, but this time? This time I had to track down a sixteen year old bug in code I wrote in a language that makes COBOL look terse that manages the non-bloggish part of the website. All because I broke from twenty-one years of tradition and used a different image size! (It's a really good picture a friend took and it really benefits from the non-traditional size)
I had thought the code I wrote would deal with the non-traditional size and yes, it picked up on the new size, but that size was then used for every self-portrait on the site.
It's also been ten years since I last dealt with the code, and even then, it was just to get it running under a newer version of the language. This time, I had to figure out what the hell I was doing sixteen years ago. From various timestamps, I can tell it only took about an hour to track down the bug and fix it (eight new lines of code, mostly under 140 characters in length—sigh) but it certainly felt longer.
This is one of those situations where the language is ugly, the solution aggravating to maintain and yet, it works, and for what I want it's still the best solution to the problem of maintaining a static website.
Hopefully, I can go another ten years before the next bug manifests itself.
So I received this in email today:
- Chevrolet <XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>
- Sean, employee pricing is back on most Chevy cars, trucks and SUVs
- Thu, 13 Dec 2018 17:11:46 -0800 (PST)
This is plain text, with a line break:
Next new line
And the thing that I immediately thought of were old IBM manuals that would have a page with the following text:
This page intentionally left blank.
No it's not. It should have read:
This page intentionally left blank, except for this line of text.
At least this email from Chevrolet is more accurate than the old IBM manuals. But then again, I wonder what Chevrolet was trying to sell me.