Eighteen Speed Upgrade

Eighteen Speed Upgrade

A couple of months ago, on a whim, I applied to a training fellows program. I ended up not seriously pursuing it because of an already full “day job” workload, but to be considered I had to write an argument for why I’d make a good trainer. Thought I’d post it here for posterity:

I’ve been communicating technical topics to varied audiences my entire career across a number of dimensions. As both an individual contributor and manager I have:

  • Sat alongside Air Force crew members in flight to teach them how to operate a map display I implemented
  • Designed and led classes for technical writers to teach them computing fundamentals (including complex cryptography topics) and how they relate to electronic voting systems
  • Run workshops within Amazon Web Services on my approach to passing cloud certifications (I’ve also written about that here)
  • Mentored numerous junior and mid-level developers on how to make the transition to technical leadership (see thoughts I wrote on it here)
  • Embraced “learning in public” by writing on technical topics as I explored them, for example, Know Thyself (and my blog in general)

Further, the last 5 years of my career have been in a direct consulting capacity, where I routinely interact with both business and IT leaders at the C-suite equivalent level in state and local government to show them how cloud technology can transform and improve the services they offer their residents. I’ve done this both as a leader within a large organization (AWS) and as CTO of a small organization. I have extensive recommendations on LinkedIn that back this up.

None of this experience would matter, though, if I didn’t want to see others learn and grow. I’ve worked to cultivate a joy that comes from seeing others succeed vs just enjoying what my own two hands can build, which I wrote about here.

Paved Paradise

Paved Paradise

One of the things I tried to do when I was a manager at AWS was connect members of my team to the broader internal community. Generally I found that, when asked, most folks were willing to jump on a call and share their wisdom and perspective from a different portion of the company.

In a particularly memorable such conversation, I’d invited Becky Weiss to present at one of my team meetings. I won’t forget something she shared that day: her love for a particular AWS service, what it enabled for experimentation and learning, and how unique an opportunity it was to have it available to us, because it was internal only (a fact Corey Quinn has bemoaned).

I took it for granted at the time, which was a mistake. Sure could benefit from it now.

They Who Pass The Sentence

They Who Pass The Sentence

That feeling when I run terraform apply in production:

Thankfully I’ve never had an outcome quite this dire, but I’ve seen databases go up in smoke, amongst other infrastructure-as-code disasters. Tread lightly!

Oh, The Places You’ll Go!

Oh, The Places You’ll Go!

Today marks the 10th anniversary of this blog. It’s been quite the career journey since I sat down to write my first post, appropriately titled Hello World.

At that time, I was sitting in a drab cubicle in a perfectly ordinary office building, probably gingerly sipping a cup of coffee (I didn’t start drinking coffee until about that time, if you can believe it) and getting ready to start my day of rewriting a large Perl application to meet a silly set of coding standards.

At least the conference room was kinda cool

Today, I sit writing this in the Rose Reading Room of the New York Public Library, about to embark on a morning of (hopefully) focused effort to provide architectural guidance and documentation feedback on a couple projects I’m overseeing. In the afternoon, I have a project kickoff to attend, and will likely have a smattering of emails and Slack messages to respond to.

Not a half bad backdrop

Such is the life of a CTO. Gone are the days of 9-5 coding. Little did I know back when I started writing here (let alone 25 years ago when I was earning my computer science degree) where my career would be headed or what it would entail on a day-to-day basis. But that’s pretty normal it seems.

If you’re here, thanks for reading. I hope to keep doing it for another 10 years. But for now, time to get back to the day job.

2 + 2 = 4

2 + 2 = 4

I talk often about Conway’s Law, both here and in real life. I also talk often about working in the public sector. But for some reason I’ve never mentally put the two topics together and drawn the inevitable conclusion discussed in this article: Conway’s Law at Government Scale.

I’ve read Recoding America, and generally agree with the notion that a product operating model makes sense and leads to better outcomes. But here’s the thing: change comes slowly, if it comes at all, and solutions are needed now, across many domains.

I’m grateful for the work of those whose role is to reorganize and rethink government, and wish them success. But in the meantime, I see my role as working within the structures that exist now and doing the best that can be done. Projects can succeed, even with constraints.

Patience Isn’t A Virtue

Patience Isn’t A Virtue

I’ve had space on the brain recently, having in the last month visited both the Jet Propulsion Laboratory and the Johnson Space Center. There’s a paradox of sorts when thinking about interstellar travel called the wait calculation (or, in simpler form, the wait/walk dilemma). The gist is that we should not launch a slow spacecraft now because one sent later with a faster propulsion system would simply overtake it. Repeat that argument ad infinitum, and you’ll never launch, hence the paradox.

These days I’m feeling caught in a similar sort of trap when it comes to learning about AI, with announcements almost daily (just this week, GPT-5 launched, right on the heels of the release of a bunch of open weight models that can run all sorts of places, including Amazon Bedrock). Just when I think I’ve identified the technology I want to really embrace, new ones arrive that create new capabilities, deprecate old ones, and demand rethinking workflows. It’s disorienting.

You know what isn’t disorienting? Photos of cool command centers. Here’s three of them from my recent travels:

The room where it happened
The room where it’s been happening a while
The room where it’s still happening

I’m a sucker for a good command center, that’s for sure. But enough distractions; I know I just need to dig into deeper AI learning. That’s the trick: just start.

Covering the Bases

Covering the Bases

Dropdowns in web forms are generally good; they make it simpler for users to input options correctly and ensure back-end data integrity. They can be limiting at times, though, so I have to respect an event registration website I used yesterday that tried to be all-encompassing in the selections for “Title”:

Henceforth I expect to be addressed as “Lord Neer”

I have to imagine this list came from some out-of-the-box form generation tool. Or created by GenAI, perhaps? I’m curious what it could have been. And was it not modifiable? Suffice it to say several of the choices are fairly pretentious given the event I was buying tickets for, so I feel like maybe the developer should have looked into culling the list.

Never Forget

Never Forget

Technologists love to collect and share horror stories (see, for example, The Daily WTF). It’s one of the reasons this blog exists, as a brag document of a different sort.

No matter how stressful the situation may be, no matter how long the debugging session took, no matter how brain-melting the eventual solution was to implement, on those days when you experience a moment that you know will go into the annals of “how the heck did this happen” infamy, it brings a smile to your face.

For me, yesterday was one of those days.

It’s a little too early to tell the full story in a public place (the key stakeholders should get to hear it first), but I hope to eventually. It’s an all-time head-scratcher.

Off The Cuff

Off The Cuff

Despite having had a number of opportunities to do so throughout my career, I’ve never progressed beyond being an average public speaker.

Thankfully I don’t have any particular phobias about it, and I can do a decent job relaying facts while being mildly interesting, but I’m far from a great orator, especially when I have to speak on the fly.

Still, every once in a while I’m happy with my ad libbing. This past week I spoke at a conference, and came up with this turn of phrase that I quite liked:

Universal problems are often best-solved through many local partnerships.

Perhaps that’s why I enjoy building for state government so much?