Fast-paced vs Right-paced
Sometimes it is hard to tell how fast the current's moving, until you're headed over a waterfall. - Kimberly McCreight Not always is it the best way to work on something so restless to increase productivity. For something that can be done in a week, if it took a couple of weeks, instead of scrutinising on the extra hours spent, start analysing the output of the work. We often end up not appreciating doing documentation around something that we write. "Oh, we need to get the MVP to production, no free-time for documentation!", is something that I hear so common. The catch over here is documentation is not something to be done on your free-time. It is something non-negotiable, which we at times forget to understand. The question here is, "What is this piece of work, if there is no manual for the users to understand how to make this work? If there is no operating procedures, for the people who maintain or support this can understand the internals, what is the point
