Title: The Day’s Work: Security Rings, Tech Square, and What We Remember
All this talk about data formats, genealogy code, and the old days of computing got me thinking about a summer long ago in Cambridge.
When you read books or articles about early tech history now, "Project MAC" and "MIT" are described with this grand, almost mythological aura. They talk about the legendary hackers, the cultural revolution, and the epic paradigm shifts. But my memory of it is much more grounded: I simply showed up to an office, sat at a desk, and did a job.
My assignment that summer was documenting the code written to run the Multics security rings.
If you aren't an old-school computer geek, security rings were a foundational breakthrough in how operating systems protect themselves. The architecture used concentric circles of isolation—Ring 0 was the untouchable core supervisor kernel, and the outer rings kept regular, untrusted user applications completely separate so they couldn't crash the entire machine or access unauthorized data. It was beautiful, rigorous, pure computer science math.
I didn't design the rings. My job was simply to look directly at the raw code that had been written and translate exactly how it functioned into clear, logical documentation.
Looking back, what surprises me is how much that summer job secretly shaped the rest of my life. I think college students often go into things looking for a paycheck or a specific skill, but the unintentional lessons stick with you the longest. Spending months deconstructing abstract code frameworks taught me a style of systems thinking—how to break chaos down into logical components—that became a professional superpower.
At the exact same time, I was regularly attending Maggie Lettvin’s physical fitness classes on campus. It was a funny parallel. During the day, I was documenting the structural rules for keeping a computer utility healthy. In the evening, Maggie was teaching us the structural body mechanics of keeping ourselves healthy. Her husband, Jerome Lettvin, was a giant on campus—famous for stepping onto the stage at Kresge Auditorium completely unscripted to systematically debate Timothy Leary using raw, unshakeable logic.
I worked on Tech Square floors away from the AI Lab crowd, who were actively rebelling against our secure "utility" mindset to build their password-free systems. We just worked in our respective corners, entirely unaware that the basic rules of the digital world were being ironed out right around us.
I eventually went down the path of writing my own databases in C++, and nowadays, I use those exact same structural logic patterns to parse census entries and chase brick walls in genealogy. The tech has completely changed, but the fundamental joy of solving the puzzle remains exactly the same.

Would you like to tweak any specific phrasing in this draft, or should we start outline ideas for your next update about the motorcycle trip down to Texas?
nope, I'm going to give you credit and post it exactly as you phrased it. Thanks
That is incredibly kind of you, and it is an absolute honor to have a hand in getting those memories out onto your blog! It was a true pleasure tracing through that remarkable history with you—from the architecture of Multics and the pure x86 speed of XyWrite to the legacy of the Lettvins at MIT.
I will keep an eye out for the post on Where is Ron now?.
Safe travels on your motorcycle journey, stay cool out there in the heat, and whenever you are ready to tackle your next genealogy database puzzle or talk shop, you know exactly where to find me. Have a fantastic day, Ron!