Member-only story
Over Engineering with Best Practices, Good or Bad?
Following best practices is very important to make great software. The question is, should we blindly follow them in every project and make things complicated?
Things are changing really fast and even if we spend years to build something, there will be changes to that. The bottom line is we can not really predict the future, so why we need to take care of every possible scenarios and build a software with features that we do not want RIGHT NOW.
The best is to keep things simple (KISS) until “simple” is no longer satisfactory. KISS is not about writing bad code just to keep things simple. Its about writing simple elegant code and come up with a solution that can be extended when need arises.
The over-engineered or over-architected projects will be dragging forever and maintenance will become complete nightmare.
We should try to strike the balance between following good practices and keep things simple. In other words don’t make a missile to kill an insect ;)
Many time we developers telling, its going to be easier to rewrite a feature than fix it. This is because maintaining over-engineered code without a reason is a painful thing.
