You are viewing a single comment's thread from:
RE: HF20 Update: Restoring Continuity
@ned I'm shaking my head
Lemme get this straight, you need rigorous gatekeeping witnesses to stop the shitty code changes, yet there are sweet fanny Adams that understand the code in its entirety
Inherently you are outsourcing code QA to people that are paid for their services by the output of that code.
And that looks like a serious conflict of interest.
Oh and vote for my witness if you want change 😂
I take blame here. Let’s now look forward again — the reality is the system is going to be stronger with published Witness’ Gatekeeping Standards. These become Steem’s development companies’ standards that must be met too.It’s something we’ll all arrive at together. I’m actually looking forward to the process. Once we get some of our sleep back
Thanks for the reply, you will be seeing more, Much More, from this fair lady, @Sapphic! 35 years IT and related fields experience, and since we've been together I have become more impressed by her skills every day. We are building something great together, and that vote request was not a joke, she can really back that up!
PS: Get some rest, we will all need it as these markets open back up. We need great leadership, @ned, so be ready for the task! I say that we are HERE:
This is a good conversation starter for Witness’ Gatekeeping Standards: https://steemit.com/witness-update/@reggaemuffin/witness-statement-for-reggaemuffin-proposing-hardfork-adoption-requirements
What about STINC/Steemit Inc. @ned? Are you planning to formalize steem's development process ever?
We have greatly improved organizational development practices since the several prior forks, including real adherence to Agile development, but we haven’t improved enough. The post mortem of HF20 will make us sick and cry. Our Standards will increase. I want the witness’ Gatekeeping Standards even higher. There is a silver lining in struggles or failure — it can be the beginning of new strengths.
Its not easy to focus on the business challenges and the software development at the same time especially in such a community where there are lots of people whose lively hood is from STEEM. So personally I would say, understanding is a good starting point and this can be the beginning of a new era. By adapting a model similar to Wikipedia and true to FOSS principles, IMHO this project can set standards in the blockchain software development.
Agile, yes -- but need "Test Driven Agile Development". This is the ONLY shortfall and everything else will fall in place auto-magically.
Few points:
Your biggest strength is an incredible community & wishing STEEM all the best!
@bobison, If you want to set standards, then start by following the lead of existing mature FOSS projects. For example Drupal (the biggest dev-focused FOSS project worldwide). It is 17 years old, Drupal adopted TDD 10 years ago and had its own moments of radical changes, but Drupal has tradition of communicating change pretty well! (starting from its founder & project lead)! In short, there is no need to reinvent the wheel @ned, if you really want to keep steem for the long run, make it formal, and if you know that you can't hold the technical weight of the project, then hire a competent CTO ;)
Agree @develcuy
Drupal is not alone. gcc, Bash, emacs etc are even older than drupal and are still holding up. I would prefer to go Python's route though (as opposed to even Linux's). Why I said Python instead of Drupal is because of the recent CVEs against Drupal which was lurking there for so many years. But in general, we are saying the same thing :-)
If you are stating that a programming language makes a final product more secure, then I think that we aren't on the same page, nor on the same book either. Review your statements and try again
Valuable input. Thank you.
@ned : followup work & status https://hackmd.io/s/ByT1BuG5m
That is good will from you @ned! However, having a formal process requires more than just good will. I've been involved on a CMMI level 3 certification about 6 years ago, it was way too boring back then, but it brought the ability to scale. Not an easy process btw, we had to make hard decisions and to deal with key people leaving the company, but things stabilized over time. So, you had the guts to let HF20 go, how about letting your company to formalize with working industry standards?