Diamonds and Digital Files

Diamonds and Digital Files

I’m a fairly good archivist. Today I happened to be rooting around some old files from college, and found (amongst other things I’m not going to share here) a paper I wrote in 1999 about the leadership style of Thomas J. Watson of IBM. I concluded with this summary that perhaps is still relevant today?

  • One of the most effective ways for a leader to build a cohesive team is to create an organizational culture that binds the employees together.
  • Having a vision for an organization is important, but being able to motivate others to get behind the vision is even more important.
  • Kindness shown to followers goes a long way towards developing loyalty and trust.
  • An autocratic leadership style can be very effective if interpersonal relationships are not ignored.
  • A good leader must not fall into the trap of wanting recognition.

I can mostly still agree, though that bit about autocracy makes me wonder.

Quasi-related factoid: I remember this class well because I pulled an all-nighter right before the final, not to study, but to drive across the state to the Lennox Theater in Columbus to watch The Phantom Menace at midnight. Good times, but a poor choice in retrospect.

Going Small

Going Small

I’ve been an Android user since the original Motorola Droid was released back in 2009. However, last month I finally broke down and made the switch to iOS.

I didn’t buy new, though. Because I don’t like big phones, I found myself a refurbished iPhone 13 Mini. It’s perfect. Sure do wish Apple would acknowledge the ongoing market for small devices, but it seems they’re well and truly dead. Maybe I should get a second Mini as a backup, especially since I’m case-free?

Concerning Hobbits

Concerning Hobbits

We’re all pretty big Lord of the Rings fans in our house, both books and movies. A few months ago we rewatched Return of the King, and I was struck by a couple moments in the dénouement that are worth talking about.

The first is one I’ve loved for a while. The hobbits have returned to the Shire and are together enjoying some well-deserved ales. Their reflective mood is in stark contrast to the conviviality around them, in particular one fellow who is showing off a massive pumpkin he’s grown. Our heroes don’t seem to mind the attention he’s getting; they’re content to sit in silence, apart from the crowd, with nothing more than a toast and some knowing glances.

No one else in that pub understands the grave danger they, and the whole of Middle-earth, were in. No expressions of thanks will come to Frodo, Sam, Merry, and Pippin. But that’s okay. It’s how it’s supposed to be. Leaders make the sacrifices so that those in their care can enjoy their pumpkins, and they seek not the credit. Fellowship amongst a small circle of friends who know the story is enough.

But even within that circle, there’s layers to the levels of awareness. It wasn’t until this most recent viewing that I realized that only Sam knows the full story: that Frodo had fallen at the last to the power of the ring, and its destruction was only completed through earlier mercy shown to Gollum, and some luck.

What Sam chooses to do with this knowledge is worthy of especial praise. When the fellowship is reunited in Rivendell, joy and celebration surround Frodo. Even the wizard Gandalf smiles in approval. Sam is late to the party, but catches Frodo’s eye from across the room.

In that moment, I wonder if Frodo is briefly afraid that Sam will interrupt with a tale of how he had to carry Frodo the final stretch, and that Frodo essentially failed, claiming the ring as his own. It would be the truth. But Sam doesn’t do that, and his expression says he never will. It’s as if he said, “I know that you aren’t a perfect hero. That at the end you did things you’re not proud of, even to me. But you gave everything you had, and the job got done. That’s worth celebrating. Fear not, my friend. Some things are just between us.”

I’m not sure if this is canon, but I imagine no one else, not even Gandalf, ever learned what really went down on the slopes of Mount Doom. That too is okay, because Middle-earth survives regardless. And that’s what ultimately matters.

Up Up And Away

Up Up And Away

Nothing thrills quite like launch day, and this time, it was nearly literal. It’s been a privilege to have been involved in this work, and fun that I can (finally) talk about it in public. I mean, when it’s on the news that’s gotta mean something right? You can check it out right here if you’re so inclined.

Hopefully the above partly explains why I’ve been pretty quiet here. As I said last month: crunch time. It’s certainly not for lack of ideas; sitting on 95 draft posts as I type. Someday I’ll get through the backlog. Or not. But it’ll be okay regardless.

Game Changer

Game Changer

I don’t use that title lightly. Not sure how I’ve never heard of git worktrees before, but I’ll definitely be giving them a spin.

Speaking of git, I don’t normally do a lot of coding in my day job, but crunch time is crunch time:

If nothing else, it’s cathartic to stretch those muscles.

A Little Nudge

A Little Nudge

I’m continually surprised at how much resistance I can put up to learning a new technology when there’s a comfortable equivalent to fall back on, because once I’m finally forced to engage, and get over the initial inertia, I’m typically able to quickly pick up the new skill.

Today’s example: FastAPI. I went from zero to fully-functional serverless stack in an hour. That wasn’t so bad! I probably shouldn’t have wasted any time with my go-to HTTP framework when I was prototyping, though to be fair, their conceptual similarities made porting painless.

Learning to learn fast is a driver of exponential personal growth.

Random Content

Random Content

Last week I stumbled onto this presentation I made for a job interview I did nearly 11 years ago. Python generators are pretty cool! I also dig the vaguely LCARS styling, which was a built-in theme of Google Sheets.

Thought it’d be fun to share here. Enjoy!

(Oh, and in posting this I also learned how to ensure a consistent aspect ratio in CSS. Cool!)

In Brief

In Brief

I like Github gists. They’re perfect for long-term publishing of any code snippet you might want to refer to later, without the overhead of a formal repository. I’ve used them as backing storage for a number of blog posts as well, and will do so again today:

Need to bulk update the contact information across a set of domain names you own in Route 53? I got you. Need to do it across a whole slew of AWS accounts (or anything across a number of accounts)? No problem.

Happy scripting!