1. The managers way of finding out what is going on instead of seeing git, running latest code.
2. A way of giving developers bi-polar disorder as they either happen to have just checked in a working piece of code (up) or are still ploughing through on what they said they would do yesterday (down).
It can be good - but only when it requires execution not thought.
My solutions:
1. A selenium / CLI recorder. We make changes to a piece of code - which is covered by ten tests. You fill in the bug report and the recorder does video grab of the selenium web broswer doing the ten tests. Then anyone who is non technical can see what the actually results are - on Youtube!
I heard of some "developer lead development" in a job ad - I think it was Sky. The idea was github like I suppose - devs think "what we really need is" and go do it.
The boss effectively has a veto not a driver. The boss becomes a government.
1. The managers way of finding out what is going on instead of seeing git, running latest code.
2. A way of giving developers bi-polar disorder as they either happen to have just checked in a working piece of code (up) or are still ploughing through on what they said they would do yesterday (down).
It can be good - but only when it requires execution not thought.
My solutions:
1. A selenium / CLI recorder. We make changes to a piece of code - which is covered by ten tests. You fill in the bug report and the recorder does video grab of the selenium web broswer doing the ten tests. Then anyone who is non technical can see what the actually results are - on Youtube!
I heard of some "developer lead development" in a job ad - I think it was Sky. The idea was github like I suppose - devs think "what we really need is" and go do it.
The boss effectively has a veto not a driver. The boss becomes a government.