How I work
Excellence in the details.
If I commit to something, I want to do it as well as I possibly can - the details most people never see are often what make the whole system better. It's what drew me to backend systems, where reliability, simplicity, and good decisions matter long after the code is written.
Ownership and independence.
If I own something, I should be able to understand it, make decisions about it, and stand behind the result. I don't like waiting around for someone else to fix what I can fix myself.
Bias toward action.
When I see something broken and there's something I can do about it, I want to do it - I'd rather try, learn, and improve than wait for the perfect answer.
Results people can feel.
I want to know that what I build actually helps someone, makes a process easier, or solves a real problem. Good technology isn't just technology that works - it should make something better for the people using it.
How I use AI
Own the outcome.
I make the decisions, understand what I build, and take responsibility for the result. As AI gets more capable, an engineer's value shifts toward knowing what to build and when the machine is wrong.
Tool not a replacement for thinking.
I use AI to explore ideas, get unstuck, automate repetitive work, and move faster - but I don't hand over the thinking.
No shortcuts no hype.
I'm not interested in using AI to cut corners or chase trends - I use it to extend what I can do while keeping my judgment and responsibility at the center.
Full transparency.
I'm always honest about how I use it. Whatever I build, write, or share still reflects my own judgment, ideas, and voice.