Understand before building
Start with the real workflow. Ask what people need to do, and where the existing system gets in their way.
I like understanding how the whole thing works. The interface people use. The code behind it. The server it lives on.
A closer look at my experienceMy work has taken me from customer software at Phylex to accounting workflows at INYC and infrastructure at ISPLABS. Different problems, but the same question: how do we make the whole system useful?
I’m comfortable moving between an application and the environment that runs it. That perspective shapes the way I build — with the people using and maintaining the software in mind.
Start with the real workflow. Ask what people need to do, and where the existing system gets in their way.
Readable code, clear boundaries and practical documentation help a project keep moving.
An interface, an API and a network are parts of the same experience. I want to know how they behave together.
Have a problem that crosses a few boundaries?
Let’s figure it out