technical debtKids, it’s 2020. That it means it way past the time to kick the can down the road. Most of us in IT have been around long enough to see us shift from a centralized CPU (mainframes) to decentralized (client/server) architectures back to a centralized approach again (cloud). That means we have encountered problems and we have ignored problems, and those ignored problems have a name. It’s called Technical Debt, and the check is coming due.

Technical Debt

We all have it, and it tends to bite us right in the ass. It causes us to make compromises and other less than stellar decisions about how to handle it. What we need to do is start addressing the debt, figure out ways to minimize the impact of the debt. Stop covering it up with more hardware, crazy monitoring schemes, and automated fixes that just treat the symptoms and ignore the problems.

Just start working on it already. You’ve known about this debt for years/decades and it’s not getting worked on. Stop ignoring and start spending some time refactoring. Your customers will thank you, your developers will thank you, and your staff will thank you.

Some times I just want to kick myself. A very simple concept that I never thought about applying to work, I was bouncing around the internet trying to get a better understanding of how to use source control with my script library when I found a rabbit hole.

The rabbit hole in question was of the “How to write better code” / “How to be a better developer” variety when I came across an article about keeping a journal for programming. In fact, it was this article.

Dammit. Why hadn’t I thought of that sooner? I suppose it follows the advice about posting articles/resources on your blog for you to search against later. It just hadn’t occurred to me to keep a journal discussing ideas that weren’t ideal for blogs for various reasons.

 

Maybe I’m just old school, or maybe I just suck at business in general, but I don’t think it’s asking much to respect your customers. I certainly understand there decisions that need to be made to keep a company afloat, and in business. I mean you have to worry about the bottom line and the employees (hopefully the employees come first, but that is a different rant). Recently Code42, the company behind Crashplan the backup service, announced they were no longer going to offer Crashplan to regular consumers, i.e. you and me. 

Here’s a screen shot of there announcement here:

So what, why does piss you off?

It’s not my business right? I shouldn’t care how they purse revenue. Ya, you’re right, I shouldn’t. The problem is, as a 20 year career IT guy…I have recommended their service time and again. Both personally and professionally. So it sticks in my crawl so to speak, that they would just throw out an entire business model. Again, not my business or my revenue stream, but it was my recommendation and my reputation that suggested you could trust these people. They abused that implied rust. Maybe I’m the only who sees it that way and I should just get over it. On the other hand, maybe that’s what’s wrong with the world today…no one cares about anything but there bottomline, and they’ll get the most money with any means necessary.

Because after all, when you tell me your focus is solely your enterprise customers, you’re telling me you are focusing on greater revenue streams. And as an IT professional, you screwed me over at home, do you think I’m going to let you have that opportunity at my place of employment.