2 ms·
What is it terrible for? I've encountered situations where someone believed it was bad for something and were wrong. Such as user interface code. The solution i
by pmarreck 10y ago
What is it terrible for? I've encountered situations where someone believed it was bad for something and were wrong. Such as user interface code. The solution in that case for example is to make as much of the code testable as possible leaving just a thin layer of untestable stuff (which can still be tested via an integration test of some sort). This idea generally follows the principles of http://alistair.cockburn.us/Hexagonal+architecture http://alistair.cockburn.us/Hexagonal+architecture or "functional core, procedural IO". Gary Bernhardt expounds on this brilliantly in his https://www.destroyallsoftware.com/talks/boundaries https://www.destroyallsoftware.com/talks/boundaries talk, btw.