I'm a backend engineer drawn to the parts of a system most people would rather not think about — the data model that still has to make sense in five years, the API contract a dozen other teams depend on, the failure mode that only shows up under real load at three in the morning.
My work centers on Python and Django, building APIs and distributed systems designed to stay predictable as traffic, data, and team size grow. Performance and security are treated as design constraints from the start, not something bolted on afterward, and I'd rather remove a clever piece of code than explain it for the third time.
There's always more to learn here, and that's most of the appeal.
| Languages |
|
| Backend |
|
| Frontend |
|
| Databases |
|
| DevOps |
|
| Infrastructure |
|
| OS |
|
| Tools |
|
| Clean Architecture Clear boundaries between layers, so a change in one place doesn't ripple through everything else. |
Readable Code Code is read far more often than it's written — optimized for the next person, including future me. |
Performance First Efficiency is considered from the first design pass, not patched in after launch. |
Security by Design Threat modeling belongs in the design phase, not in a post-incident review. |
| Scalability Systems built to handle growth in data, traffic, and team size without a rewrite. |
Automation If it's done more than twice, it should be scripted, tested, and version-controlled. |
Maintainability Software is a long-term liability — every decision is weighed against its upkeep cost. |
Continuous Improvement Refactoring and learning are part of the job, not extra credit. |
"A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable."
— Leslie Lamport

