Rahul gives unsolicited advice

In December 2022, I was on the All Things Policy podcast to talk about  An Open Tech Strategy for India  with Bharath. Bharath is the Programme Manager of the Graduate Certificate in Public Policy (GCPP), Technology and Policy programme at Takshashila. at the Takshashila Institution. You can listen to the podcast at the link above. I was a nervous wreck before the podcast but it was a lot of fun. We recorded the podcast right as I was finishing the GCPP Tech & Policy programme and I tried using as much of what I had learnt in the course in crafting what an Open Tech policy would look like. You might have noticed from my recent blogposts that I'm getting involved in Tech Policy circles. Over the next year or two, I hope to get enough exposure to decide whether or not I can do this for the rest of my life, maybe even in a professional capacity.

On Friday, Arun and I talked mostly about two things - documentation and processes. Arun is working on documentation and he was wondering whether or not he should document the failure modes of an external tool that is used as part of a process. This gave way to a broader discussion on what should be documented and when. In this particular instance, I talked about how documenting the failures of an external tool internally feels unnecessary unless the external tool has no documentation to speak of. There can be a basic expectation from the developer that they can look up the tools' documentation if and when necessary. In general, we talked about deciding whether or not to document something depending on how much time it can save a person/company. If it can save a person one or more hours per week, the savings can add up to thousands of dollars per years. If the documentation can only save a few hours an year, then it might not be worth spending time working on that piece of document