❖ step 1: create something that is useful and provides opportunity for developers.

❖ step 2: create interfacing functions for said thing such that developers can begin to expand upon it in various ways.

❖ step 3: wait until significant documentation is written for your API, and many tutorials are created on how to use it. As a bonus you should wait until many applications utilize the functionality provided by the specifics within the API before moving on to the next step.

❖ step 4: come up with some changes to upgrade the API and post about it on your blog, then mention if developers don't upgrade to the latest implementation their applications will break, and convince yourself that everyone is reading your blog anticipating this upgrade. Be sure to ignore the idea that documentation and tutorials have any worth whatsoever.

❖ step 5: break everything

There are some semantics involved in correlating this to steem,
but seriously, WTF?
The thing I really don't understand is how this kind of development is praised. "Wow, thanks for all the hard work and upgrades!", so you want to tell me that if I make a foundation for your house and later on come back to play jenga with the blocks it's made from and collapse the entire structure any time you're not actively rebuilding it you would be happy?
How many things at http://steemtools.com/ are in active development?
...