> If you hit something successful, that's when it's time to start thinking about these ideas I agree with you completely. But the article did not specify the u

> If you hit something successful, that's when it's time to start thinking about these ideas I agree with you completely. But the article did not specify the use case of these guidelines. They are not to be applied (in my opinion) for research code when you quickly need to publish something. They can be useful however when your already proven and battle tested ideas are used by other people. For example for keeping a shared code base inside a lab, or when you want to provide a robust implementation on top of your ideas.