The Documentation Conundrum Any typical code base, given enough years, becomes large enough to find it difficult to maintain documentation for. Every new piece of code I saw in my career had one of the below 3 issues with regards to documentation : No Documentation Incomplete Documentation or Outdated Documentation So I started on a quest to find out what’s the best way to document your application and the internal implementation, and I shall try to summarise my findings to the best of my knowledge.

This is the first in a series of mini thought-bytes from my experiences. There will be a lot of times when your actions will be misinterpreted or your words will be misconstrued in unimaginable ways. It’s bound to happen more than once in your career, so what can you do about it ? The first step is to have an open conversation with whoever raised the concern, and listen, not talk.

Notes on Technical Leadership and Problem Solving Recently I had a deep dive conversation into what the role of a technical leader should be and wanted to share a few points here. There are lot of aspects to consider here Setting Platform roadmap and vision Before we can set a roadmap and a vision for where the platform should be heading, it’s important to first understand it in-depth. Once you have that level of detailed knowledge about the current system, changes and roadmap can be proposed with a level of certainty in mind.