About
The Through-Line
Thirty years of building — software, hardware, infrastructure, organizations, degree programs — produced the same recurring question: what does it take for an organization to adopt a capability it doesn't yet trust? The technologies changed. The question did not.
The work covered a lot of ground: software architecture, DevOps, cybersecurity, networking, databases, AI and machine learning, embedded hardware, and rapid prototyping — at scales from a campus Linux server to regulated medical device platforms to statewide library infrastructure. But the domain was never the point. The point was what happened when a team or organization moved from "we can't do this yet" to "we can do this now." Making that transition happen — reliably, at whatever scale, without breaking what already works — is the thread that connects every chapter.
My leadership approach: build and activate teams, establish the process and metrics that drive execution, and leave the organization more capable than it was.
The Pattern
Each chapter of my career has put this to work at a different inflection point — moments when a capability became viable before the organization knew how to adopt it.
In the early 1990s that was open systems. Linux was real but inaccessible, and campus IT had no strategy for it. Rather than wait for a mandate, I built Cutter — Shippensburg's first web server, running on a 486 — which eventually served nearly 2,000 users. The lesson was not about Linux. It was about lowering the barrier before demanding the behavior.
In the 2000s I spent two decades as a professor of computer science and engineering. I founded an engineering school, led ABET accreditation, taught 41 courses, mentored hundreds of students, and published research in AI, the semantic web, and engineering pedagogy. The greatest impact was often through people.
That same lesson recurred across statewide library infrastructure, university enrollment systems, ABET-accredited engineering programs, and medical device platforms. Each time, the technical problem was solvable. The real work was making the solution approachable — abstracting away the hard parts, building the right bridges, teaching the people who would carry it forward.
The Domains
I have led and delivered hands-on across:
- Software development — architecture, SOLID principles, clean code, test-driven development, code review, mentorship
- DevOps and platform engineering — CI/CD, automated testing (DAST/SAST), infrastructure, harmonized toolchains
- Cybersecurity — embedded authentication, PKI, certificate authorities, access control, regulated compliance (FDA 510(k))
- Networking — distributed systems, statewide infrastructure, firewalls, VPNs, remote authentication at scale
- Databases — data warehousing, Oracle, machine learning on institutional data, enrollment management
- AI and machine learning — composite kernel learning, semantic web / OWL constraint generation, applied ML in industry
- Embedded hardware — FPGA design, PCB fabrication, embedded Linux, firmware, rapid prototyping
- Engineering education — 41 courses taught, 30+ undergraduate research projects, ABET accreditation, degree program creation
The common thread in every domain: learn from first principles, find where complexity is hiding, eliminate it, and teach others to do the same.
Career Eras
| Era | Focus | Lesson | Case Study |
|---|---|---|---|
| 1990–1993 | Discovering systems | Great engineers learn systems, not products | — |
| 1993–1996 | Democratizing computing | Lower the barrier and people surprise you | Cutter Linux |
| 1994–1999 | Statewide infrastructure | Platforms are relationships as much as software | Platform Is Relationships |
| 1999–2002 | Enterprise applications | Information becomes strategic when connected | Enterprise Registration & Data Warehouse |
| 2002–2022 | Professor and builder | The greatest impact is often through people | Building Engineering Programs & ABET |
| 2022–present | Platform and AI | AI changes organizational capability more than software | Platform Strategy in Regulated Environments |
The invariant across every role: recognize inflection points, build bridges, teach others, leave systems more capable than before.
What I Believe
Technology by itself rarely transforms organizations. Organizations transform when technology, process, economics, governance, and people evolve together.
My work has always been about enabling that transition — building systems that outlast components, reducing friction before demanding effort, and leaving organizations more capable than I found them.
Outside the Résumé
I continue to teach through writing, speaking, and practical demonstrations. I am Professor Emeritus of Computer Science & Engineering at Shippensburg University.
For employment history, publications, courses taught, and technical projects, see the Professional Archive.
For how I reason about engineering and organizational change, see Doctrine and Thinking.
Thomas H. Briggs, Ph.D. — Technical Director, Medical Device Software, Baxter Healthcare