You ever heard someone say 'do something, even if it's wrong.'? I have, and I avoid folks like that in my industry, because they cost me a lot of money.
Here's something I like to keep in mind: if you don't take the time to do it right, you'll make the time to do it over.
I work in construction, where things get cast in stone. Doing it wrong costs more than three times as much as doing it right, because you first pay to do it wrong. Then you have to pay to undo the wrong you did. Then you have to pay to do it right, finally. Then there's the additional loss of time and money not having the right thing done costs you by delaying other things that depend on it.
That's if you're lucky, and you don't have to fix it again. You don't have to lose money too many times that way before you learn to think as long as necessary before acting.
We don't want this to end up costing us money. We're doing this to make Steem more valuable.
I agree with your sentiments and I can imagine in construction it can be a problem! I work in tech and I’ve built plenty of sites and applications for startups to large scale corporates and in my experience it’s better to move fast and break things
Since tech can scale easily the money you waste on time debating a solution can be far more than selecting a poor implementation you create a system you test the load you get data and you refine! Tech is fluid it’s nimble and can be adapted as long as you start doing and iterating, you only find the best solution through data and user interaction
I’m not saying it’s the only approach to things it’s just one I’ve personally use and advocate and I’ve had a lot of success with it
Posted using Partiko iOS
While tech as an industry is fast and nimble, it is through evolution that this is expressed. In other words, those individual companies that fail and break die, and the rest of the industry continues along without those failures.
Individual companies that can quickly recover from failures that break them can be fast and nimble. Steem requires a consensus of witnesses to implement code after that code has been developed, and that is after learning what code should be developed. All that takes time, and is not fast and nimble.
We need to carefully NOT implement code that will break Steem, as it will take months to recover if we do break Steem. Steem is not fast and nimble in that sense, and the DAO will make it far less nimble that one stakeholder being able to decide what it wrong and fixing it has been. Just grasping as a community that there is a problem, and then deciding what to do about that problem, will take more time than Stinc took to fix the RC problem that came from HF20, for example.
Steem development has only been funded through direct spending of the stake of a single stakeholder to this day. The DAO is intended to enable us to fund development, and spending the stake of Stinc to do that is no longer going to be the only means of doing so.
Speculating that reducing spending on marketing to increase spending on development - which is what drawing from inflation will do - without negative consequences to marketing, is foolish, and I am confident it will harm Steem.
Let's give this a lot of thought before casting it in code that will take months to undo if it's done wrong.
So even doing that as fast and nimble as you tell... you're in the tech a minimal plan is needed for avoid to lose money. That's mentality is the mentality created by Microsoft on Bill Gates time. Nowaday even them planning for long term before announce a product.