are programmers "failures"?

[pier4r]

(03-28-2019 07:03 PM)Maximilian Hohmann Wrote:  for every hour of writing code one was required to spend nine hours doing paperwork, documentation, test cases, testing, acceptance testing, kick.-off meetings, other meetings, ... you name it.

If there would be documentation, test cases, testing and so, it would be gold! In most cases, far away from constructing aircrafts (that are still something very fragile), there is nothing of the sort.

Agile in theory should be a collection fo cycles with a reflection in each cycle. What we did good? What was wrong? What should be improved?

There is none of it in most companies.
Testing? no.
Reviews? no.
Adjusting the plan? no.
Documentation? Haha, good joke.

etc...

If there would be what you mentioned, it would be much better. Tedious maybe, but better.