Infrastructure
Servers, networks, and systems administration. I learned to look beneath the interface and understand what keeps a system alive.
A field notebook by Jesse Anderson
I’m a software engineer who took the long way here—through server rooms, cloud architecture, product code, and now AI. This is where I keep the things I’m building and what they’re teaching me.
Begin at the beginning ↓Still learning. Still making.
Usually the hard way.
CHAPTER ONE / THE LONG WAY AROUND
Servers, networks, and systems administration. I learned to look beneath the interface and understand what keeps a system alive.
A self-taught path into professional development. Building became the way I learned—and the way I made ideas useful.
A year as a Solutions Architect taught me to see the whole landscape: people, constraints, tradeoffs, and the connections between them.
At Disney, and in my own work, I’m exploring how people can build with capable agents without giving up understanding or responsibility.
遠回りにも意味がある
There is meaning in the long way around.
CHAPTER TWO / CURRENT EXPEDITIONS
LOCAL AI AGENT COMMAND CENTER
“Code became cheap.
Understanding did not.”
A keyboard-first home for running multiple local coding agents without losing track of the work—or my responsibility for it.
Why I’m building it To understand what dependable agent systems actually need: identity, visible state, honest permissions, and an operator who remains in control.
Open the project ↗A CLIMBER’S TRIP NOTEBOOK
A trip planner connecting climbing areas with camping, approaches, parking, and the practical details that shape a weekend outside.
Why I’m building it Because the best days outside begin long before the first climb—and useful local knowledge is usually scattered everywhere.
Open the project ↗A SMALL LAB FOR AGENT MECHANICS
Take it apart.
Put it back together.
Understand every piece.
A deliberately small Python lab for learning agent loops from the inside: tools, structured outputs, evaluation, and safe boundaries.
Why I’m building it I don’t want to understand AI only from the surface. This is the notebook where I test the machinery.
Open the project ↗CHAPTER THREE / NOTES FROM THE ROAD
Not thought leadership. Just an honest record of decisions, dead ends, things that worked, and what I understand now that I didn’t before.
Why I’m making space to record the experiments, decisions, and lessons behind what I build.
Code became cheap. Understanding did not. Cyberdeck grew from my need to manage multiple coding agents without losing track of the work—or my responsibility for it.
A NOTE FROM JESSE
I’ve spent nearly two decades following my curiosity through technology. The labels have changed—systems administrator, developer, solutions architect, software engineer—but the habit underneath has stayed the same: get close to the machinery, ask how the pieces connect, and make something that helps.
This site is a record of that journey while it is still happening. If something here connects with what you’re working through, I’d be glad to hear from you.