Thefuturebymob

This makes it sounds like you are using users to test, rather than code inspections and actual testing. Feedback from users should be change requests, additional functionality etc. There are so many bad things if a company is relying on its users, customer shouldn't have anything to do with bugs. If your customers experience bugs 1. Why should they spend effort and time reporting them, its up to the supplier to find and fix. 2. They have to keep upgrading to the latest version to get fixes (ok when publishing web services, not ok for firmware) 3. There will be zero trust on each new release, which means you'll have to support many releases as customers will not upgrade and will want single fixes for their current release etc.

--

--

I must admit, I never did this, and I always managed to get promoted every year or so. This was due to the fact many companies wanted to retain me. This just shows there are no real promotions in SE. Progression is just used as a cheap way to try and retain staff that are in short supply. Its a trick, no company gives 2 hoots about an individual SEs career, its just marketing. Also managers need to give engineers a promotion/level up as there are pay ceilings for each level. If they want to keep someone they need, they level them up so they can give them a pay rise once the SE has hit that levels ceiling.

--

--