The assumption is this:
Steemit, Inc. Knows What They're Doing
Are they going to implement your favorite feature? Maybe. Probably not, though. Are they going to do it perfectly? No. Are they going to try their very best? Yes and they have an incentive to do so.
Will Steemit, Inc. do anything it takes to go mainstream, even if it means abandoning early adopters? Yes.
You might say, "What? They can't do that! They can't abandon the early adopters!"
I didn't say they would abandon their early adopters. I'm saying that they are willing to if it means going mainstream.
Want to know what they're up to? Read on:
Quotes from The Mythical Man-Month by Frederick P. Brooks, Jr.:
The opportunity to be creative and inventive in implementation is not significantly diminished by working within a given external specification, and the order of creativity may even be enhanced by that discipline.
We don't get to look at the full specification before the developers. We can only jump to conclusions from the current iteration.
By documenting a design, the designer exposes himself to the criticisms of everyone, and he must be able to defend everything he writes. If the organizational structure is threatening in any way, nothing is going to be documented until it is completely defensible.
Yeah, the documentation sucks. Just suggesting such a thing is threatening. They're working on it, but that's what they're up against. It's normal.
It is more important that milestones be sharp-edged and unambiguous than that they be easily verifiable by the boss. Rarely will a man lie about milestone progress, if the milestone is so sharp that he can't deceive himself. But if the milestone is fuzzy, the boss often understands a different report from that which the man gives. To supplement Sophocles, no one enjoys bearing bad news, either, so it gets softened without any real intent to deceive.
We have a roadmap with some pretty sharp edges in terms of timeframe. Maybe it doesn't go where you want to go. Deal with it.
This does not mean there will be no course correction. The wonderful thing about having a roadmap is that if there is any course correction, we'll know where we were going and where we're going now.
The brain alone is intricate beyond mapping, powerful beyond imitation, rich in diversity, self-protecting, and self-renewing. The secret is that it is grown, not built. So it must be with our software systems.
This is why it's right to be excited about a new voting button animation. Small incremental changes will add up. This is not to say there cannot be large sweeping changes. But they will take the form of going from State A to State B, not right to State F like we users tend to prefer.
Organizations which design systems are constrained to produce systems which are copies of the communication structures of these organizations.
I'm just going to leave this quote to stand on its own.
An omelette, promised in two minutes, may appear to be progressing nicely. But when it has not set in two minutes, the customer has two choices—wait or eat it raw. Software customers have had the same choices. The cook has another choice; he can turn up the heat. The result is often an omelette nothing can save—burned in one part, raw in another.
Although I want Steemit, Inc. to stick to the timeframes set out in the roadmap, I also do not want them to just turn up the heat if there is any slippage. It's their call. They know what they're doing.
The general tendency is to over-design the second system, using all the ideas and frills that were cautiously sidetracked on the first one.
Lucky for us, the STEEM platform is the third of Larimer's systems. This means the frills that were added to the second system (BitShares) have been pulled back a bit and corrected.
Also see: To Be The Best In Crypto
Lol, I can find you even in posts this old. How are you everywhere?
Assume = Making an ASS out of U and ME
Yes, indeed.
And this is where i hate the words "We just have to wait and see" assuming they do know what their doing. There is still the community to keep them in check, tho i can see now why they are trying to be more transparent. Its bad enough many people think steemit owns steem. But ehh i Guess
Steemit Inc, as any other software company, needs to implement (if not done already) proper product management. The product manager is responsible for what get into the next release(s) and to not over promise in terms of time lines. Roadmaps are there to be changed, however, the next release should always be clear, since also development is doing their work towards the next release. Let's assume these topics are kind-of-covered and more or less properly implemented. In addition, Product Management has more responsibilities such as 1) communicate to the customer their plans 2) provide good documentation 3) provide material to sell to suspect and prospect users 4) define partner program incl plans, documentation and defined roadmap with feature to support 3rd party apps 5) make clear where the boundary is set between Steem Inc software and external (eg Steemit Inc Steemit UI...will this be developed further? and when so, this needs to become part of roadmap big time! and when not, who then and how are they compensated? a backend does not work with a solid front end).
I'm glad to believe that there's someone up there knowing what he's doing. it's reassuring ;)
From this thread you can see ...
Isn't happening for sure.
Greetings @inertia! Are you the moderator "inertia" on OpenBazaar? If so, could you please login and tend to a few disputed/stuck cases which "intertia" is the moderator for, and which have been in dispute for a cpl months now? If you're a different Inertia, then my apologies... Regards!
I am inertia on OB. If people are using me as a moderator, that worries me because my store hasn't been accessible in a few months. I've been troubleshooting it here and there, but no luck.
I've logged into OB slack and I'm going to do more troubleshooting now.
I'm happy to send you a loaner RasPi with OB on it so you can config with your user ID and pw, if that would help you?
Sorry for the confusion. I've looked into it, but I believe the "inertia" who has moderation cases is not me. My store has been down since December and I do not see any open cases in the database.
Hmm, I see. But are you certain? Just to be clear, this "inertia" is not you, then: ad79ca496a7d4373f04951b558a17af42497cd66 ? As this inertia does list the same URL for the blog as you list here..??
I know of at least 3 pending dispute transactions with the above inertia, we just need them to help get the coins moving again.
ad79ca496a7d4373f04951b558a17af42497cd66is me. But there are no open disputes on my store. I got the store running yesterday and it has been running pretty smoothly. Here is the full list of disputes I've been moderator on, as seen from in my client (only 1):Ahh, your node was running earlier, but not seeing it now - if your node can remain online for a time, we can try to resend the start of the dispute and perhaps your node will pick it up that way.