I got this email from Danish, one of the early engineers at HackerRank.
I’m writing this email to you to ask you whether you’d be interested in a “Blog Questions Challenge”. It’s basically a set of questions you’ve to answer in a blog post and it works like a chain. So I’m currently writing the post and then I’ll tag some folks and they’ll do the same. A ponzi scheme without a scam at the end, sorta. Here are the questions:
======* Why did you start blogging in the first place?
* What platform are you using to manage your blog and why did you choose it? Have you blogged on other platforms before?
* How do you write your posts? For example, in a local editing tool, or in a panel/dashboard that’s part of your blog?
* When do you feel most inspired to write?
* Do you publish immediately after writing, or do you let it simmer a bit as a draft?
* What’s your favorite post on your blog?
* Any future plans for your blog? Maybe a redesign, a move to another platform, or adding a new feature?
* Who’s next?
======
Obviously, I was interested. So, here I go, sharing my answers.
Why did you start blogging in the first place?
I started blogging back in 2006, when it felt like everyone in college—friends, seniors, peers—had a blog. It was a natural thing to do: write about what you were learning, exploring, or just thinking about. Blogging turned into a habit, a way to make sense of ideas by putting them into words. It wasn’t about going viral—it was about documenting a learning journey, one post at a time.
Looking back, I’m incredibly glad I started when I did. I don’t think my blog is super popular or anything, but gives me a space to write about my experience, thoughts and learnings.
What platform are you using to manage your blog and why did you choose it? Have you blogged on other platforms before?
Right now, my blog runs on a self-hosted WordPress setup, and I’ve been using it for quite a while now. I chose WordPress for a couple of very specific and personal reasons.
First, back when I was still learning software development, I used to read through the WordPress source code just to understand how it worked. I was fascinated by how it was structured, how plugins were integrated, and how themes could customize the experience so effortlessly. It wasn’t just a CMS—it felt like a well-thought-out product with a clear philosophy behind it. That exposure deeply influenced my thinking around software architecture, and interestingly enough, a lot of the early architecture decisions at HackerRank were inspired by what I had seen and learned from WordPress. So for me, WordPress isn’t just a tool—it’s part of my developer journey.
Second, I genuinely love the freedom that WordPress offers. The vast ecosystem of plugins and themes makes it incredibly flexible. And on the rare occasion when I can’t find a plugin that does what I want, I can just roll up my sleeves and build one myself. That kind of power and extensibility is hard to find in many other platforms. Being able to completely own and customize your blogging environment is a huge plus for someone like me who enjoys building things.
I transitioned to WordPress when I finally got my own domain—sp2hari.com. That domain, by the way, was a birthday gift from my friend Manas, which makes it even more special. Before that, I was blogging on Blogspot, Google’s old blogging platform. My very first blog still lives at sp2hari.blogspot.com, frozen in time. It’s a bit of a relic now, and while I say this with a bit of embarrassment, it really does capture who I was back then: raw, naive, and figuring things out as I went. Don’t judge me too harshly for those early posts! I was young, still in college, and figuring out not just how to write, but how to think.
How do you write your posts? For example, in a local editing tool, or in a panel/dashboard that’s part of your blog?
I usually write my blog posts directly in the WordPress editor. Over the years, I’ve found it to be simple, convenient, and just enough for what I need. Since I already manage my blog through WordPress, it feels natural to write in the same place where I publish—it keeps everything in one flow.
I typically start by creating a draft with just the title or a rough outline, and then revisit it when I have more clarity or time to flesh it out. The built-in formatting tools in WordPress are more than enough for my use—especially since my writing is mostly text-focused, with the occasional code snippet or link.
Sometimes, I might jot down quick ideas in my notes app if I’m on the go, but the actual writing and editing always happens in WordPress. I like seeing the post take shape in the same environment it will be published—it keeps me focused and minimizes the overhead of switching tools.
When do you feel most inspired to write?
Interestingly, most of my writing inspiration doesn’t come from a sudden burst of creativity—it comes from a commitment. I have an ongoing blog bet with a few friends where we each have to publish a post at least once a month. That external accountability, paired with the looming deadline, is usually all the motivation I need.
In fact, most of my blog posts are the result of last-minute panic, where I scramble to organize my thoughts and hit “Publish” just in time. It might sound chaotic, but that pressure has consistently pushed me to write, reflect, and share—especially on weekends when the deadline is near.
The blog bet has become a great motivator, not just for consistency, but also as a fun shared ritual with friends. I’ve written more about how it started and what it’s led to here: Writing Bets Experiment. For now, it’s safe to say that structured panic is my main source of inspiration!
Do you publish immediately after writing, or do you let it simmer a bit as a draft?
I usually don’t publish immediately after writing. My process typically starts when I get an idea—often sparked by something I read, a conversation, or a moment of reflection. When that happens, I quickly jot down a potential title or a rough heading for the blog post. That title acts like a placeholder or a mental bookmark for the topic I want to explore.
From there, I begin outlining the structure with subheadings or key points, even if I don’t yet have the full content ready. It’s a way for me to scaffold the post, giving it some shape before diving into the details. Sometimes, that rough draft sits for days or even weeks while I mull over how I want to approach the topic.
When it’s time to publish—usually prompted by a personal deadline or one of my blogging bets—I sit down and write most of the content in one focused session. That’s when I give it the final fit and finish: refining sentences, fixing flow, and making sure the message is clear. So, while the post might look like it was written quickly, it’s usually simmered for a while before it reaches the final published version.
What’s your favorite post on your blog?
One of my favorite posts on the blog is “Advice for a Junior Software Developer”. Among everything I’ve written so far, I truly believe this is the most useful and impactful piece. It came from a place of genuine reflection—thinking back on my own early years in the industry, the mistakes I made, the things I wish someone had told me, and the small mindset shifts that made a big difference.
This post is special to me because it’s not just advice; it’s a consolidation of real experiences, hard-earned lessons, and encouragement that I hope every junior developer finds at the right time. I’ve had friends, peers, and even strangers reach out saying they found it helpful or that it gave them clarity—and that means a lot.
While I’ve written about a variety of topics over the years—some technical, some personal—this one stands out because it feels like it has the potential to positively influence someone’s journey. That’s the kind of writing I want to keep doing: simple, honest, and useful.
Any future plans for your blog? Maybe a redesign, a move to another platform, or adding a new feature?
As of now, I don’t have any major redesigns or platform changes planned for the blog—I’m pretty happy with how things are running. That said, one idea I’ve been playing with is writing a focused series of blog posts around a specific theme. In particular, I want to explore the journey of how a programmer or coder evolves into a true developer or engineer—not just technically, but in terms of mindset, habits, and thinking.
It’s something I’ve thought about often, especially when mentoring or reflecting on my own growth. There’s a big leap between just writing code and building systems, understanding trade-offs, communicating effectively, and taking ownership of a product or problem.
The goal would be to take this series beyond the blog—ideally, once I have a strong collection of well-thought-out posts, I’d love to compile and refine them into a book. It wouldn’t be just a how-to manual, but more of a guide for the transition, both practical and philosophical. It’s still just an idea for now, but it’s one I’m excited about.
Who’s next?
Adyasha, Ishan, Shloka and Vaasavi – you’re up next. No pressure!