3 ms·
Much like most things in life, it takes practice and intelligence. The negative aspects are primarily because people haven't practiced enough or are being idio
by d0 13y ago
Much like most things in life, it takes practice and intelligence.
The negative aspects are primarily because people haven't practiced enough or are being idiots.
TDD is absolutely fine with OO. We have no problems with ~2 million lines of C#. It works pretty well to be honest. If you're finding something hard to test, it's usually broken in some way and usually because concerns aren't separated properly.
- raverbashing 13y ago"The negative aspects are primarily because people haven't practiced enough or are being idiots." Oh, I forgot, OO is perfect. Way to be condescending. "TDD is absolutely fine with OO" I don't mean OO in general (and it makes it easier in some aspects) I mean inheritance. The more your inheritance is deep the more the classes down the hierarchy (does that inherit the most) will have non trivial testing. Because of all the dependencies/initializations/creation of the parents. Oh I am sure I'm doing wrong and I have to use a VisitatorSingletonFactory I wouldn't have had a problem and "I'm being an idiot", of course. And surely, the problem is not usually within the codebase, but in external libraries/utilities, those that you need to interface in order for your system to do things.
- d0 13y agoSorry if I came across as condescending. Agree with respect to inheritance. I tend not to find any terrible libraries these days. I think people have developed some clue in the last decade.