TaoOfSatoshi
Well-known member
Are all Masternode operators financial advisors or not?Are all Masternode owners technical experts or not?
Are all Masternode operators financial advisors or not?Are all Masternode owners technical experts or not?
This sounds fair. You went from being the one of the worst contributors on this thread to one of the best!"So really the better way to set all of this up is to have each task tied to a budget"
In my experience the solution you are proposing would be a terrible way to manage a software development project and typically leads to chaos in terms of trying to build a quality product and take it to market.
To give you an analogy, let's imagine Sony is building the PlayStation 5 and has a new system where the shareholders can vote on individual tasks and hire professionals to do that...
What is the CPU, GPU, sub system architecture? What is the OS? How many USB ports will it have? What is the backwards compatibility? What is the thermal solution? Where should it be manufactured? How should it be marketed?
Right now Sony's shareholders appoint a single team to achieve that which is internally organized and allocated basically a single budget. They work together internally and develop the product and take it to market and report to the shareholders at stages. This is essentially the same for every successful company on the planet.
But by opening up each part of that design / production lifecycle to different groups without a single lead you just end up with a mess, that's over budget and overtime and fails pretty much all the requirements in my experience.
Because by removing the brain of that project team and replacing it with the shareholders to manage, you are removing the professionalism, experience and knowledge required to do it effectively and replacing it with a disparate group each with their own interests / agendas and probably lack of experience, otherwise they would be doing the work and not be the shareholders in the first place.
What you end up with is a meltdown where shareholders would be constantly fighting to micromanage each part of the development and without any leaders who can view the whole lifecycle from the top down and make the correct/difficult decisions to balance all the various elements that need to be considered and resources that need to be directed (including human resources) to deliver a cohesive and quality product.
It's just a basic fact of engineering great products that you need leaders with the vision and experience in how to do that leading the show whether that's an iPhone, Ferrari, Operating system or space shuttle. How that is decentralized in Dash is that rather than a benevolent dictator at the top, we split areas of the project into teams each with their own benevolent leaders, and those leaders can be replaced - the core team is an example, Evan is leading it with the permission and funding of the network. If the network disapproved, it could cut off his funding and has $40k or whatever per month to hire a new team for that specific role, i.e. development of the core project. That is about as decentralized as any organization that wants to succeed should go as far as my experience goes.
So micromanagement of project is something that Dash needs to actually prevent to survive, same as in any company with shareholders (and i have invested in 1 medium-sized venture that failed largely because the shareholders gained too much power and were then able to use their voting rights to micro manage the technical development and it ultimately cost the shareholders a lot of money and with what you are proposing I can see a similar thing happening actually).
What tends to happen in that situation too is that developers basically end up downing their tools and saying 'this is ridiculous' with having the direction changed and disconnected ideas from different people who think they know what their doing but don't have the professional experience. One can imagine the same scenario in many types of project where creators are tasked to do something and the stakeholders don't let them 'get on with it' but instead jump in and try to change everything mid flow - it just ends up with a mess.
Another major thing that goes wrong with this model is you have a massive increase in inefficiency caused by the increase in reporting and communication required for developers forced to have to present everything they were doing at different levels and have this 'approved' by a mass of stakeholders constantly throughout the lifecycle, who are all fighting each other to get things done how they wanted.
Therefore the best way to develop a software product and take it to market is to appoint an experienced team that works well together and fund them to do that and get stakeholders to approve and fund that at a high level with control/reporting limited to intervals where deliverable / goals are pre-agreed and metrics are used to monitor that and asses that.
Hope I explained it well enough. I'd be interest to hear if anyone with professional experience in product development or team management would disagree with this and why.
Andy
Andy, you pretty much went down the rabbit hole on that one. LOL. I was just trying to prove a point that the masternode voting can't really force developers to work on anything in particular. It can really only determine how many funds go to a person/area."So really the better way to set all of this up is to have each task tied to a budget"
In my experience the solution you are proposing would be a terrible way to manage a software development project and typically leads to chaos in terms of trying to build a quality product and take it to market.
Andy
NO, that's why I wrote this in one of my previous post:Are all Masternode operators financial advisors or not?
Relax, I was just being facetious... I'm a puppy, remember?NO, that's why I wrote this in one of my previous post:
This, is my opinion, should be the role of MN network. Giving power to steer every aspect of the project to the MN network will end-up with a royal mess and failure (it doesn't work in a real world and won't work here - Andy explained why).
- Masternodes (investors) provide infrastructure for Dash and budget for projects (project sponsor role).
As @yidakee pointed out - we are talking many times about the same thing here...
Cheers
great info, agree. thanks@AndyDark Well said. Here is an article from a lawyer who reviewed the Slock.it DAO governance model. Their model is similar to what we have now and he picks it apart pretty well. I think Evan is on the right track. http://www.cameronhuff.com/blog/slock-it-dao-paper/index.html
Relax, I was just being facetious... I'm a puppy, remember?
This sounds fair. You went from being the one of the worst contributors on this thread to one of the best!
Cheers.
Andy, you pretty much went down the rabbit hole on that one. LOL. I was just trying to prove a point that the masternode voting can't really force developers to work on anything in particular. It can really only determine how many funds go to a person/area.
But to address Tao's question. If a developer requests a vote from the masternodes, the voting system is a fair system and the votes tallied can be considered an accurate network decision. (This is actually really impressive and incredibly important). Now the interesting thing that Tao is seeing is that it only works when someone that is able to offer an option(a developer) is requesting a vote. If a new option A project and vote pass, it can't enforce a change to implement option A - in this case a forum discussion is probably more effective.
@AndyDark I am 75 years old and have spent most of my life working on high risk edgy projects. A fatal attraction I suppose. I have long history of participation in failures as well as a few significant successes. Don Quijote and Sancho salute you!
And BTW there is a windmill over there that has been threatening us. A fellow who bought me my horse ttolld me so.
I know what facetious means, but thanks for posting that.@tao, with all due respect, we are trying to build a project that is anything but facetious.
Facetiousness is one of the greatest threats to serious business development.
There is a time a place for humour.
.
I know what facetious means, but thanks for posting that.
My style is my style, and I would appreciate it if you would let me express myself how I see fit, as I would extend you the same courtesy.
We are in complete agreement that this project is serious, but features people of all nationalities, styles and backgrounds coming together to make a team.
We would do well to understand each other, promote tolerance and not presume to lecture others on their personal style. With respect.
Did you miss the part where @kot, @AndyDark, @Solarminer and myself were starting to agree on things? We had a respectful talk, opinions and input was considered, and a consensus was formed, which was the goal of this thread to begin with? What is your problem with me? I don't know how to be more diplomatic...I've never to this day commented on your style, even though it's not particularly my cup of tea. I'm sure it's a mutual feeling.
But when we spend 13 pages going round in circles, requesting enlightenment on how things operate, and those doubts addressed, and simply not acknowledged, and just keep repeating the same questions over and over... people do tend to get frustrated.
When you candidly say you're just being facetious, it ceases to be your natural fun-loving style and just becomes plain obnoxiousness. I'm sorry you can't see that - afreer, kot and I keep courteously answering them, but keep getting challenged on the same issue over and over anyways....
For one to be preach tolerance, one must practice tolerance, and you've been completely intolerant to the answers given for 13 pages now, despite your warm "why can't we all just get along" prerogative.
And again, we don't all make up a team, we make up a community that has a team. Or many teams. Anyone can create a team and work. Operating word here being "work" - towards a common goal, put forth by the founder and creator of this project.
.
OK, in case you need me to spell it out for you:@TaoOfSatoshi
No I didn't miss it. I had hopes for advancement. Did you miss, on this very same page, the exact opposite and once again doing exactly what I described?
My problem with you right here right now is that you're like a "dog with a bone" - simply not letting go. Maybe it's the dalmatian in you, I don't know. I', just seeing that every time a page rolls over, you go back the the same premise. You're taking the discussion backwards - look, just read what @kot wrote not a few posts back!
.
OK, in case you need me to spell it out for you:
WE HAD A TALK. I GOT MY CLARIFICATION, I SEE THEIR SIDE, THEY AGREE THAT EVENTUALLY WE NEED TO DECENTRALIZE MORE, BUT NOW IS NOT THE TIME. WE REACHED A CONSENSUS.
I, for one, consider the case closed, having reached the clarity and consensus that I wanted from the beginning. With seriousness, and not a trace of facetiousness.
Do you understand me?
Now, if you'll excuse me, I'm going to go continue bringing more people and talent into Dash Nation. That's a way more productive use of my time.