> (ii) testing, deployment and all that is minimal.
Since when did testing and deploying become "unproductive work"? If getting reliable, tested code in front of customers is not your job, what is?
Since when did testing and deploying become "unproductive work"? If getting reliable, tested code in front of customers is not your job, what is?
Old school people might call it getting stuck in a rut. It's much easier for me to get stuck in a rut doing testing and documentation, compared to doing something new and exciting.
I'm curious as to whether developing automated testing and deployment stuff would count as doing testing and deploying, or as developing exciting new stuff.
And for me, developing the automated stuff is still not particularly interesting. I guess if I were designing cars, my interests (and thus most productive department) would lie with building the car itself (engine, body, drivetrain, etc.) rather than the safety system or QA. Maybe it's just my personality.