The Path
A different route to software engineering
Economics Background
Analytical thinking and systems perspective from the start. Health challenges redirected the path, but the foundation remained.
Chemical Operations
Five years working with complex industrial systems. Precision, safety protocols, and understanding that in critical environments, reliability isn't optional.
Building on the Side
Game modifications, community websites, team forums, LAN party infrastructure. Always finding ways to make technology solve problems and bring people together.
Professional Development
Formal software engineering education. Turning years of practical experience into structured expertise. The passion became the profession.
Enterprise Systems
Nearly a decade building platforms for government, healthcare and security sectors. The stakes evolved, the drive to learn and improve stayed constant.
Independent Practice
Employment brought experience but also limits. Now as a freelancer, the constraints are gone. Full control over projects, continuous investment in books, courses and seminars. Growing faster than ever before.
What I believe
The principles that shape how I work
Value over output.
Anyone can ship code. The question is: does it solve the right problem? I'd rather deliver one thing that matters than ten things that don't.
Fail fast, but don't break trust.
Speed matters. So does not blowing up production. Test what needs testing. Ship with confidence. Learn from what goes wrong.
Humans first, always.
AI will automate a lot. But it won't replace the creativity to solve problems that don't fit a pattern, or the judgment to know when the pattern is wrong. Tech should serve people, not the other way around.
Building together beats building alone.
The best work happens when people bring different perspectives and actually listen to each other. I'm not here to push what I know. I'm here to combine what we all know into something better.
Curiosity doesn't stop at the job description.
Code, infrastructure, networking, security, privacy, governance. It all connects. I want to understand how the whole thing works, not just my corner of it.
How I work
What it's like to work with me
I take ownership of problems, not just tickets.
Give me a complex system and I'll decompose it, find the leverage points and solve it piece by piece while keeping the big picture coherent.
I research before I commit.
Before picking a stack or pattern, I spike it. POCs, benchmarks, edge cases. Then I build with confidence instead of hope.
I ship fast without cutting corners.
CI/CD pipelines, automated tests, feature flags. The goal is sustainable speed. Iterations you can keep up for months, not just a sprint.
I communicate like a human.
Clear async updates, honest code reviews, pairing when it helps. I'll tell you what I think, ask questions when I'm stuck, and remember that everyone has off days.
I make teams better, not just codebases.
Short demos, lightweight docs, actionable feedback. I share context so knowledge doesn't stay stuck in one head.
I build security and privacy in, not on.
Medical records, immigration data, government systems. I've worked with all of them. Compliance isn't a checklist. It's how you think from day one.
Where this has played out
Stories from the work
I don't stop at code
The breadth of what fascinates me
Most developers specialize. Pick a lane, go deep, stay there. That's fine, but it's not me. I want to understand how the whole thing works. How the code runs. Where it runs. How it's secured. Who can access what. How teams collaborate. Why we're building it in the first place.
Infrastructure.
Not just "deploy to Azure." How networks are configured, how traffic flows, how environments stay consistent from dev to prod.
Security.
Threat modeling, least-privilege access, defense in depth. Not a checklist at the end, a way of thinking from day one.
Privacy & Governance.
Data minimization, retention policies, audit trails. Especially in healthcare and government, this isn't optional.
How teams work.
Communication patterns, decision-making, knowledge sharing. Code is the easy part. People are harder.
I don't know everything. But I want to, and that curiosity keeps me learning across boundaries instead of getting comfortable in one box.
And I can't keep it to myself. When I learn something useful, I want to share it. Short demos, written notes, pairing sessions, a quick "hey, I found this" in Slack. Knowledge stuck in one head doesn't help anyone. Ideas get better when you talk about them.
Developer by passion.
