Author: Jud

Technologist interested in building both systems and organizations that are secure, scaleable, cost-effective, and most of all, good for humanity.
Headquarters (Part 2)

Headquarters (Part 2)

Continuing from earlier, this post covers early adulthood, pre-kids.

Year: 2000
Machine: Custom built beige box with NewEgg parts
What I was doing: Enjoying early married life; playing Deus Ex; renting movies from Blockbuster and watching them on my computer’s DVD-ROM drive; organizing documents in that green file box (which I still have).

Year: 2001
Machine: Same beige box but with new guts
What I was doing: starting to explore high-end audio and home theater, applying to Ph.D. programs, anticipating The Fellowship of the Ring.

Years: 2002
Machine: Still the same beige box but a new “flat” monitor
What I was doing: trying to understand Topology, skipping graduate school classes to play Diablo II; anticipating The Two Towers (I still remember waiting for this trailer to download… it was was mind-blowing, despite the low quality of the day).

Year: 2003
Machine: You guessed it, a beige box, though I believe I’d upgraded it yet again
What I was doing: starting a blog on Xanga, anticipating The Return of the King (it was on this setup that I created a postcard inviting 40 of my closest friends to a private midnight screening at the Arena Grand).

Year: 2004
Machine: A second beige box filled with scraped together cast-offs from my main computer, complete with double optical drives
What I was doing: embracing my minimalist tendencies by trying to hide boxy components inside closets and running cables through the walls; ripping my entire CD collection to FLAC; preparing for our first kid.

Headquarters (Part 1)

Headquarters (Part 1)

Here begins my catalog of all the computer setups I’ve had to date (hopefully more visually appealing than this overview I wrote in 2017). Today’s installment: childhood and teens.

Years: 1983-1987
Machines: TI-99/4A
What I was doing: playing cartridge games like Parsec and Munch Man; writing BASIC programs that could test your knowledge of addition and print ASCII art.

Years: 1988-1995
Machines: Three successive Tandy computers: 1000 TL/2 (the only picture I could find from this time), a 386, and a 486
What I was doing: Writing small QuickBasic, C, and Pascal programs; memorizing powers of 2 and digits of Pi; playing Battle Chess and Where in the World is Carmen Sandiego.

Years: 1996-1997
Machines: Custom-built Pentium 2 bought from a computer-fest convention type thing
What I was doing: Discovering online stuff like a local BBS and then the Internet; learning how to assemble computers from parts (shoutout to NewEgg); optimizing my AUTOEXEC.BAT and CONFIG.SYS files so I could play Doom.

(Unfortunately I don’t have any pictures I could find of my college dorm room setups but they were suitably epic, especially junior year which had 3 full workstations and a console game station)

Years: 1998-2000
Machines: Whatever Cedarville supplied (but it was cool that they supplied desktop PCs!); a home-cooked box I cobbled together with parts scrounged from my job at The Hackery.
What I was doing: Breezing through college programming classes in C++, Java, and VisualBasic; optimizing programs that generate interesting integer sequences; playing Diablo and Age of Empires II.

Along the Same Lines

Along the Same Lines

Photographic remembrance continues to be on my mind after watching Black Mirror’s Eulogy. In that spirit, here’s a picture of me I quite like. It captures the energy that I hope I bring to conversations involving the intersection of government policy and technology. I call it “CTO Mode”:

More photos to come in the next couple of days, as I’m finally going to go back and deliver on this promise.

Echoes In Eternity

Echoes In Eternity

As I’ve gotten older, it’s become increasingly important to me to capture (usually digital) relics of what I’ve been up to. Mostly for my own benefit, but it’s a good professional habit regardless.

Five years ago today I was part of a team launching a new website and associated automated phone system helping unemployment insurance claimants at the beginning of the COVID-19 pandemic. I wish I’d done more to document our midnight release event, because it was a pivotal moment in my career. But I do have this one blurry screenshot:

This launch had a trifecta of positivity: a meaningful use case, cool technology, and (most importantly) it all actually worked! I’ve been doing this almost 25 years, and it’s rare to have all that come together. It made such an indelible memory that several of us have found ways to continue working together since.

(Obviously I didn’t get the memo about hoodies; instead opting for formalwear. No regrets on that one!)

Figuratively Speaking

Figuratively Speaking

Speaking effectively to non-technical people can be a challenge for technical folks, but it’s an essential task for all but the most mundane (read: least-effective) of roles. One mechanism that I’ve found helpful is the use of metaphor. I’m a huge fan of trying to describe complex topics by mapping them to more broadly understood concepts. Being able to come up with such mappings fluently is a powerful skill. There may be many ways to develop it, but I suspect one is cultivating a wide set of interests.

While I was writing Tuesday’s post, it occurred to me that today’s Generative AI tools are to software what today’s 3D printers are to physical objects. On one hand, it’s incredible to be able to provide a specification and have it manifested in near real-time. Printers can make a variety of solids: toys, some kinds of replacement parts, that sort of thing. GenAI can create chunks of useful code, quick user interfaces, and basic apps, like my Pinochle scoresheet. But there are limits. Can either of these tools produce high tolerance, precision parts / highly secure, performant code? Can they build complex solutions like electronics / web browsers?

A 3D printer creating a figurine

I could be wrong, but just like we’re a long ways from 3D printing an iPhone, we seem a ways away from vibe coding Microsoft Word or an entire government system of record.

Old Dog, New Tricks

Old Dog, New Tricks

Over two years ago I bought a few domains with the intent of building a tool for keeping track of card game scores. Like many of the best laid plans, I didn’t get around to doing so. Until now.

With the advent of GenAI and “vibe coding” I figured there was no longer any excuse. I spun up Lovable and started prompting. The results? Not bad. Not bad at all. With maybe a dozen prompts and half an hour, you can see the results at onlinescoresheet.net. What was most impressive for me is that I was able to simply ask the model to do Pinochle scoring, and it was able to understand what that meant and implement it without me explaining the rules.

What’s up next? I’d like to generalize the scoring system to be configurable, or at the least add explicit support for a few more game types. I’d also like to dig into the source code to evaluate quality. Should be fun!

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.