You are viewing a single comment's thread from:
RE: "Our Corrupt Sense of Fairness" or Steemit's Incessant Rule Changes?
The issue I have with rule changes is that they aren't happening, but they are often happening much too quickly, and too many rules change at once!
Good science lets you change one 'knob on a console' and then observe how that change affects an experiment. You don't change 5 parameters at once and then accurately determine which of those 5 parameters affects the outcome of the system.
I don't think that's the problem. We're still in beta and iterating quickly is important in the early days. Lack of ability to iterate quickly has slowed Bitcoin down quite a bit.
In my view, the main problem is that the changes aren't being made in a completely transparent way. Sure, everyone can see on Github but Steem is attracting lots of non-technical users. We need a changelog and central repository that has the up-to-date rules so non-technical Steemians can stay in the loop: https://steemit.com/steem/@ntomaino/echoing-tuck-fheman-from-3-months-ago-we-need-a-steem-changelog
make up your fucking mind, they arent happening or they are often happening much too quickly?
would it be that the changes to the rules that would benefit you, are not happening
and the ones that you dont understand are happening too quickly?
Or What?
I should change the first line to :
i.e.
ischanges toisn't.Exactly. You don't have clue which variable is responsible for the outcome you get. Change should be done one thing at time. I can understand fixing multiple bugs at once but I agree with your reasoning regarding adjustment of multiple variables. You just turn your experimental data into garbage by doing that.
Exactly!