Blogs

Four exhausted people, five huge bags, and a hotel that would not let us check in early taught me to plan trips differently. This is the checklist I use now, and the story of the day that produced it.

It is not the food. From a first visit for a Grab workshop in 2019 to moving there on an internal transfer, these are the five things about Singapore that made it stick, seen from the inside.

I wrote this from a sickbed at my parents' place, in the middle of upskilling and in the middle of doubting myself. It is a reminder of why I started, going back to an astrology website I coded at thirteen.

I came out of college with five hundred solved problems and the belief that engineering was a coding contest. It was not, and this is what the first year on the job taught me instead.

It is not just about solving algorithm problems on CodeChef and Leetcode. These are the six things I think are worth your time in college, written six years into working as an engineer.

A holiday planned to the hour ended with us enjoying ourselves only after we dropped the plan. I use that trip to look at how the same urge to control everything shows up in how people invest and build careers.

On-call is the week most engineers dread, but it is also the fastest way to learn how a system really works. I argue that it is worth wanting, and share what to do when you are the one holding the pager.

I kept signing up for every webinar and course and ending up with nothing to show for it. This post is about why spreading attention across everything leaves you with no depth, and the go-broad-then-go-deep split that finally worked for me.

Documentation is the part of engineering that most often gets skipped. After writing a hundred wikis, I look at what they changed for the team and for me, and how to make writing them a normal part of shipping.