It helps. Each product can now be viewed as a general scientific hypothesis; so publishing your work is essential. You wouldn't be writing _on MVP development_

It helps. Each product can now be viewed as a general scientific hypothesis; so publishing your work is essential. You wouldn't be writing _on MVP development_ but rather exposing to everyone just how well you are at executing it. In my mind, your question seems like asking, "Is it a good idea to write an ebook on the scientific method?" You have to manage what kind of philosophical posturing you're going to make. What you will write about may not necessarily translate to other projects, and that'll be for the fact that your hypotheses will be defined by the nature of your product. I believe what I'm saying is consistent with "don't choose your tech stack first" since the product's nature determines what the tech stack will be.