About Me
Hi, I'm Yawar – a software engineer who builds reliable backend systems.
I specialize in building the behind-the-scenes software that powers businesses in healthcare, logistics, and finance. The kind of systems where accuracy matters more than speed, and failures need to be handled gracefully.
What I enjoy most is solving real operational problems – automating workflows that save teams hours of manual work, building integrations that sync data reliably, and creating tools that non-technical users can trust.
What I Do
- ✓Build secure systems for handling sensitive data (HIPAA, PCI)
- ✓Create automation that replaces hours of manual data entry
- ✓Design fault-tolerant systems with automatic recovery
- ✓Build dashboards and admin tools for operations teams
My Background
I've spent years working on systems that handle sensitive information – from patient health records to financial data. I've learned that when it comes to important data, getting it right is more important than being fast.
I build software that can handle problems gracefully. If something goes wrong (and in the real world, things do go wrong), my systems are designed to recover on their own or at least alert someone right away instead of failing silently.
Tools I Use
- →Python — Django, FastAPI, async programming
- →Automation — Playwright, Celery, scheduled tasks
- →Data — PostgreSQL, Redis, data pipelines
- →Cloud — GCP, Docker, containerized deployments
- →Frontend — React, Angular (internal tools & dashboards)
What I Believe In
Reliability First
In healthcare and finance, wrong data causes real problems. I optimize for correctness before speed.
Idempotent by Design
Every operation should be safely retryable. Networks fail, services restart – systems must recover gracefully.
Explicit Over Clever
Code that's easy to read and debug beats elegant abstractions. Future maintainers will thank you.
Fail Loudly
Silent failures corrupt data. Systems should alert immediately when something isn't right.
Audit Everything
In regulated industries, you need to prove what happened and when. Comprehensive logging is non-negotiable.
Document as You Build
If it's not documented, it doesn't exist. READMEs, comments, and decision logs are essential.
How I Build User Interfaces
When I build screens and dashboards for users, I focus on clarity and reliability over flashy features.
The Server Knows Best
All the important checks and rules live on the server. The user interface just displays what the server decides – it doesn't make its own decisions.
Double-Check Everything
While I add helpful form checks for users, the server always does its own verification. Never trust data from the user's browser alone.
Clarity Over Flash
Internal tools should be clear and easy to use. No fancy animations just for show – users need to get their work done efficiently.
Built for Everyday Use
The people using these tools use them every day. They need things to work reliably, not to be impressed by fancy designs.