It’s funny because it’s true but half of them come from layering changes in changes with no proper regression analysis
Discussion
It's because they just want to do the rapid prototyping part, and skip stuff like customer review or unit tests.
Like shooting code out of a machine gun.
They're always telling me that the great part is that you get user feedback early, but they often ignore that feedback or don't bother to collect any.
They just build and deliver, in a bubble.
Not enough foreplay.
I also think it's sort of nuts that they need users to give them feedback that, for example, the login doesn't work or the site doesn't load.
At least, occasionally open your own app and just look at it and try it out. And do so on a different machine!
I don't know why I bother. Like talking to a wall.
Feel similarly. Throwing ideas out there w/o response. I think the best solution is to embody the solution you want to see. Let the product speak for what we're capable of, we're not going for flashy anyway.
W
O
R
K
S
O
N
M
Y
M
A
C
H
I
N
E
Currently 3 years into an 18 month project. Nothing works because reasons