Architecture, implementation, performance, live operations, and product delivery across enterprise platforms, immersive systems, games, and open infrastructure.
Software engineer · systems thinker · student of the physical world
Complex systems,
made useful.
I’m Nick Holbrook. For more than 13 years, I’ve helped teams turn ambitious technology into reliable software products; just as importantly, I’ve helped the people building them do their best work. Now I’m extending that systems practice from software and AI toward electrical engineering and nanotechnology.
Now: building AI systems, maintaining open infrastructure, and planning to begin electrical engineering studies in Fall 2026.
SYSTEMS PRACTICE / 13+ YEARSFORT WORTH, TX
N07
CONTEXTMATTER
SOFTWAREAI SYSTEMSATOMS
I translate ambiguity into shared decisions, strengthen the people closest to the work, and remain accountable for the outcome.
AI systems remain active work; electrical engineering and nanotechnology are the deliberate next frontier.
Selected work
Evidence over adjectives.
Four projects show the range: enterprise architecture, biomedical training, global live media, and open creator infrastructure.
Flite Golf
A configurable, white-label golf entertainment system built to perform reliably across live, multi-bay venues.
- Product architecture
- Real-time networking
- Team leadership
Roche VR Training
An immersive training system that let scientists and technicians practice complex laboratory procedures in a safe virtual environment.
- XR architecture
- Authoring systems
- Assessment
Rio 2016: 360° Broadcast
Application and production-control systems for one of the earliest large-scale Olympic 360° and VR broadcast experiences.
- Broadcast interfaces
- 360° video
- Rendering
OGAL + Token Toss
A public-good asset protocol and the end-to-end game that demonstrates portable, verifiable, creator-owned levels.
- Protocol design
- Rust / Anchor
- Unity
Flagship working idea
Evolving framework · V0.1
The Contextual
Pipeline Framework
A method for designing AI and agentic automation around context, constraints, routing, verification, and resource budgets; the model alone is never the complete system.
Explore the framework01FrameIntent · context · constraints
02RouteModel · tools · autonomy
03ExecuteBounded work · visible state
04VerifyEvidence · tests · judgment
OUTPUTUseful work you can defend.
Choose your path
What do you need to know?
The site is structured to answer different trust questions without making every visitor read everything.
01
Hiring teams
See how I architect systems, lead delivery, and reduce ambiguity.
Evaluate experience ↗02Clients
Explore focused advisory, architecture, and engineering engagements.
Explore services ↗03Collaborators
Follow the ideas, open-source work, and road toward nanotechnology.
Read field notes ↗04Investors
Review product thinking, market awareness, technical proof, and current initiatives.
Review a venture case ↗The next frontier
New challenges,
now made of atoms.
Software taught me to think in systems. I plan to begin at Tarrant County College this fall, adding the physics, mathematics, circuits, and materials foundation for a future transfer to UTA in electrical engineering with a nanotechnology focus.
Follow the learning journeyField notes
Learning in public.
Working essays on AI systems, software architecture, leadership, product judgment, and the road from code to matter.
AI systems10 min read
Context Is The Scarce Resource
Why an agentic system’s quality is often determined before the model receives its first instruction.
Read the working essayLeadership9 min read
Create Clarity, Then Give It Away
A servant leader’s job is to make good decisions easier for everyone else; the leader should not become the permanent decision-maker.
Read the working essayLearning log10 min read
From Bits To Atoms
What changes when a software engineer begins learning to design for matter, energy, and the nanoscale.
Read the working essayA service function
Leadership should leave the system and the people stronger.
Create clarity
Turn uncertainty into an honest, shared plan.
Grow capability
Share context, mentor generously, and remove bottlenecks.
Own the outcome
Stay close to reality and take responsibility when it changes.
Build · advise · collaborate
Bring me the hard problem.
If it sits at the intersection of product, architecture, emerging technology, and human judgment, we will probably have a useful conversation.