About the service
I offer niche engineering services around Sather — an object-oriented language grown from ICSI Berkeley and bearing strong Eiffel influence. Over the years I have worked closely with parameterized classes, abstract types and iterators — a construct that makes Sather special — so I am comfortable reading source code that most engineers have never seen. My work divides into three directions. First — legacy maintenance: I bring projects back to life that stopped compiling on modern tools, untangle old build scripts, fix broken class hierarchies and add small capabilities still needed by the research group. Second — academic and research migration: I port algorithms written in Sather to languages your team can realistically maintain today, preserving the exact semantics of the original iterators and generics rather than guessing. Third — documentation and knowledge transfer so people are not left with a black box. Every project starts with a short audit: I read the codebase, clarify which dialect and runtime you depend on, and give an honest assessment. The deliverable includes a working build, a written report describing each change, notes on regressions and a maintenance checklist. I test each module separately before integration and never remove behavior without explaining why. If you have a pile of Sather sources from a former graduate student or closed lab, I will tell you what is worth saving and what is not, and then perform the rescue. Typical timeline is one to two weeks depending on scope and I stay in touch for questions after delivery.
