Perspective earned
inside the work.
Selected work on the rules behind operational software: financial workflows, imported data, access boundaries, and the people who use them.
Examples from my professional work, with company and customer details omitted. Each explains the problem, the technical decision, and the behavior implemented.
Ending one session without signing out everywhere
Implementing organization-specific inactivity rules inside one application while keeping its session boundary separate from the identity provider.
02Data imports that respect local decisions
Defining record matching and local overrides so repeated imports could update shared data while preserving project-level choices.
03Keeping payroll and billing workflows independent
Correcting a shared lifecycle rule so completing payroll did not incorrectly block a separate billing workflow.
Have a technology decision
you need to get right?
Tell me what’s happening. I’ll let you know whether I can help
and how I’d approach the next step.