Posts

Back in 2016, a younger and mildly more optimistic Jay heard about a Kickstarter Campaign for a remake of the classic title, System Shock. Young Jay had fond memories of the original and immediately pledged $30 to help turn the dream into reality. Expected delivery was in December of 2017. Actual delivery for some was yesterday: May 30th, 2023. UPDATE 6/1/23: After logging onto the Discord server for Nightdive Studio and making a support request, I was able to finally exchange my PS4 version for an actual Steam key. The provided key seems to work so at least I have finally gotten what I paid for! Nevertheless, this post will remain as it serves as a word of warning when it comes to crowdfunding. Go into it expecting nothing but disappointment otherwise you will be let down ;) ...

Everybody knows I got a big mouth. That’s why I have a domain for my name and I’ve been posting tripe to it for over two decades now. The surprising part is that every once in awhile I say something that resonates with other people. That happened last week and I’m happy to report that my website handled it wonderfully. For starters, if you haven’t read my post “Low Code Software Development Is A Lie”, you should give it a go. The internet seemed to enjoy reading it for the most part. I generally don’t do any self-promotion of posts short of directly sending links to a few friends over Discord that I think might be interested in the topic. So at least one of my few dedicated readers (who presumably use the RSS feed to keep tabs on my content), posted it to Reddit and YCombinator. A riveting discussion was had by all. Note: I did not participate in any of the discussions as I had already spoken my piece on this topic. I just enjoyed reading what others had to say about it. ...

I’ve been writing custom software for a long time and one of the things that annoys me most is when a client adopts the position that there is a silver bullet which will reduce or remove the inherent complexity of this task. This happens more often than you’d think and guess what? They are almost always wrong. Perhaps I’m getting a bit too old and loose lipped for my own good, but the truth is that creating software for other people is exceedingly difficult. Contrary to the opinions of non-practitioners (aka non-coders), this difficulty is not the fault of coding languages, tools and paradigms. It is actually the result of clients and developers not taking the time to understand the root causes of the problems they want to solve and not designing a solution around the conclusions you’d draw from that process. ...

Anybody even remotely invested in keeping up with current events here in America, knows that TikTok is on the verge of being banned. If you are a frequent reader, you already know that I am against that. Doubly so in this case as the US Government has yet to provide a single evidence based argument to support the move, much less addressed the fact that American tech companies engage in largely the same exact kind of behavior that TikTok does. ...

Compared to most coders I work with, I’ve been coding a long time. Specifically since my father and uncle gifted me and my siblings an Apple II in 1985 when I was six years old. We also received a book called “Computer Fun” which attempted to teach BASIC programming to children. So despite all that youthful enthusiasm why do I feel like this career may not be for me anymore? ...

Much text has been written in recent weeks on the topic of the ChatGPT chat bot, its forthcoming integration into Bing and how it will change the world as we know it. While the commentary has run the entire gamut of possible responses, most of it is definitely more hype based than anything else. Today the hype dies. So lets start off with the most basic question. What is ChatGPT? Well as it so happens, ChatGPT is capable of furnishing us with a perfectly acceptable answer (LOG-TXT / LOG-PNG): ...

I recently took a new job and my new employer gave me a choice between a Lenovo Thinkpad with Windows and an M1 Macbook Pro with MacOS. Even my least dedicated readers know that I have no love for Windows and have spent literal years trying to rid myself of it. So of course I chose the Macbook Pro. Well dear readers, I’m going to be blunt: I wish I hadn’t. The reason why is simple: MacOS is a mess of bugs, half-baked features and is clearly only being maintained because Apple obviously feels like it has to. Over ten years ago when I last used MacOS on a regular basis at work, MacOS was perfectly serviceable by the standards of the day. It was competitive and Apple was clearly still excited for it’s future prospects. It wasn’t lacking in any noticeable way. ...

I’ve spent a lot of time debating on whether or not I should even write this blog post. Truth is that I was this close to just letting the entire thing fade into oblivion but after searching out some reading material on the subject, I decided that I needed to write about this, if only to remind future Jay what he just escaped from. Future Jay has a tendency to forget important things like that. ...

There is no great way to put this without a certain segment of my readers recoiling in horror, so I’m just going to say it. I’m tired of fighting for things on the job. After over 20 years of professionally being combative when I thought the situation called for it, I have resolved to turn over a new leaf. If you’ve worked with me, you know how it can be at times. When the company, the team or the boss decided to go down a road that I strongly disagreed with, I pulled every ethical tactic out of the bag to try and reverse things. Sometimes I was right and sometimes I was wrong on a technical level. But looking back I now realize that the level of technical correctness is not particularly relevant. ...

To those who don’t already know: I will be starting a new job next week. This is notable for one reason above all others: It marks my return to a much more normal situation. You see, for the last four and a half years I have actually had two jobs with two different employers. One of the conditions of the arrangement with one of my employers was that I had to largely keep this a secret from my coworkers there. So I mostly did (excluding those I worked very closely with who needed to fully understand my availability). For over four years. That included not discussing it on this blog. ...