The long view⌗

I have spent much of my life around systems—military, business, educational, and technical. The best of them share a few qualities: they are understandable, dependable, disciplined, and built for people who must actually use them.

I served in the U.S. Army from 1982 to 1988. My later work moved through payroll and scheduling, bookstore software, FoxPro business systems, data conversion, barcode systems, semiconductor manufacturing, SAP, technical instruction, and independent development.

The technologies changed. The basic questions did not:

  • Can a person understand what the system is doing?
  • Can the work be checked and repeated?
  • Does the design preserve useful knowledge?
  • Will it still make sense to the next person?

A working timeline⌗

1982–1988
Army service. Discipline, responsibility, and practical work under real constraints.
Around 1990
College and early professional computing. Business software, payroll scheduling, COBOL, and database work.
1990s
xBase and FoxPro systems. Cross-platform business applications, time and attendance, receivables, and data-centered software.
Enterprise years
Manufacturing, barcodes, conversion, SAP, and ABAP. Systems attached to physical work, production, and long-lived business processes.
Teaching
Technical instruction. Explaining programming and systems reinforced the belief that software should reveal its own structure.
Now
x64base and DotTalk++. Revisiting the strengths of readable database systems with modern C++, cross-platform tools, documentation, and AI-assisted development.

Not simply nostalgia⌗

I value older systems because many of them were direct. A table looked like a table. A command described an action. A programmer could follow the path from input to result.

That does not mean freezing technology in the past. It means carrying forward the parts that still deserve to live: clarity, inspectability, modest dependencies, durable data, and respect for the operator.

Beyond programming⌗

Photography and art provide a different kind of discipline. Technical work asks whether a system functions. Visual work asks whether we noticed what was there.

This site holds both.