Tag Archives: mmm

August 9, 2025: Weekly Notes 2025/08

  • August 9, 2025 is Rakshabandhan which is a big festival. For many years, it has stopped being exciting for me, just like Holi and Diwali. When I was a kid, Rakhi used to be an exciting day. My three buas will visit us, stay over for a day or two and bring sweets and of course rakhi for their brother (my dad). The sweet of the season was ghevar. I don’t find that kind of ghevar here in Bengaluru. Perhaps you won’t find it in any big city unless you search for it. The sweets made in the villages and town are cheap. There is just not enough margin for shopkeepers/online platform to sell them.
  • I finally got a hard copy of one of my all-time favorite book. When I read this book last time a few years ago, I had no strong feeling about project management. This time the intentions are different. The reread is a very different experience.
  • https://pocketcasts.com/podcasts/9d4880a0-6a51-0139-3424-0acc26574db2/8c1458b3-3c4c-4be5-9429-5eb681d41172 was a good podcast. It resonated with me quite strongly.


    Ninety-five, [perhaps] 99% of the applications on the planet are and should remain monoliths. Full stop, end of story… I mean, I love distributed systems. I’ve lived in it for about 25 years, and, like, I just get joy from doing this kind of thing. And I read the papers, and, like, I find it super exciting… The vast majority of you should only be dragged kicking and screaming into distributed systems rather than starting from the beginning.” — Randy Shoup


    image.png -- A Classic Book: The Mythical Man-Month
  • I need to plan my weekends a bit more seriously. Last three weekends were not very productive.

  • I wrote a few (wip) design docs at work. Doing a good job at them is really hard and time-consuming! Totally agree with Writing a good design document and many comments on HN on this topic.

    > Think of a design document like a proof in mathematics. The goal of a proof is to convince the reader that the theorem is true. The goal of a design document is to convince the reader the design is optimal given the situation. The most important person to convince is the author. The act of writing a design document helps to add rigor to what are otherwise vague intuitions. Writing reveals how sloppy your thinking was (and later, code will show how sloppy your writing was).