Think twice, code once! - by Bruno Kiafuka - BK's Essays
When I review code from more junior developers or even tenured developers, I find a tendency to either overengineer or overcomplicate solutions. When I ask them to explain the rationale behind their implementation, I get an answer that feels like this was their first thought, and they implemented it without analysing why their approach is ideal.
I ran through the same issue for so long until I heard a quote that said — “ think twice, code once”, — and I incorporated it into my process; given that I like to visualise my thoughts .
Ideally, we should strive to produce maintainable and scalable solutions that are also easy to understand and test. Let’s say you have a task to add to optimise a feature on a given app. At first glance, you may have an idea of what needs to be done and how, but then you decide to jump straight to implementation.
Going straight to implementation would be the best and fastest thing to do, assuming you have an idea of what needs to be done. Regardless of how much context I have on the feature, here is what I would do:
