Everybody’s Got One

If you woke up this morning hoping for one more person’s take on all this ‘AI’ stuff, I guess it’s your lucky day.

You won’t find a(nother) rant about how large language models (LLMs) aren’t all that ‘intelligent’, how they pose an existential risk to humanity, make people dumber, are eroding our ability to build and maintain software, are eliminating millions of jobs thereby upending the global economy, or how the whole thing is a bubble floating over a pyramid (scheme) and built entirely on theft.

All of those things seem true to me to varying degrees (especially the theft part), but that’s not what this is about. So if a rant about one of those what you’re looking for, best keep looking.

Ok, I said no rant. I lied. For the record, I utterly abhor that a small number of sociopaths are building empires and fortunes based on what can only be described as blatant and intentional theft. It’s not the first time this has happened – see: robber barons – and it probably won’t be the last. But these people are “sorta my people” and my small part in enabling this reality fills me with no small amount of regret. Even if AI ends up being amazing (and to me the jury is most definitely still out), the original sin will remain.

If you’re early in a career in software and looking for guidance, or predictions about the course of the industry, there are lots of places to look. If you’re well into that career arc and trying to orient and navigate there are no shortage of thought-provoking and often depressing perspectives to consider.

If you’re looking to understand how these chat bots (and the large language models they’re built on) do the seemingly magical things they do, take a few hours (!) and let Andrej Karpathy explain.

All I’m offering is a (hopefully cogent and coherent) exposition of what’s in my head.

Caveat emptor.

I’m not an Artificial Intelligence expert. Like others “of that age” I had a dream of teaching machines to think. In my teens I voraciously consumed science fiction, read futurists like Hans Moravec, and was convinced we were probably “really close” to being able to build thinking machines. For a while I considered studying cognitive neuroscience on top of computer science, but realized it was probably biting off more than I could comfortably chew.

I was interested enough to do some related coursework during my computer science undergraduate, in the mid 90’s. At the time the practical state of the AI art were things like expert systems, and there was a bit of an “is it/isn’t it” tug-of-war with the information retrieval folks who focused on organizing information in ontologies and graphs. Image recognition and natural language processing were unsolved areas of active research, and you could tell the “AI people” ‘cause they wrote code in Prolog or Lisp.

I ended up being pretty disillusioned by the state of the art and didn’t give it much more time or attention for years.

I started paying attention again around ten years ago. Advances in compute (and a bit in algorithms) made things that had been “impossible” (or at least impractical) suddenly possible or “adjacent possible.” This was right around the time a bunch of non-PC gamers started to care about GPUs (Graphics Processing Units).

Since then I’ve built stuff – and helped teams build stuff – using machine learning (a term I strongly prefer over “AI”), and I’ve built and trained small models, and used the current (recent?) crop of large language models enough to have a sense of their current capabilities and limitations.

So I guess I’d describe myself as “not completely clueless.”

So… “AI.” Let’s start with two dirty little secrets.

Dirty-little-secret #1: In the decades I’ve been in the software industry, I’ve rarely loved the act of writing code.

I loved (and still love, mostly) solving problems for people who couldn’t solve those problems themselves. Writing code was a means to that end – not the end.

I didn’t hate writing code, but knowing I’d figured out a solution was the really rewarding bit. And (or maybe “So”) I was really never “the best coder” in a group. I was a “pretty good programmer” and I worked to develop good habits that let me collaborate with people who were better than me and only rarely feel like the idiot holding us back.

I also had some experience early in my career that forced me to realize that over time – especially as the people who wrote it disperse – code becomes more of a liability than an asset. So, in the long term, less can very much be more.

Dirty-little-secret #2: One of my few persistent “career goals” has been to put myself out of a job. To make my role unnecessary. I think of it as being “lazy in the long term” – willing to work hard on a problem today so I can stop working on or even thinking about that problem entirely “tomorrow.”

Despite the marketing hype, the current generation of LLM-based tools don’t have the potential to make “people like me” obsolete. What they do have is the potential to drastically reduce the number of people who need “people like me” to help them solve problems with computers and technology.

In a world that “software ate,” but where most people can’t self-service their software needs, these tools have tons of potential for disintermediation and empowerment. Disintermediation and empowerment seem good.

So you might think I’d be loving these tools.

I thought I would, too.

But, it turns out, I do not.

That’s not to say I hate them. I don’t. The opposite of love isn’t hate.  It’s indifference.

On a personal level, I’m mostly indifferent.

On the broader implications and impact of these tools and technologies it’s closer to say that I’m ambivalent, and from a professional perspective not actively embracing AI is potentially problematic. Those are both topics for another time.

I’ve come to realize that I just don’t enjoy using these tools, and I really struggle to convince myself that the value they have is worth their costs. (NB: Their actual costs. Not just the loss-leading “we’ll make it up in volume” fistfuls of dollars each month they’re priced at today.)

They’re too often opaque, capricious and unpredictable. making it unwise to trust their results.  That makes me not reach for them to answer questions, or solve problems, unless I’m already confident I know the answer.

I think about the output from an LLM as I might the writings of a hard-line political pundit. Everything has to be skeptically considered. Everything has to be fact checked. It turns out that without chasing the footnotes, you’ll never know if the reference material really says that, or even if it exists.

Maintaining the appropriate level of skepticism is real work.

I find that these tools transform work but don’t reliably reduce or eliminate it.

They turn writing English into reading and re-writing English.

They turn writing code into reading reasoning about and fixing code.

They turn fact and knowledge seeking into, well, fact and knowledge seeking.

Don’t read this as me saying these tools have no value. That’s not my point at all. I’m making a bounded statement about my experiences with these tools.

The other thing I’ve learned, which surprised me at first, is that using an LLM to answer a question, or write code, or solve a problem makes me feel … nothing.

I was drawn to computing, and ultimately studied and pursued it as a profession, because I found it rewarding. Not just financially – though getting well paid to do something I enjoyed was certainly not a bad thing. Solving problems – especially tricky problems – feeds my brain endorphins.

And who doesn’t love endorphins, right?

I love learning, and each time I attack a problem – win or lose – it changes me a bit. Teaches me something.

I get none of those rewards when I use these tools. The victory feels hollow. As if I’ve cheated. Or have been cheated.

A friend and former colleague said we’ve “…largely become a culture of answer seekers, not knowledge seekers. We want the answer, but don’t particularly care to understand why or how. This was a problem before AI.”

I think he’s right, and his observation touches a nerve. One of my most valuable (and most irritating) habits was instilled in me at a young age by my uncle Denis – an actual working scientist who told me to “Always ask why.”

Supressing that impulse, lessening the drive to understand, makes me… sad.

I stumbled across an analogy that resonated with me – using language models and chat bots to write or solve “thinking” problems for you, this author said, is like bringing a forklift to the gym to lift weights. If your only goal is to lift the weights, fantastic, job done – provided the model doesn’t drop the weight on someone’s toes, or decide to drive through the locker room instead. But if any part of the goal is to become a person who can lift weights … learning to drive a forklift is becoming someone who can drive a forklift, not someone who can lift weights.

If what you need to do is move lots of heavy things, over and over, day in and day out, and that’s all there is, by all means use a forklift. Just realize that what you’re getting good at is driving a forklift.

This might lead you to ask the entirely reasonable – “so what?”

Well, from a personal perspective, I just don’t use these tools much. I don’t pay for a chatbot and don’t imagine that changing. I occasionally ask Gemini questions – when it’s not outright fabricating things the model is pretty good at summarization. I’ve had Claude write code – especially when I already know what the code needs to do and the cost of verifying it’s “done it right” is lower than the cost of me just doing it.

But I don’t use AI every day. Or even most days.

I don’t ask a chatbot for feedback on my writing, for instance. I write it, read it, revise it, and sometimes ask other people to read and critique it too. So my writing has occasional typos, sometimes mixes metaphors (thanks, Matt!), and can be a bit awkward.

And that’s ok.

Over the years I’ve been writing, I’ve gotten better at it – and the point isn’t just to lift the weights.

We Are What We Do

There’s a quote, (mis)attributed to Aristotle, that begins “we are what we repeatedly do…” I’ve always like the quote for its resolution – “excellence, then, is not an act but a habit.”

Lately the first bit, and what it captures about our odd relationship with work, has been on my mind (for probably self-evident reasons).

Most of us spend most of our time “at work” – it’s literally what we repeatedly do – and for many of us it becomes a defining aspect of self.

“I’m a carpenter.”

“I’m a lawyer.”

“I’m a nurse.”

“I’m a software engineer.”

It’s right there, hidden in the contraction. We’re not saying I do, we’re saying I am.

And yet, at the same time, most of us look forward to the day we can choose to stop.

Maybe you’re not “most of us.” Maybe you’re someone who – like a former colleague of mine – “would do this [job] for free.” If that’s you, I’m not sure this will make much sense. Sorry.

The question that’s been rattling around in my head lately is “If we are what we do, and mostly what we do is work, what are we when we’re not working – when we aren’t doing?”

I grew up in a “vanishing middle class” family. Both my parents spent their working years working “for someone else” – and nearly all of my friend’s parents did, too – so it’s probably my plebeian background that makes being able to opt out of someone else having claim to most of my time – while continuing to maintain a comfortable lifestyle – feel like an incredible luxury.

At the same time, prioritization was a recurring theme in my up-bringing. It wasn’t always explicitly talked about as prioritization, but in retrospect prioritization was the kernel of many of the lessons my parents worked to impart. Time was a scarce and finite resource, so you did what needed doing first, and once that was done you did what you wanted with whatever time was left.

If you don’t eat your meat, you can’t have any pudding. That sort of thing.

I internalized that lesson really well. Maybe too well. I remember times as a kid, being burned out working on some “needs doing” thing – like homework – and not letting myself take a break. Even though a short break would would likely let me get done faster and better. Because this thing needed doing, and “needs doing” things come first.

Somewhere along the way – probably in college, when all the things that needed doing would overflow the available time – I got more intentional about prioritization. I stopped just thinking about something “needing doing” and started thinking about what would be “the best, most valuable, use” of my limited time.

What was “valuable” was a bit … subjective. Learning was valuable, so reading – even fiction – qualified. So did spending time with friends, almost irrespective of what we did with that time, as long as it was interactive. Watching TV was not valuable (unless it was what Dawnise and I have come to call “edutainment” on PBS). Ditto video games, which basically never qualified. On the other hand, “needs doing” things were valuable unless proven otherwise.

Where did that leave “work?” It turned out that many of the things I wanted to do required money. And since I didn’t have the foresight and fortune to be born into a wealthy family, work was how one got money.

One of the interview questions I used to ask software folks just starting out in the industry was “where does your paycheck come from?” It’s not a trick question – the goal was to see if they could turn their mental crank enough to get to some version of “the work I do is valuable to someone, that someone trades money for that value, and my paycheck is some of that money.”

So work, by definition, is (must be) valuable. Or, put another way, if the work you’re doing isn’t valuable to someone, you probably won’t be doing it gainfully for long. The Faustian bit is that to get money, you trade time – and the more time you trade for money, the less you have left to do the things the money lets you do.

All of that comes back around to me, having stepped away from full time work “for a while,” not having a particularly satisfying answer to the question “what do you do?”

I’ve tried “I’m on a sabbatical,” “I’m taking a career break,” and even “I’m test-driving retirement.” They’re all basically true, and they all trigger the same follow-up: “what did you do?” which often quickly segues into “how do you fill your time now?”

It’s not unreasonable to ask. To try to find some sort of handle on “me.”

What’s surprising, and doesn’t feel entirely reasonable, is my emotional response.

The question makes me angsty.

Because, at least right now, all the answers I have fly in the face of a deep seated long standing belief that I should be doing “something valuable.”

It turns out I’m basically still that kid. Still struggling to take a break from my homework, despite knowing a break is sensible.

I’m really not sure how I fix this. It’s been “me” for as long as I remember. That doesn’t mean it’s right, it just means it’s hard to change.

Perhaps the nagging voice in my head is right – perhaps I do need to “find something valuable to do.” Either by deciding that something I want to do is valuable, or by finding something that’s valuable and deciding I want to do it.

Or perhaps I need to ignore this feeling for a bit and see if it goes away…

One Day It’s Fine, and Next It’s Black

For the past few months I’ve been working with some like-minded watch enthusiast colleagues, and a couple of UK watch companies, on a design for a custom Axon watch. We’re getting really close to taking orders, so I posted about the project in a company wide Slack channel.

A colleague, who knows I’m leaving the company, messaged me and asked:

“Are you gonna buy one, or is the brand toxic now?”

I honestly didn’t find the question terribly surprising. What I found a little surprising was that I hadn’t really considered not buying one of the watches we were working on – even though I’ll be long gone from the company before it’s delivered. (Bespoke watches don’t happen overnight. It’s months between order and delivery.)

It’s tempting, and not entirely unreasonable really, to blame this on my watch … enthusiasm. Or on some variant of sunk cost – since I’d done most of the work on the project.

But I don’t think it’s either of those.

I think it’s an aspect of Annie Duke’s insight, that the right time to quit feels like quitting too soon, and that by the time it’s obvious you need to quit, you’ve waited too long.

We’ve probably all known people who’ve stayed at a company, or in a relationship, long past the point we think they’d be happier elsewhere.

We might be wrong… but we might also be right, and something is making them stay: a paycheck, or the promise of a payday around the corner; colleagues and friends they don’t want to lose contact with; the sense of prestige that comes from their title and role at a big-name firm that’s woven itself into their sense of self.

Whatever the reasons, they persist long past their “sell-by date.” And the motivation, belief, passion and commitment they used to feel twists and changes.

By the time they make the decision to quit – or the decision is made for them – all that’s left is disdain and a lingering sense of betrayal. That this was done to them. And that feeling colors everything that came before.

Many of us have experienced this a least once. For some of us it’s the experience every time we leave a job, or a relationship.

Acrimony and scorched earth.

I responded that I totally intend to buy a watch, and said “I’m not leaving ’cause I hate this place, I’m leaving ’cause my bet is that I’ll be ‘better out than in.’”

That led to a conversation about … all of this stuff. And specifically about how, for many of us, by the time we leave we’ve come to dislike the thing we’re leaving – at least a little.

I think we get there in the normal two ways – “gradually, then suddenly.”

The trick is to notice the “gradually” bit.

To spot that you’ve stepped onto a path that ends with wanting to burn everything to the ground.

My best advice, when you realize you’re on that path – when you notice that you’re keeping track of where the sticks & the marshmallows are in anticipation of the coming conflagration – is figure out how to fix it, or figure out how to leave.

It’s critical in those moments to remember that – job or relationship – past you chose to do this. It wasn’t done to you. It was your choice. Your decision. It seemed like the right thing to do at the time.

Things change. This version of this thing maybe isn’t the thing you’d choose, if you were choosing now.

That’s okay.

The best thing you can do now, to borrow some wisdom shared with me, is “wake up smarter,” and make a different choice.

Not with a bang…

Early in my career I had an uncomfortable couple months that taught me that the correct number of times to decide to leave a company is once.

Sometimes you can get away with twice.

More than twice is almost always a bad idea.

So having decided (again) to leave Axon, I don’t expect there to be another do-over.

I did some thinking while we were traveling over the holidays and came to realize that while I still want to be doing something, I was less and less confident that what I was doing was that something.

Annie Duke, professional poker player turned author, describes quitting as a prediction problem. You should quit, she argues, when you’d bet that your future not doing the thing is going to be better than your future continuing to do it. Sh argues that it often feels like we’re quitting too soon – but that if you wait long enough to be sure quitting is the right move, you’ve probably waited too long.

By the time we got home I’d thought about it as much as I thought thinking about it could help.

All that was left was to place a bet.

Stupidity Should be Isolating

Sometime last year, quite by accident, Dawnise and I found ourselves looking at Edward Jenner’s house over his garden gate.

Jenner may not be a household name, none the less his work pioneering vaccination has literally – no hyperbole or exaggeration – saved countless lives.

Vaccination isn’t perfect. Vaccination isn’t infallible. Vaccination saves lives.

We know all of these things to be true beyond any reasonable doubt.

We know that vaccination saves lives. In the immortal words of Richard Dawkins, “it works, bitches.

A wise magician described science as, “a careful, disciplined, logical search for knowledge about any and all aspects of the universe, obtained by examination of the best available evidence and always subject to correction and improvement upon discovery of better evidence.”

“What’s left,” he went on to say, “is magic. And it doesn’t work.”

Along with millions and millions of other people, I’m likely alive because I’ve been vaccinated against a cadre of diseases that could have killed me in infancy. And my parents, and likely their parents, were vaccinated against diseases they subsequently didn’t get.

Diseases that didn’t kill them. Didn’t maim or cripple them. Or change the course of their lives.

The diseases we routinely vaccinate against have become vanishingly rare in vaccinated populations.

Which is entirely the point.

They’ve become rare enough that many of us have never seen someone affected by any of them. Rare enough that some of us have the luxury of asserting the threat of those diseases isn’t real.

We’ve succeeded in making these afflictions rare enough that we’ve collectively forgotten that not very long ago tens of thousands of people contracted paralytic poliomyelitis each year. We’ve forgotten what a hospital ward full of people who need iron lungs to breathe looks like.

Rare enough that some of us believe, despite a preponderance of evidence, that the risk of being vaccinated outweighs the risk of the disease.

The universe, of course, doesn’t give a toss what nonsense you believe.

Thanks to some of the physicians in charge of America’s vaccination advisory committee – like Dr. Kirk Milhoan – who believes that an individual’s right to choose takes primacy over public health – we may soon have a chance to refresh our collective memory.

“Good news, everyone!”

For the record, I believe he’s wrong. And I believe everyone – not just the people who follow his advice and “exercise their right to choose” – are worse off for having people like him in positions of authority.

I also don’t for a moment believe any argument will change his mind.

His position isn’t objective, or rational. It’s not likely to change when confronted with evidence, or a well reasoned argument. Anyway, assuming for a moment he didn’t get his medical degree from a box of Cracker Jack he’s surely seen the data. He’s surely studied the evidence.

And he’s chosen to value individual choice over collective benefit.

Or perhaps he’s betting on magic over science.

He might as well argue that it should be a surgeon’s choice whether they scrub in for a procedure. Or that it’s a a city’s choice to keep sewage out of the drinking water supply.

After all, the “germ theory of disease” is just a theory.

Of course theory doesn’t mean “personal belief,” or even “someone’s wild-assed guess.” A theory – about anything – is the best explanation we currently have – consistent with all the evidence we currently have. A theory helps us reason about and ultimately understand the thing in question.

Doctors, of all people, know this. Doctors, and engineers, are the people who most directly put science into practice. They use it to solve (and prevent) real problems. They use it to hopefully make the world a little better.

So it absolutely infuriates me that he has the nerve – the utter fucking audacity – to call himself a doctor while actively undermining one of the most effective tools we have to protect health. He’s encouraging people in his care – people who look to doctors for trustworthy advice and guidance – to forgo the best protection against these diseases science has.

<deep breath>

So be it.

As America chooses to turn its back on vaccination, no other country can force them to reverse course.

What other countries can do, and should do, is work to ensure that their populations are protected from America’s choices.

The risks from an individual choice to be unvaccinated absolutely shouldn’t be imposed on others.

Acountry might, for instance, make proof of vaccination against diseases they routinely vaccinate against a prerequisite for crossing their border.

Want to enter such a country? Show evidence that you’ve been vaccinated.

Each time Dawnise and I have relocated internationally, proof of vaccination against some set of things has been demanded as part of our entry paperwork. No vaccination, no entry visa.

During the COVID pandemic we demonstrated that it’s completely possible to scale those inspection mechanisms up to everyone traveling between countries.

Many of us don’t have ready proof of childhood vaccination. The straightforward answer is to get re-vaccinated.

Getting (re)vaccinated, managing and checking records – none of that is free. But the cost are low compared to what’s at stake.

I recognize that there are some people who really actually can’t be vaccinated. People for whom the vaccination itself actually carries material risk. I even know a few such people.

I also know there are a bunch of people who demand, and are often given exemptions for religious or philosophical reasons.

To me the line is bright and clear: a bone-fide medical exemption permits travel. A religious or philosophical exemption does not. If your god, or your philosophy, preclude vaccination they implicitly preclude international travel.

Because magic doesn’t work.

Everybody’s Gotta Have a Hobby

When someone meets Dawnise and asks her “what she does,” she often responds “I go to the theater!” This usually elicits a chuckle from the person asking. That’s intentional, but the the answer isn’t entirely a joke. Supporting live performance (sounds better than “going to the theater,” right?) is one of Dawnise’s (many) hobbies – she’s seen hundreds of shows since we moved to London in 2019, and because she’s innately frugal the average price paid for a ticket is surprisingly low. She also sews, paints, reads, and has become the primary user of our Steam account, playing odd and interesting games involving lots of puzzles and exploration and fairly few bullets.

When it looked like I’d be taking some time off work, Dawnise and I would chat on and off about what I might do while I wasn’t working. I had precious few specifics to offer, but I wasn’t worried – I figured I’d have plenty of things to do and wouldn’t get bored – at least for a fair while.

I ended up postponing taking time off, but that nagging question – “what will you do?” – won’t quite leave me alone.

Trying to answer has made me realize I don’t really have what you might call “a hobby.” Computers were an early hobby that turned into my field of study and subsequently into my profession. That a hobby turned into over three decades of gainful employment has meant that for most of my working life what I do hasn’t generally felt like “work.”

All these years later, however, and it’s fair to say that some of the shine has come off. I no longer think of computers as a hobby.

Why? Well, I have a truly marvelous explanation that this margin is too narrow to contain…

At any rate, I’ve been thinking about hobbies. And I’ve decided that “I need to find a few.”

So I’m building a list of potential hobbies. Well, really, I’m building a list of evaluation criteria.

I’m open to things with moderate startup costs, and reasonable (low) recurring costs. Whatever it is needs to be space efficient, ’cause we don’t have a bunch of spare room knocking about. If it’s outdoors, it has to be “London weather compatible” (turns out, it rains here, and the winter is chilly), and it needs to be “reasonably flexible” to schedule.

I have a guitar – two in fact – I should find a teacher and learn to play. It requires some scheduling, and lessons are an ongoing expense, but supporting a teacher and learning something feels like a totally worthy investment of time and money.

I also have a camera. I take it with me when we travel, but I shouldn’t only take it out when we’re getting on a plane or a train. London is huge and much of it – not just the touristy bits – are stupidly photogenic.

I also have a car, and there are plenty of things to see (and photograph) beyond London proper.

I don’t have a motorcycle here – the lack of a good (read: reasonably secure and out of the weather) place to park one has kept me from seriously considering “fixing” that – but I love the idea of taking the camera with me on motorcycle rides around the country (and the contingent). So maybe I take another tilt and figuring out where I can park a bike that doesn’t cost an arm and a leg or make it so inconvenient to access that I never do.

Finally I think I’d like to find a TTRPG group. I’ve played and run games on and off since I was nine or ten but haven’t regularly played in over a decade. I expect this will be tricky, as it involves finding other people whose priorities (schedules) and play styles align with mine.

So I have the start of a list. I’m sure there are other things I should consider, and, if I’m lucky, maybe someone reading this will drop me a note and make a suggestion.

Maybe even you.

The Actual Stuff of Nightmares

12-December

As I write this, Dawnise and I are a train back to Krakow. We spent most of the day at Auschwitz.

I can’t yet put words to the thing.

Deciding to visit was very much in the category of “things we feel compelled do as an adult” not “things we want to do.” And it’s certainly not a thing I’m in a rush to do again.

Auschwitz is a place that should not be. A thing that should only exist in nightmares.

The place, and the events that transpired there, are too terrible to contemplate. The horrors beyond imagining.

And yet it is.

Terribly soul-crushingly real. Refusing to fade into mist.

There were moments today I’ll likely remember forever.

And I was just a visitor.

We booked admission in November, once we’d decided to visit Krakow. Even well in advance there were no English tour slots available, so we booked individual entry.

A 90 minute bus trip from the Krakow central bus depot and we joined the queue, where our tickets and IDs were checked and we were ushered through a metal detector.

We stopped at the bookshop and bought the guidebook and entered the compound.

I may have taken a dozen steps before I felt tears on my cheeks.

When we emerged from the last building dark had fallen. The camp was eerily empty – I don’t think we saw anyone as we made our way to the exit. Any return buses had long since departed, so we walked through the freezing dark to the Oświęcim train station.

I chose to leave my camera at the hotel, and we took very few pictures. The place deserved our full presence and attention, without the comforting intermediation of a camera lens.

So we looked.

We saw.

And we will remember. We have no choice.

22-December

We left Krakow and met up with friends in Switzerland, spending most of a week between Basel and Zurich before returning to London.

I’m finishing this entry over a week later, and I still can’t put words to the thing.

So I’ll borrow some from the entry marker:

Genocide presents us with an image so appalling that it can be damaging even to look.

But we know we must look.

We know that repressing memory, willed forgetting, is perhaps the greatest danger we face as a species.

If we want to remain fully human, we have no choice but to confront and remember the past, to learn, and to act on what we’ve learned.

Steven Spielberg’s RIGHTEOUS PERSONS FOUNDATION

No Boom

I was in Seattle last week, on what I expected to be my last work trip. While I was there, I was asked if I’d consider un-resigning and staying on to help with a thing.

If you read my post about about deciding to leave – and how I felt like I was leaving before I was “done” – you’d be forgiven for thinking staying would be an easy choice.

By last week I’d spent the better part of three months handing things off and starting to plan – ok, more imagine than plan, really – a new normal.

The idea of being “funemployed” had grown on me.

On the other hand, I meant what I said about wanting Axon to succeed.

I worked with someone, years ago, who said “show me you love me, don’t tell me you love me.” Investing (more) time and effort definitely felt like showing.

So I thought about it, got input from some colleagues, and Dawnise and I talked it through when I got home.

And this morning I agreed to rescind my resignation.

Is it the right choice? I’m not sure, but helping when someone asks for your help rarely feels like the wrong one.

Funemployment will wait a bit longer.

Things That Go Without Saying…

As someone who’s spent most of his career working in “at will” America, I find long notice periods… a little strange.

It seems sensible to keep your departure on the Q.T. for a while, so only people who “need to know” get told. But someone always needs to know, so your departure is never really a secret. And before long – and long before you’re gone – practically everyone knows.

Those days and weeks can feel a bit like attending your own wake, or listening to your own eulogy.

Some stop seeking your input, stop including you in conversations, even stop making eye contact. Some decide you can’t help them accomplish… whatever it is they’re trying to accomplish anymore, and stop involving you. Anything you’ve asked for tends to fall to the bottom of people’s priority lists, or on the floor, whichever is further.

People reach out to say farewell, or find out why you’re leaving, or both. And some, who regret that you’re leaving, try to get more shared time. Try to get more of whatever they think you’re good at, or good for, in the time that’s left.

It was one of those interactions that made me write this, and suggested its title.

A colleague, who I’ve come to respect as a co-worker and value as a friend, said some very kind words about the impact I’ve had over the time we’ve worked together.

All prefaced with “it goes without saying…”

And book-ended with “and the things that go without saying are often the things most worth saying.”

Absolutely true.

Long and Winding Road

“You’ve arrived at your destination” by Diego Arellano

I don’t typically post about work, but then this isn’t really “about work” – it’s me wrapping my head around something. No offense, but you’re sorta along for the ride.

A few years back – as the pandemic was loosening its grip on the world – I had left Amazon, and was happily “bumming around London,” when I got a note from a Amazonian colleague. He had taken a new role at a company I’d never heard of, and wanted to chat about working together again. Over breakfast.

“Breakfast sounds great,” I said, “but I’m not really looking for a job right now.”

After breakfast, and video chats with a couple other folks, I flew to Seattle for what turned out to be the first on-site interview most of my panel had done since the pandemic. Looking for it or not, it seemed a new thing had found me.

When Axon extended an offer and asked me to join I couldn’t delay any more, I had to really decide what I thought about the company and its products.

My decisions about where to work, and what to work on, have always been guided by a few rules, the top one being “I don’t want my code to kill people.” When I had the chance, early in my career, to work on medical device software I decide not to – because I didn’t like the idea of my code killing people by accident. And I’ve never chosen to work on things that kill people by design, like weapons systems.

When Axon was founded, 30-odd years back, it wasn’t called Axon – and it didn’t do software. It was called TASER, and that’s mostly what it did. The TASER is a weapon, no matter how you slice it. A “less lethal” one for sure, but a weapon. I wouldn’t be joining to work on TASER – I’d be working on real time and situational intelligence tools for first responders – but TASER was a proverbial elephant in the room.

So I think it’s fair to say that the decision to join Axon was one of the most carefully considered career choices I’ve ever made.

I turned the decision over and over. Stared at it from every angle. I talked to friends. I got input from people I expected would tell me why joining was the stupidest thing I could do, and from people I guessed would argue the opposite. I didn’t always get what I predicted. I looked into the company. Its founder. The things they built. The customers they built those things for…

Ultimately, I decided that as much as I wish law enforcement didn’t need TASERS – or firearms – the TASER seemed like a tool that could make things better. And making things better seemed… better.

I’ve told bits of that story to hundreds of the candidates I’ve interviewed since joining. I’ve encouraged them to think about the implications of working on systems that are mission critical – and sometimes safety or life critical. One of the senior leaders sometimes calls it a “sacred responsibility,” and while I might choose different words, I understand and agree with the sentiment. The responsibility, and the associated ways of working it encourages, aren’t a good fit for everyone. They demand thinking critically about choices and tradeoffs, and being willing to fly in the face of commonly accepted industry best practices – what’s right for selling consumer goods and services, or selling advertisements and sharing cat pictures on the internet, isn’t clearly right for building systems people rely on to keep themselves and others safe. Moving fast and breaking things is a terrible idea when it puts people in harm’s way.

My time at Axon has taught me a bunch.

About public safety, and the people who choose to walk that path.

About the tools we ask first responders to use while doing their jobs.

About how it feels to go 70mph – the wrong way on a 20mph street – in the back of a Met patrol car, lights flashing and siren screaming. Whenever I think “I’m a pretty good driver,” I’ll think about the police constable who was weaving the patrol car through impossibly tight spots that I swear didn’t even exist until he was in them; and for whom this race through London toward danger was just a Tuesday…

And along the way, I learned some things about myself.

Three years on Axon and I have reached a fork in the road, and our paths are diverging.

There’s no one simple reason. The London R&D center I joined to help grow from nothing has grown – to over a hundred in and around London. And the company continues to grow globally year over year. What a company needs changes as it grows. And I started getting the distinct feeling that what I’m good at – and the ways I most enjoy contributing – were falling out of alignment with the company’s needs.

I was growing less and less confident that I was in the right place, doing the right things, right now.

I still looked for ways to stay. I worked with leadership to create a new role that we were optimistic I’d be both happy and effective in. Sadly after the first couple months in that role it was clear to everyone it wasn’t going to work out as hoped.

I tried to convince myself there was at least one more viable thing to try, but evidence was piling up that I was trying to fit a me-shaped peg into a someone-else-shaped hole.

In retrospect, perhaps I shouldn’t have been surprised that deciding to leave was just as difficult as deciding to join. But it was difficult, and I was surprised. Deciding to quit was hard, for a bunch of reasons – all the “normal” ones, and some I struggled to put words around.

Lots of companies have a mission statement. They hang it on a wall in a lobby, or the executive offices. They trot it out in shareholder letters, or during shareholder meetings.

Axon has a mission.

An audacious and seemingly impossible mission. We’re out to obsolete the bullet, and incredibly, impossibly, we’re actually making progress.
(I know, it sounds impossible, or maybe just charmingly naive.  I've become convinced it's neither of those. Axon's founder and CEO Rick Smith talks about the company, the vision and the mission with Joubin Mirzadegan in this episode of Grit - give it a listen, see if he convinces you, too.)

And I had no idea, when I joined, how much having “a mission that matters” would matter to me.

Still, that didn’t change the situation on the ground, and failing to find a better path, I handed in my notice.

I’m parting ways with some great colleagues, and folks I hope to keep as friends. And I’m leaving a company I feel more emotionally invested in than most anything else I can point at in my career.

I don’t yet know what comes next. Some time off, catching up on things work displaces in life. Hopefully more travel.

And if I’m very lucky at some point the next thing will find me. Again.

I want Axon to succeed in its mission to Protect Life, and I think the best way I can support that right now is to help Axon find people who contribute to that success.

So if you or someone you know are looking for a place to have outsized positive societal impact, and are based in Seattle, San Francisco, Phoenix, Atlanta, Boston, London, Brussels, Tampere, Ho Chi Minh City, or anywhere Axon has a hub, drop me a line. I’m more than happy to make introductions.