I have an AI subscription with daily credits that reset every 24 hours. Somewhere along the way, 'credits remaining' stopped being a number and started being a compulsion.
Read more...
A manager asked me where I saw myself in five years, and I froze. Not because I didn't care, but because I genuinely didn't know what the options were. It took me years to learn that the career landscape in software engineering is wider than most of us realize.
Read more...
Programming languages aren't just syntax and tooling. Like natural languages, they carry tribal codes, community values, and cultural expectations that shape how we think about problems and why we argue so passionately about technology choices.
Read more...
Nobody gave me a reading list when I started my engineering career. I learned through messy codebases, painful code reviews, and years of not understanding why things worked the way they did. Curating a book library for others forced me to confront everything I'd learned the hard way.
Read more...
A mentor asked me why some people think bigger than others. My answer surprised me: curiosity is the fuel, but it needs discipline and knowledge to actually go anywhere.
Read more...
We spent months discussing data structures, matching algorithms, and scoring strategies for a new search system. It generated more meetings. Then I built a simple side-by-side comparison UI out of desperation, and jaws started dropping. Why does making something tangible work so disproportionately well?
Read more...
A happiness researcher's conversation about what makes entrepreneurs thrive made me realize the same three principles quietly shape whether engineering work feels fulfilling or just feels like work.
Read more...
After years of watching perfectly good proposals die quietly while weaker ideas gained momentum, a book on cultural psychology gave me a framework for understanding what was actually going on. The quality of the idea was never the real problem.
Read more...
The best engineers I've worked with rarely have all the answers. What they have is something more valuable: the confidence to admit what they don't know and the drive to figure it out anyway. This mindset might be cultural, it might be situational, but it's definitely learnable.
Read more...
When organizations try to rethink how they work, the same patterns emerge. Cross-functional teams, hackathons, new pod structures. Some spark real change. Most quietly fade. Observations on why, drawn from watching these cycles play out.
Read more...
In most meetings, someone has a question they're not asking. The evolutionary wiring that kept our ancestors alive now keeps us silent when we should speak up. Here's why I've made it a practice to ask the 'dumb' questions, and why it matters more than you think.
Read more...
Just because I learned to make excellent pizza during the pandemic doesn't mean I should open a restaurant. The same logic applies to polished prototypes that spark premature excitement about production readiness.
Read more...
My zigzagging interests often made me feel 'not engineer enough.' David Epstein's 'Range' helped me understand why diverse interests and analogical thinking might be exactly what complex engineering challenges need. Sometimes wandering isn't being lost; it's building a different kind of map.
Read more...
Like most initiatives it failed, and what I learned from launching a Design Authority that never quite took off. The real lessons aren't just technical. They're about process, culture, and tooling working in harmony.
Read more...
A decade of home automation tinkering became an unexpected lesson in technical debt and feature creep. From one problem-solving smart bulb to a complex system requiring documentation for guests, this is how my smart home journey mirrors the software development patterns we all know too well.
Read more...
Inspired by Arthur Brooks' insights on finding purpose through helping others, I'm creating this space to share thoughts and experiences from my journey in tech.
Read more...
