// Skills
How I think about engineering
What I work on
Full-stack products with real users, leaning backend. I care about API design, data modeling, and making sure the boring paths — auth, migrations, tests — are solid before adding features.
What I'm interested in
Distributed systems, database internals, developer tooling, and reliability. The problems that show up when a system has to keep working, not just work once.
Currently learning
System design (from first principles, not templated interviews), deeper Java concurrency, and practical AWS infrastructure patterns.
Principles
- 01Tests are a design tool — if a module is hard to test, it's usually badly shaped.
- 02Simple schemas beat clever ones. Normalize first, denormalize only with a reason.
- 03Measure before optimizing. Most performance wins come from removing work, not adding cache.
// Stack
Tools and tech
Grouped by area. Only what I've actually shipped or studied deeply.
Languages
PythonJavaScript (ES6+)JavaCSQL
Backend
FastAPINode.jsExpress.jsREST APIsMicroservicesJWTOAuth 2.0
Databases & Caching
MySQLPostgreSQLNoSQLRedis
Frontend
React.jsTailwind CSS
Cloud & DevOps
AWSDockerCI/CDLoad balancingGitHub ActionsNginxGitGitHub
AI & Machine Learning
PandasNumPyScikit-learn
Tools
n8nLinuxPostmanVercelJupyterClaude
Concepts
Data Structures & AlgorithmsOOPSystem DesignDistributed SystemsAgile