4 ms·
Writing tests for your own code is a relatively recent phenomenon. When I worked at MSFT as a developer in the early 2000s, we had dedicated test developers wh
by umeshunni 10y ago
Writing tests for your own code is a relatively recent phenomenon.
When I worked at MSFT as a developer in the early 2000s, we had dedicated test developers who wrote tests. You wrote your code and checked it in after a code review and as long as it passed the integration tests, the test developers wrote their (what would now be called) unit tests and checked them in to make sure someone else didn't break your code.
I think writing your own tests gained favor in the early/mid-2000s with the "extreme programming" and TDD movements (https://en.wikipedia.org/wiki/Test-driven_development https://en.wikipedia.org/wiki/Test-driven_development)
- mseebach 10y agoExactly. If union rules had been written down, even in 2005, developers would be forbidden from writing, possibly even running, tests, lest they take away the jobs of the testers. Unit testing would in practice be illegal, never mind (gasp) DevOps.
- bigtimeidiot 10y ago>If union rules had been written down, even in 2005 What are "union rules"? Each union is free to bargain their demands collectively with the employer. If your members think such a rule is stupid, they won't demand it. But your lack of knowledge and disdain of unions is noted.
- flamedoge 10y agoEven running itself. That would actually mean seeing what you wrote. That would be bad. Takes away potential job creation opportunities.