Section The Long Gallery
02 / The Long Gallery
Not a résumé. The eras carry the argument; roles, employers and dates are supporting detail. Read only the lessons and you have the whole of it.
Technician · Architect · Executive · Builder · Teacher
01
Learning that technology exists to support a mission.
What this era taught me
Systems are not abstractions when people depend on them. Reliability, communication, procedure and accountability come before novelty.
02
Moving from individual problems to interconnected systems.
What this era taught me
A system looks very different to the person who has to keep it running than to the person who designed it. Maintainability is not a courtesy — it is the job.
Desktop environments, infrastructure, enterprise systems, troubleshooting, deployment, operations and user support.
03
Connecting technology to business requirements.
What this era taught me
Clients rarely need the technology they ask for. They need the outcome they believe that technology will produce. The work is discovering the difference.
Enterprise, government, defense, education and other regulated environments — SharePoint, collaboration platforms, CRM, application development, systems integration and compliance-aware delivery.
04
Becoming responsible for organizations, teams, adoption and outcomes — not merely systems.
What this era taught me
The hard part of enterprise technology is rarely installing the software. It is aligning people, process, incentives, data and systems well enough for the change to last.
05
Returning to hands-on creation with three decades of accumulated context.
What this era taught me
AI changes what can be built and how quickly. It does not repeal the lessons of architecture, operations, governance, testing or human behaviour.
Also learned