...will be to Bletchley Park:
The National Museum of Computing is a must-see if you are ever in the UK. It was a short 30ish minute train ride up from London. We spent the whole afternoon there.
There is a rebuild of the Colossus, the the world's first electronic computer. It had a single purpose: to help decipher the Lorenz-encrypted (Tunny) messages between Hitler and his generals during World War II. The Colossus Gallery housing the rebuild of Colossus tells that remarkable story.
We saw the Turing-Welchman Bombe machine, an electro-mechanical device used to break Enigma-enciphered messages about enemy military operations during the Second World War. They offer guided tours (recommended as the volunteers have encyclopedic knowledge) and we were able to encrypt a message with the German Enigma (there's a 90 second video I made, here) and decrypt it with the Bombe, which is effectively 12 Engimas working in parallel, backwards.
I wanted to understand the computing power these systems had then, and now. Check out the website where you can learn about the OctaPi - a Raspberry Pi array of eight Pis working together to brute-force Engima. You can make your own here!
Yes, there's a Raspberry Pi Enigma-cracker. If only we'd had one in 1940...
The official temperature at O'Hare got down to -31°C before 7am. Here at IDTWHQ it's -28.4°C. We didn't hit the all-time record (-32.8C) set in 1985, but wait! We will likely hit the low-maximum temperature record today.
WGN reports that temperatures under -29°C have occurred only 15 times since records began 54,020 days ago.
And the Wiccan coven next door has just received a shipment of battery-heated, thermal-insulated sports bras.
So, I'll be working from the IDTWHQ today. And tomorrow.
This review of music notation software Sibelius starts out normally...but then...
I'm happy to announce that I started a new role on the 14th at Rally Health, a software company wholly owned by United Health Group. I'll have more to say later (still figuring out the social media policies), but for now I can say, look at the view:
And here's the view from the north:
Today, by the way, is the first day since I started that we've had anything approaching full sunlight. Of course, it's frighteningly cold out, but hey: nice view.
(I'll update Facebook and LinkedIn over the weekend, for those of you who care about those things.)
As readers have inferred, I've started a new position (more later), and with that I've got to set up a new work computer. I say "computer," but it's actually a MacBook Pro. All of my everything lives in the Microsoft universe. This has caused a slight problem trying to get access to my new company's source code in GitHub.
See, I've used Password Safe for years to manage all my passwords. By "all" I mean that I follow the standard industry practice of never re-using passwords, and generating strong passwords for each asset. This includes my GitHub account.
Today I finally got my existing GitHub account authorized to access the company's repositories. So all I have to do is log in to my GitHub account, and...wait...crap.
So how do I get my GitHub password? Here are the steps I tried:
- My safe file is on OneDrive, so I can get it off my phone and email it to my work address. No problem there.
- But PWSafe is a Windows application. There isn't a Mac version available through the same vendor.
- There is a Mac version through a different vendor—for $15. OK, let me rule out all the free options first.
- Aha! I have a virtual machine sitting in Microsoft Azure that I can spin up. It has access to OneDrive and it has a local copy of PWSafe already installed.
- Log into the Microsoft Azure portal.
- Spin up VM.
- Google how to connect to it from a Mac. (Microsoft has a client available through the iTunes store.)
- Go to the App Store on my Mac.
- Find the RDP client.
- Attempt to install the RDP client.
- Dammit. I have to set up a new Apple ID because my personal Apple ID is—you guessed it—in the safe.
- Set up a new Apple ID for work.
- Actually install the RDP client this time.
- Realize that the password for the VM is—you guessed it—in the safe.
- Shut down the VM for now.
- Jot down a note to add my GitHub account to LastPass so I can get into it from work.
- Jot down another note to add my VM credentials to LastPass.
- Get more tea.
- Blog about this.
Oh well. I have plenty to do this afternoon that doesn't involve writing software.
I missed posting two days in a row because I've just been swamped. I'll have more details later. For now, here's my new office view:
One of my smartass friends, who lives in Los Angeles, asked what that white stuff was. It's character, kid. It's character.
Let me elaborate on last night's post.
Microsoft has two flavors of .NET right now: the .NET Framework, which has been in production since February 2002, and .NET Core, which came out in June 2016. .NET Core implements the .NET Standard, which defines a set of APIs that any .NET application can use.
Here's the problem: The 18-year-old Framework has a lot more in it than the 2-year-old Standard specification or Core implementations. So while all .NET Standard and Core code works with the .NET Framework, not all Fx code works with Core.
Where this bit me over the weekend is dealing with Microsoft Azure Tables. I store almost all the data in Weather Now in Tables, because it's a lot of data that doesn't get read a lot—Tables' primary use case. There are .NET Standard implementations of Azure Storage Blob, Azure Queues, and Azure Files...but not Azure Tables. The latest implementation of Microsoft.Azure.CosmosDB.Table only supports the .NET Framework.
And that's a problem, because the new version of the Inner Drive Framework will follow .NET Standard 2.0 (or 3.0, if it comes out soon).
So yesterday I spent an hour going in circles before finally getting a definitive answer on this point.
Support for Azure Tables will happen soon enough, and I have a lot of documentation to write before the new Framework is ready for prime time. But I really wanted to tie a bow on it this weekend.
I'm mostly done with a major revision to the Inner Drive Framework, and I've discovered, to my horror, that one part can't be done yet. Microsoft Azure Table support doesn't work with .NET Standard yet.
This will make more sense at some point soon.
Another problem with open-plan office spaces, according to comedian JiJi Lee: it's hard to find a place to sob. She suggests some:
By your C.E.O.’s work station: Flatten hierarchies by sobbing in front of your company leader. Open offices were made to foster communication, so introduce yourself and say, “Hi, I'll never make as much money as you!”
The center of the office: The company doesn’t believe in walls, so why build one around your emotions? Let it go and play the “Frozen” soundtrack while you’re at it. Do a cartwheel that turns into a split and then cry onto Colleen’s emotional support dog. You have the space for it! After all, the company wanted to increase productivity and you’ve never been more efficient with your crying in your life.
The restroom: This is where everyone goes to cry. Anticipate long lines.
At least my office has a coat closet. But it's very small.