3 ms·
> The other problem is, Microsoft got rid of Software Development Engineers in Test, and they replaced them with devs doing test. But at Microsoft, SDETs served
by ChrisMarshallNY 4y ago
> The other problem is, Microsoft got rid of Software Development Engineers in Test, and they replaced them with devs doing test. But at Microsoft, SDETs served as the last line of defense for the users, as an SDET it was made clear to me from day 1 of my employment that I had the power to stop shipment of software if I felt the code wasn't up to snuff. As a junior SDET I only ever used that power once, I was damn well scared, and when I spoke up and said we had open bugs that I personally considered ship blockers, the lead dev said no problem, the release would be delayed until his team fixed the bugs.
I worked for almost 27 years, for a Japanese optical corporation that is synonymous with "Quality."
Their QC department was the most powerful one in the corporation, and all the devs lived in fear of failing QCT, as that would have C-Suite-level notice.
In the US, there used to be a joke, saying "If you have 'Quality' in your job title, your career is over." At this company, it meant you were just short of a God.
That said, it tended to make life stressful for us. As an American development team, we were often treated as "Bad Software Cowboys." Most folks here, would consider us to be completely uptight, anal-retentive, risk-averse, babies, but they thought of us as reckless.
- antifa 4y ago> In the US, there used to be a joke, saying "If you have 'Quality' in your job title, your career is over." At this company, it meant you were just short of a God. I would welcome this as a cultural change in the US. It just sucks living downstream of people dumping tons of cowboy code into the river.