A good day for coding

Here’s what it looks like outside:

I didn’t know when this day dawned, but it’s a good day for coding. I’ve been a little off the past several days (quiet, Bruce), so today has been good for me. My time spent searching for and finding a bug, then restructuring a lot of code to get it out of there makes me feel a lot more like a programmer than I ordinarily do. And finishing up with a script that completely validates in PHPStorm? Well that’s just an extra bonus. I love my pretty code.

Another reason this differs from my normal days is that I’m almost doing “forensic coding.” That’s where I have to track down how other peoples’ code from other interacting programs works so I can figure out how to make their process do what I want it to do! There’s probably actually another word or phrase for that, which programmers who work in programming departments know, but I’m just a lonely little web developer, so I don’t know those kinds of things.

So today, I serve the Lord by fixing a piece of a machine I built wrong months ago but didn’t know it until another stresser broke it. At least I think I fixed it. In fact, that’s exactly what this post is for. If it goes through, then I fixed it! Otherwise I’ll copy and paste this into the next attempt.