A developer is what I do. Not the whole of what I am.

Most portfolios open with a job title and a stack. Mine opens with a habit: I get curious about how something works, take it apart, try to rebuild it myself, and somewhere in that process stop being a beginner at it. It's happened with authentication systems, with cloud infrastructure, with why people react the way they do under stress, and with what my own training log says about consistency.

So there are two versions of me on this site. One designs backend architecture, deploys and operates production systems, and debugs infrastructure at midnight. The other is more interested in why a claim is true, why a person did what they did, or what's actually happening underneath the library that's hiding it from you. They're not really different people — same habit, pointed at different material.

That's also why it makes sense to hand me the messy parts of a system. The same refusal to accept "just use this library" as an answer is what makes auth, payments, and infrastructure work reliably once I've been through it.