{{ current.date }} · {{ current.readingTime }}
{{ current.title }}
{{ current.excerpt }}
{{ block.text }}
{{ block.text }}
{{ block.text }}
Fifteen years of writing code, five of looking after the people who write it. Developer tools, trading systems, products people rely on at work — different worlds, the same recurring questions about building something that holds up.
I grew up in India and started out in Bengaluru building tools for other developers — the unglamorous kind that save someone an afternoon.
Then a few years in banking, where a bug has a number attached to it, and then a long stretch building products people rely on at work every single day. Each move taught me something the last one couldn't.
Somewhere along the way I became the person everyone came to when they were stuck, and that quietly turned into leading teams. It's the part I've come to care about most — watching someone go from nervous about their first release to running a whole area on their own. I've worked with people spread across India, the U.S., and Ukraine, and the lesson that keeps repeating is that clarity beats process almost every time.
I moved to the Philadelphia area in 2026 and I'm still learning the roads. These days I'm nose-deep in generative AI — language models, retrieval, the awkward question of what a machine should and shouldn't be trusted with — and I build small things on weekends to keep my hands in the code.
{{ post.excerpt }}
If any of this sounds like your kind of thing, write to me.
ashilpashree.com/writing
Notes on building software, working with people, and the parts of both that nobody writes down.
{{ post.excerpt }}
{{ current.date }} · {{ current.readingTime }}
{{ current.excerpt }}
{{ block.text }}
{{ block.text }}
Read next