2 ms·
Just for perspective, I think code reuse was the panacea of the last batch of "business BS". Tests driving development is more the latest batch. It's to the c
by joe_the_user 16y ago
Just for perspective,
I think code reuse was the panacea of the last batch of "business BS". Tests driving development is more the latest batch.
It's to the credit of software gurus like Robert Martin that Object Orientation is no longer really sold as a way to magically get software components to use on your other projects, that inclusion is preferred over inheritance etc.
Today, the idea that you can substitute writing tests for design is the "BS", the excessive paradigm touting, of today.
Which is to say that it's an unbalance presentation of new, useful tools. Tests are great but don't let you get by without high-level design unless your application is so simple it wouldn't need it.
But objects were and are great too. They just don't magically morph a class declaration into good code or reusable code. You still have to put effort into that part of things.
- nostrademons 16y agoYou can substitute tests for design - once you already know what the design is. It doesn't work quite so well when you have no clue what the overall picture is going to look like. Of course, this is like saying that you could've predicted the future with the benefit of 20/20 hindsight.