The Long Way Around

For most of my professional life, I assumed I had a collection of unrelated careers.

Over the years I worked in politics, professional kitchens, construction, technical education, developer advocacy, and technology leadership. More recently, I’ve found myself spending time on institutional memory, provenance, AI architecture, museums, archives, and historical research.

Looking at that list on paper, it feels random. A career counselor might call it a lack of focus. An Applicant Tracking System would almost certainly struggle to figure out what box to put me in.

For a long time, I viewed it the same way. Every career change felt like starting over. Every transition came with the uncomfortable feeling that everyone else had chosen a lane and stayed in it while I was wandering between industries.

It wasn’t until recently, while working on the Sovereign Systems Specification and updating my personal website, that I began to notice something unexpected.

The industries had changed.

The questions had not.

The Same Questions in Different Places

When I worked in politics, information was everything. Every statement, every policy position, and every talking point ultimately came down to a simple question:

“According to whom?”

When I worked in professional kitchens, the same question appeared in a different form. Recipes, inventory, supplier relationships, food safety procedures, and training all depended on knowledge being documented, shared, and trusted. Making the same “house ranch” recipe from memory isn’t the same as having it written in a procedure.

Construction wasn’t much different. Plans, permits, change orders, inspections, and customer agreements all relied on accurate information and a clear understanding of where that information came from. A builder who’s working from memory instead of the stamped plans builds the wrong room. That’s not a rounding error — that’s a tear-out.

Technology brought the same challenges into a new domain. Documentation, system architecture, databases, APIs, observability, and developer education all revolve around helping people understand complex systems and trust the information they are using to make decisions.

More recently, my interests have expanded into museums, archives, historical research, and AI systems. Yet even there, the same themes continue to emerge.

The questions kept reappearing in different forms:

  • How do people store knowledge?
  • How do they trust knowledge?
  • How do they lose knowledge?
  • How do they pass knowledge to the next generation?

The technology changes. The industries change. The underlying questions remain remarkably consistent.

A Phrase That Refused to Stay in One Project

While writing the Sovereign Systems Specification, I coined a phrase that I initially thought was simply a good line:

Information without provenance is just gossip.

At first, it was intended as a commentary on AI systems. Large Language Models are increasingly capable of producing convincing answers, but confidence is not the same thing as evidence. If an answer cannot be traced back to a source, its reliability becomes difficult to evaluate.

The more I thought about it, however, the more I realized the phrase applied far beyond AI. Every field where trust matters has a provenance problem.

The phrase kept showing up because the principle kept showing up.

Eventually I stopped thinking of it as an AI concept and started viewing it as a general truth.

Maybe It Wasn’t Several Careers

For years I looked at my resume and saw a collection of disconnected experiences.

Politics, culinary arts, construction, technology, education, and research.

The assumption was that these represented different chapters of my life.

What I’m beginning to suspect is that they were all chapters in the same story.

The industries were different. The tools were different. The job titles were different.

What remained constant was an interest in understanding how knowledge is created, organized, trusted, preserved, and shared.

Seen through that lens, the transitions no longer look quite so random.

Politics was about information and trust.

Kitchens were about process and knowledge transfer.

Construction was about documentation and accountability.

Technology was about systems and understanding.

Museums and archives are about preservation.

AI is forcing us to revisit all of those questions at scale.

The Questions That Follow Us

One of the unexpected benefits of getting older is that you eventually accumulate enough experiences to identify patterns that were invisible while you were living through them.

In your twenties and thirties, careers often feel like a sequence of decisions.

In your forties and fifties, they sometimes start to look more like a sequence of questions.

The jobs change.

The industries change.

The technologies change.

The questions worth asking tend to remain remarkably consistent.

Looking back, I don’t think I’ve spent thirty-five years working in a series of unrelated professions.

I think I’ve spent thirty-five years exploring the same problem from different angles.

And perhaps that’s the lesson hidden inside a long and winding career:

The most important thing you carry from one job to the next isn’t a title, a skill, or a technology.

It’s the set of questions you never stop asking.

That’s the foundation the Sovereign Systems work is built on.

<>
That’s the foundation the Sovereign Systems work is built on.

Facebooktwitterredditlinkedinmail

A Review of PyCon 2017

PyCon 2017 was held about 45 miles south of Portland, Oregon where I am fortunate enough to live. I am typically not a great conference attendee so I was a bit nervous and apprehensive about going. After walking into the Portland Convention Center and being surrounded by 3,500 fellow Python enthusiasts, however, I was super excited.

PyCon 2017 Talks

There were several amazing talks on a wide array of subjects. There were first time PyCon presenters like Jonas Neubert with a fascinating talk on using Python for factory automation. Along with some “heavy hitters” in the Python community such as Philip James and Daniele Procida. Daniele’s talk on documentation was very interesting and definitely a different way of thinking of of the documentation process.

There were some really good keynote speeches as well. I really enjoyed learning from Lisa Guo on the migration path Instagram took to go from Python 2 to Python 3. I also found Dr. Katy Huff‘s talk on some practical applications for Python in the science field to be quite interesting.

Kenneth Love gave a tutorial on the Django Admin which I would encourage people to work through as well. As usual it is a great presentation and Mr. Love provides excellent information.

There were many other great talks, from many great speakers. The conference talks are available on YouTube here. I’d encourage you to watch, listen, and learn from as many as possible.

Vendors

There were some great vendors and businesses in attendance. Big companies like Google, Microsoft, Intel, and Facebook/Instagram were all there. They all offered some excellent short talks in their booths on how they were using Python for their applications or products. They also had a variety of swag they were giving away in exchange for a badge scan.

Google had an hourly trivia session and provided prizes for the correct answer. I picked up a copy of Python in a Nutshell: A Desktop Quick Reference for knowing that PyCon 2018 would be held in Cleveland, Ohio. Intel had several drawings for an Amazon Echo, along with several other vendors actually. Booz Allen Hamilton had several drawings for a Raspberry PI 3 Model B which I sadly wasn’t able to win.

Company branded socks were one of the big swag things at PyCon, beyond the t-shirts, stickers, and fidget spinners. Microsoft, O’Reilly Publishing, Citus Data, and Heroku all had custom socks. Scan your badge… get socks.

PyCon 2017 Vendor socks

Community

In addition to the great learning opportunities the talks provided, and the interaction with sponsors, another key feature of any conference is the people. The opportunity to get to meet and talk with people like Andrew Pinkham who authored Django Unleashed, or Russell Keith-Magee of BeeWare was spectacular. Having the chance to meet and talk with other developers about industry trends was great as well.

I have heard that the Python community is second to none in terms of inclusiveness and I was able to witness first hand that is indeed the case. Due to the exceptional overall experience I had at PyCon 2017, I am sincerely hoping that I can make to the trip to Cleveland in 2018.

Facebooktwitterredditlinkedinmail