I started reading The Pragmatic Programmer: From Journeyman to Master when I was at Multunus. It was early in my career; I used to write blog posts summarizing whatever I learned. I wrote mostly for myself. I didn’t have many readers. The goal was to learn, and writing was the best way to do that.

In March 2014, Dave Thomas and Corey Haines spoke at Agile India 2014. They were invited as guests to the Bangalore Ruby Users Group meet-up. My colleagues and I had the chance to listen to Dave’s talk, “Elixir Language.” The language was new and functional, and the talk was interesting. Later, I tried Elixir and wrote a few posts on that too.

After the talk, there was a small, informal session to meet and introduce ourselves. As an introvert, I didn’t plan to chat with him. But with a little push and help from my colleagues, I told him I was reading The Pragmatic Programmer and writing about it on my blog. I was hesitant, and a little scared too. But Dave’s response was encouraging. He appreciated it and asked me to continue writing. He also asked me to email him a link to my blog.

I wasn’t expecting much. I was just happy to meet him, tell him about the blog, and have a photo with him, with my colleagues who had pushed me to say hello.

I emailed him the link later. He replied that it was fantastic, and asked if I’d mind him sharing the link on Twitter. I said of course not, and he did:

For a newbie like me, this was an uplifting moment. I had less than a year of experience at the time, and the author of the book I was reading and enjoying inspired me to keep writing and sharing, and tweeted about me to his audience. I’ve returned to The Pragmatic Programmer multiple times, and I still consider it one of the best books I’ve read on software development.

Over the years, I wrote code in different languages, frameworks, and domains. I completed my Master’s. I continued writing blog posts, albeit less often, and the topics ranged from languages to image processing. I read many technical books, and didn’t make time to write about those. Around the time I met Dave Thomas, I had also written about simplicity for the first time, summarizing Venkat Subramaniam’s keynote, The Art of Simplicity, at Agile Kerala 2013. With experience, I found that sometimes, context matters more than the rules, but it was difficult to explain that in words.

Then, last month, I picked up another book by Dave Thomas: simplicity: sustainable, humane, and effective software development. The book offers practices you can use in your life as a software developer. It felt familiar, coming from an author I loved reading. The practices reminded me of the named set of tips from The Pragmatic Programmer, yet they were different. As a beginner, those tips were necessary. But simplicity offered something different that I could connect with as an experienced programmer.

The disclaimer says these are not rules, but practices, and we use our own judgment to decide when to apply them. That was the missing piece I found difficult to put into words. Rules are black and white, but practices thrive in the grey area.

Many practices go beyond programming. Have Empathy for Things and Spin a Story aren’t about code at all, and anyone can try them. Dave Thomas explains these in the context of software development.

Here is another practice that stood out while reading the book:

Spread Your Skills: Share what you learn to help others and yourself.

Twelve years ago, this is what I was doing: trying to share what I was reading, and Dave Thomas gave me a motivational boost by sharing my blog. The book nudged me to pick it back up. The time I was writing was when I was learning the most, trying to explain the concepts I read. It gave structure to the explanations in my head and helped me turn them into organized words.

Reading is easy, but writing about it isn’t. Earlier in my career, I did that confidently and effortlessly. I was new, and I wasn’t afraid to ask questions or share even simple things I learned. But now, when I am more self-aware and second-guess what I write, Spread Your Skills is exactly what I needed to hear.

Sometimes a reminder is all you need: Ask simple questions, and write about simple stuff. Now I’m getting back into the habit to help myself and others. It doesn’t need to be complex. I don’t need to use big words. It just needs to be simple and thoughtful.