4 ms·
Not a programmer, but as a QA "analyst", the productivity involved was probably less than 15% of my time spent on "projects". To the point where I quit (several
by fishtacos 3y ago
Not a programmer, but as a QA "analyst", the productivity involved was probably less than 15% of my time spent on "projects". To the point where I quit (several years ago) because it seemed pointless. Another colleague quit within 2 months for the same reason. I felt I was riding the clock simply to make a paycheck. It paid well, yet I'd rather work in retail or something else and feel useful than simply be a body following "the process" as was asserted by my immediate manager. Screw "the process". It felt like a waste of time.
I don't think I'm an outlier in my thought process regarding my peers, but there was little upward mobility and couldn't stand the multiple meetings where I was supposed to provide value by making up CMMI metrics to please the other managers in addition to my 3 current ones in a team of 2 devs and myself. That's 4 managers in a team of 3 people. Too many chiefs... as the saying goes.
It's not all bullshit, but most of it is.
I have no problem saying it was at Dell Services, later acquired by NTTData while I still worked there. The rest is irrelevant.