You are viewing a single comment's thread from:

RE: To Ned, re:roles

in #steem6 years ago

"code review", if they (steemit), are expecting a line by line review of proposed code, that is the job of a Quality Assurance Team, (my view only). To me code review is code that has passed QA, and then been handed over to be reviewed. Does it work as expected? A person is given a list of what the code should do, and asked to review the working of the code.

  1. Check sign-in function
    a. Did sign-in function work as expected?
    Yes No (circle answer); if no please describe error received

So a big discussion it seems really needs to be done so that everyone is operating under the same expectations. I am pretty much only a consumer on steemit, and a social entity, not much of a High Quality Blog of information and Ideas, more of a social blogger. (I do believe there is a lot of room for people like myself). The testnet was, or at least how I understood it, (after reading all about HF17), was the test area for the witnesses to Test (review), the programing.

Steemit needs to provide functioning tools if they have expectations of something being tested. It is easy for a programmer to say yes it works as it should, but does it work for non-programmers.