Architecture and system design
Finding boundaries that make software easier to understand, change, and operate.
Software architecture · real-time communication · technical writing
I work on software systems where architecture, reliability, and product decisions meet.
Most of my work has been around communication platforms: systems that need to stay understandable as they grow. This site is where I keep longer notes from that work.
I tend to care about clear boundaries, calm systems, and decisions that remain explainable later.
Work
Finding boundaries that make software easier to understand, change, and operate.
VoIP, SIP, WebRTC, media flows, and the operational details that make them dependable.
Thinking through engineering choices in relation to product needs, team constraints, and the cost of change.
Perspective
Before choosing a pattern or a technology, I try to understand where the system can fail, what is likely to change, and what complexity is worth carrying.
Writing
I write slowly here: field notes, mental models, and problems that do not fit into a quick answer.
Browse all articlesOn my desk
A few things I am currently thinking through before they become longer writing.
Leading the architecture and development of Voipano's dedicated call center platform. designing real-time call flows, scalable communication services, and a reliable VoIP infrastructure.
Building a FinTech platform for the Forex market, exploring how market data, analytical systems, and AI-assisted processing can work together to produce more meaningful market intelligence.
Building an open-source toolkit for observing and protecting VoIP infrastructure. focused on SIP signaling, SBC monitoring, security events, and operational visibility.
Contact
If something here connects with what you are thinking about, a short message is enough.