Coding tip — Code with a mindset as if your code is going to production after …

Before you put your hands on the keyboard and write any code, ask yourself the following question:

When I write and eventually push that code (even if it is to a feature branch) to the repo and somebody automatically promotes that code to production, will it negatively change the experience and will it even positively change the experience that the product team is not yet ready to release?

If the answer to both parts of the question is YES, then you need to step back and see how you can code it in such a way where you are encouraged to promote to production more often and answer the above parts of the question with a NO.

Ask yourself if you were doing main trunk development and what you would do in those situations.

Feature toggle and feature dial is the way to go. Don’t underestimate its power. The less code you pile up in develop and feature branches, the less pain you have in those branch merges and the less risk is added in testing and ultimately for your customers. We all know that with feature toggles, we will need to be more disciplined in cleaning that code regularly, but the net new benefits of feature toggles justify all of it.

Thank you for reading this short post. Keep geeking out!

Almir Mustafic