3 ms·
DDD, Netbeans debugger and Eclipse's debugger are on equal standing. I've used all heavily. However, I tend to rarely use the debugger on my own code in any la
by gouranga 14y ago
DDD, Netbeans debugger and Eclipse's debugger are on equal standing. I've used all heavily.
However, I tend to rarely use the debugger on my own code in any language since I started doing incremental TDD and using assertions galore all over the place to check inputs, outputs and assumptions. Prevention is better than cure (or debugging).
- josephcooney 14y agoDo you do any kind of concurrency in your code? How is unit testing working out for you there?
- gouranga 14y agoLots. Incredible amounts actually. We don't have any problems at all. In fact it's really easy. We use nservicebus and share by communicating rather than communicate by sharing. We use concurrentqueue class in the framework and all is solved.
- lucidquiet 14y agoYou can't assert everything, you can't test everything (like the tests themselves). You can't assert a list of hard coded values are all correctly spelled via an assert. You can't determine if a library that has it's own asserts is failing or your code is failing. You can't always add asserts to legacy code, etc.
- gouranga 14y agoAnd? I fail to see your point. Assertions check assumptions and tests test code. And yea you can use a dictfile from Unix to test spelling quite easily (we do it for document construction) Nothing is ever 100% certain. Are you suggesting that I magically write perfect software? I don't, but it works first time in 99% of cases with the right tests and assertions. The 1% left goes to debugging. Our bug rate is approx 1 per 2000 lines of code that hit production.
- marshray 14y agoHats off to you if you can use DDD heavily. I've given up on that shortly after every time I've tried to use it. It seems very prone to crashes and lockups. MSVC will too sometimes, but it's really pretty rare.