Unfortunately, I never got around to writing a good AI so you could play against the computer. At some point, I'd like to get back to that project.

Unless there's some life-changing event that requires me to get a larger vehicle, I plan to keep this car until it drops, or I do.

As a side sleeper, I can't use masks with speakers or even long ear plugs, as they put enough pressure on my ear cartilage that they make sleep uncomfortable.

Siteground had a "move my WordPress site" plugin that worked much smoother than I expected.

During the stream, I keep up a fairly constant spoken description of what I'm doing, what I'm thinking, what problem I'm stuck on, etc.

I've noticed I've also been speaking my thoughts out loud when programming, but not streaming. It ends up being a continuous "rubber duck" conversation, and feels (completely subjectively) like it helps me develop easier/better.

Back in 2014 I wrote a beginner's guide to C#, with the lessons building a very simple (non-graphical) role playing game. It was mostly to show the thinking behind starting out very simple, with the basics of objects, and eventually build a program that is larger and "complete".

It got a little popular and I've received quite a few messages/comments from people who've told me the lessons helped them understand things better in their programming courses at college or code camps. Those messages have been a lot more fulfilling than being coder #12 on $BigCo's multimillion-dollar, multi-year project.

It's also a nice thing to point to when interviewing. Just like a public GitHub repo, I doubt most interviewers take more than a cursory glance at it, but it is a way to stand out from the crowd of candidates who don't have a technical blog.

I've had times when I've burnt out and haven't posted for a year or more. Other times, I get a burst of energy and write every day. There is a bit of pressure to feel like I should be writing and posting. And, since I have programming guides, there are occasional support questions to answer (especially when Microsoft changes Visual Studio or moves from .NET Framework to .NET Core then to .NET 5/6). But, it usually doesn't take too long to deal with that.

On the technical side, it has been a bit of a pain to go through web hosts every few years. The hosting service eventually gets bought out, service quality goes down, or the site gets slow (and support says, "It looks OK to me"), etc.

It basically looked for all the "a" elements in the DOM and:

1. Set the href to call a JavaScript void

2. Set the element style's text-decoration to none

3. Set the element style's background color to #f3f315

The idea is to tag files/documents with attributes like "auto", "insurance", "2022", encrypt the file locally (using your manually entered key), copy it to a network share/cloud storage/etc., and add the tags and document information to a database.

Later on, you can search for documents based on the tags and get a decrypted copy of the file.

After 6-7 hours of dealing with the most aggressively-incompetent "support" I've ever had the misfortune to encounter, I cancelled every Intuit product/service I was using.

The reason they get away with this type of behavior is because we're all trained to fear the IRS to such a degree that we just want someone else who promises to "take care of everything" for us. And what recourse do we have when they behave badly? The court system? That's just as obfuscated and frustrating as the IRS. How much more of my time and money am I willing to put into dealing with Inuit? By the numbers, the smartest move is to just let this go.

It's everyone just settling for the lesser of evils/frustrations - until they get burnt badly enough.

It's a variation of chess where the capturing piece acquires the movement capabilities of the piece it captured.

I originally wrote a version seven years ago, but never got far in building a good AI for the bot player. As much as I like the idea behind the game, the program is really a testbench for me to work on memory and speed optimization techniques and probably eventually learn some AI/ML.

I keep "Can you please send me the job description and pay rate, so I can let you know if I'm interested?" in a text file, so I can easily copy-paste it.

I also created a web page, to send a link to the most annoying recruiters (https://hellotechrecruiters.com/), but haven't used it - yet.

www.youtube.com###secondary

www.youtube.com##ytd-browse[page-subtype="home"] #primary

www.youtube.com##.ytp-show-tiles.ytp-endscreen-paginate.videowall-endscreen.ytp-player-content.html5-endscreen

The lessons are based on building a simple role-playing game. They try to quickly get to something to make the students feel, "I wrote a program!". I try to get them creating a screen, displaying a little data on it, and adding a button that makes a change they can see on the screen.

However, a big problem is that this approach avoids a lot of good architectural decisions. I don't want to spend the first twenty lessons describing abstract application architecture. So, as the lessons progress, and students ask for more-advanced features, I inevitably need to do a big series of refactoring lessons - which loses a good percentage of the students.

Another struggle has been with the language and tools changing over the years. I really wish people stopped using the lessons I wrote in 2014, with Windows Forms, .Net Framework 4.5, and Visual Studio 2013. Most of my support has been for version issues. Unfortunately, I don't have the time/energy to re-do all those lessons and videos.

I've been a corporate C# programmer for years, working in Windows. But, I should be able to do a lot of my work in Linux now.

Besides undercommitting for the sprint, I've seen a lot of point inflation. Developers start padding their story point estimates to allow for extra time.

The worst case I ever saw was a team of five developers breaking down a feature request into very small stories with total points that would require the whole team's workload for two sprints. I completed all those stories by myself in three days. I'm good, but not that good. I suspect the team was so tired/afraid of being admonished by the Product Owner, they just kept padding and padding their estimates.

Of course, no one bothered to look at the cause of the problem behind the developers massively over-estimating required effort. "The Process" is always right, and the people are always wrong. Isn't that the first principle of the Agile Manifesto (sarcasm intended)?

It's a little difficult to hold conversations with chat while trying to remember what I'm doing with the program. It also feels a little awkward talking to an empty chat (which is what to expect when first starting out). You potentially need to handle spammers and trolls.

On the positive side, I've watched other streaming programmers, and met programmers in chats. We've shared ideas with each other, and it's giving me new ideas and interests. And, it gets me out of my comfort zone, which is the only way to grow.

If it ever becomes more pain than pleasure, I can always stop.