The Daily Parker

Politics, Weather, Photography, and the Dog

On this day...

May 5th has some history, and not just about a relatively minor battle in Mexico that most Mexicans don't even remember.

For example, two hundred years ago today, Napoleon died and The Guardian was born. I never knew about that coincidence. TIL.

And this morning, Facebook's Oversight Board upheld the social-media company's ban on the XPOTUS, at least for the next six months.

Also TIL that my main programming language, C#, commands 7% of the Internet's mind-share, making it the 4th most-popular programming language. Python, at 30%, is the most popular, because its ease of use (and ease of writing the most godawful spaghetti code imaginable) makes it the preferred language of non-programmers.

I'm glad to see that one of my most-hated languages, Scala, continues its plummet, now even less popular than Visual Basic and and VBA, two languages that should have died during the GWB presidency.

Found an old game. Now what?

Over the weekend, I stooped down to give Cassie some pats while she slept on her bed in my office, and realized I had a cache of turn-of-the-century computer games on a lower shelf. Among them I found SimCity 4, from 2003.

It turns out that SimCity 4, like many games from that era, relies on a thing called "SecuROM" which turned out to have sufficient security problems of its own that Microsoft decided not to support it in Windows 10. I didn't know this until I started researching why the game just...didn't work. When you find a support article that says "96 people have reported this problem" you at least know you're not alone.

So, following the advice in the support article, I opened a support case with Electronic Arts. We are now on a 24-hour cycle of them asking me to send back auto-generated codes to prove I'm an actual person with an actual copy of the SimCity 4 CD. This, after it took three rounds with their automated systems to set up a support account. The merry-go-round with their automated systems was irritating, but the 24-hour cycle time between emails just makes me laugh. I haven't actually taken the time 

After all that, I may actually play SimCity for the first time in 17 years at some point this month. I can't wait to see how a game designed for Pentium 4 processors and 256 MB of RAM performs on a Xeon 6C with 40 GB available...

Lunchtime reading before heading outside

Today is not only the 35th anniversary of the Chernobyl disaster, it's also the 84th anniversary of the Nazi bombing of Guernica. Happy days, happy days.

In today's news, however:

I will now get lunch. And since it's 17°C right now (as opposed to yesterday's 5°C), I may eat it outside.

What a difference a small change can make

I've just made a change to the side project I'm working on that will reduce my database costs about 94%. Maybe 96%. This is only in the dev/test environment, so it may make less of a difference in production, but still... Sometimes taking something out of your code can make an enormous difference.

I promise I'll write a lot about what I've been working on once it launches.

Sure Happy It's Thursday! Earth Day edition

Happy 51st Earth Day! In honor of that, today's first story has nothing to do with Earth:

Finally, it looks like I'll have some really cool news to share about my own software in just a couple of weeks. Stay tuned!

Wait, what?

The United States Postal Service has a surveillance program that tracks social media posts for law enforcement, and no one can say why:

The details of the surveillance effort, known as iCOP, or Internet Covert Operations Program, have not previously been made public. The work involves having analysts trawl through social media sites to look for what the document describes as “inflammatory” postings and then sharing that information across government agencies.

“Analysts with the United States Postal Inspection Service (USPIS) Internet Covert Operations Program (iCOP) monitored significant activity regarding planned protests occurring internationally and domestically on March 20, 2021,” says the March 16 government bulletin, marked as “law enforcement sensitive” and distributed through the Department of Homeland Security’s fusion centers. “Locations and times have been identified for these protests, which are being distributed online across multiple social media platforms, to include right-wing leaning Parler and Telegram accounts.”

When contacted by Yahoo News, civil liberties experts expressed alarm at the post office’s surveillance program. “It’s a mystery,” said University of Chicago law professor Geoffrey Stone, whom President Barack Obama appointed to review the National Security Agency’s bulk data collection in the wake of the Edward Snowden leaks. “I don’t understand why the government would go to the Postal Service for examining the internet for security issues.”

I mean, scraping social media takes only a modicum of technical skills. In the last year I've written software that can scan Twitter and run detailed sentiment analysis on keyword-based searches. But I'm not a government agency with arrest powers. Or, you know, a constitutional mandate to deliver the mail.

Weird.

Git yourself over here

Stack Overflow recently had a good blog entry on Git branching:

When trying to imagine how branches work, it’s tempting to use the concept of “folders.” After all, creating a new branch feels very much like copying the project’s current state and pasting it into a new, separate folder.

But part of the genius behind Git is that it doesn’t just “copy all contents” of your project, which would make things slow and use up lots of disk space. It’s much smarter than that!

[C]ommits in Git are identified by their SHA-1 hash, those 40-character long, cryptic strings. These commit hashes are static and immutable. Branches, on the other hand, are highly flexible, always changing to the commit hash of the latest commit anytime you create a new commit in that branch.

Speaking of Git, I'm moving to the next phase of my big at-home project. The end, while not in sight exactly, has gotten much more predictable. (In software, predictability is a good thing.)

Ten years ago

Just a quick note: I'm halfway to the "20 years from now" I mentioned in this post from 13 April 2011. And as I'm engaged in two software projects right now—one for work, one for me—that have me re-thinking all of the application design skills I learned in the 10 years leading up to that 2011 post, I can only hope that I'm not walking down a technological cul-de-sac the way Data General did in 1978.

Sunday not-so-funday

Bit of a frustrating day, today. I spent 2½ hours trying to deploy an Azure function using the Az package in PowerShell, before giving up and going back to the AzureCLI. All of this to confirm a massive performance issue that I suspected but needed to see in a setting that eliminated network throughput as a possible factor. Yep: running everything completely within Azure sped it up by 11%, meaning an architecture choice I made a long time ago is definitely the problem. I factored the code well enough that I can replace the offending structure with a faster one in a couple of hours, but it's a springtime Sunday, so I don't really feel totally motivated right now to do so.

Lest you worry I have neglected other responsibilities, Cassie already got over an hour of walks and dog park time today, bringing her up to 10½ hours for the week. I plan to take her on another 45-minute walk in an hour or so. Last week she got almost 14 hours of walks, however. I blame the mid-week rain we got.

I also have a 30-minute task that will involve 15 minutes of setup, 10 minutes of tear-down, and 5 minutes of video recording. I will be so relieved next fall when all of our chorus work happens in person again.

Before I do that, however, I'm going to go hug my dog.