I'm a full-stack engineer at BNY. I work across the backend and the interfaces on top of it, and I care as much about a system holding up under load as I do about how it feels to use. Lately I've been spending more of my time where software meets AI.
At BNY I own services across a banking transaction platform. It's Spring Boot on the backend and Angular on the front, running on systems that move real money for internal and external clients, so getting it right and keeping it up really matters. Before this I did ML, building with GANs, LSTMs and decision trees at Google, and these days a lot of my time goes to where backend work meets AI and the Model Context Protocol.
That doesn't stop at work. I've built and shipped full products on my own too, like a fault-tolerant payments engine, real-time anomaly detection on Kafka, and a full-stack book platform with its own backend and admin. Building the whole thing is honestly just how I understand it best. Serious system or side project, I go about it the same way, and I want the result to be fast and actually nice to use.
“I build software the way I'd want to use it. Fast, honest, and not a pain to deal with.”

This is what I reach for most. Honestly though, the thinking underneath matters way more than any one tool on this list.
Writing is how I think things through. Mostly notes on stuff I build, break, and eventually figure out.
A few things I keep thinking about but haven't built yet. Vote for the one you'd actually use and it moves up my list.
I read a lot. Enough that I built a whole site for it: The Bookish Land, 60+ honest book reviews sorted by aesthetic, like Dark Academia, Cottagecore and Romantasy.
And yes, I designed and built that one too. Full stack, cover to cover.
visit thebookishland.in →Have a role, a project, or just want to say hi? Drop me a message.