3 ms·
That's just doubling your work. If you don't already have a spec, your unit tests and actual code are essentially the same code, just written twice.
by HideousKojima 3y ago
That's just doubling your work. If you don't already have a spec, your unit tests and actual code are essentially the same code, just written twice.
- deleted 3y ago[deleted]
- __MatrixMan__ 3y agoDetermining which states are authentically hazardous and mocking data and adjacent services to make those states accessible at the press of a button is definitely not the same as writing code which handles those states appropriately.