4 ms·
Clean architecture: https://smile.amazon.com/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164 https://smile.amazon.com/Clean-Architecture-Craftsma
by lucidguppy 9y ago
Clean architecture: https://smile.amazon.com/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164 https://smile.amazon.com/Clean-Architecture-Craftsmans-Softw...
Anything that touches the real world should be as small as possible.
I've been writing code using tests for about 4+ years and I now can't think of writing code any other way.
I would be scared of refactoring. Also I'm testing the code anyway - why not write it down so it gets done every time?
Run integration tests too for sanity - they're testing the integration of things.
To me: coding without tests is like going caving without a flash light. You don't really know what your code does until you run tests. Your confidence rises when more code is covered.
No it isn't perfect - but not writing tests is not better.
- wolco 9y agoThe problem with always relying on testing is you lose your ability to create without the test crutch. Everything is red/green and your brain can get a lazy. Balance is the best.
- lucidguppy 9y agoWhat is science without tests? I say coding is similar.