3 ms·

Or they paid for it because the alternatives weren't any better. Visual Studio Debugger is very nice, I don't know of anything that's as good, and as mature.

Or they paid for it because the alternatives weren't any better. Visual Studio Debugger is very nice, I don't know of anything that's as good, and as mature. Attach To Process with a nice UI is a great tool compared to the command line debugger. VS 2008 and 2010 are worlds better than 2005 -- so if we count the last 10 years nearly half of that will be people using 2005, and yes that was awful. Two version later, is it worth asking for a good price for a full featured version? Probably.

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 ago
  Do you do any kind of concurrency in your code? How is unit testing working out for you there?
  - gouranga 14y ago
    Lots. 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 ago
  You 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 ago
    And? 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 ago
  Hats 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.

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 ago
Do you do any kind of concurrency in your code? How is unit testing working out for you there?
- gouranga 14y ago
  Lots. 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 ago
You 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 ago
  And? 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 ago
Hats 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.