Mahdi Yusuf

@myusuf3 @Lotterleben Tests don't eliminate your bugs. Good design does.

@schwarzmaler20 @myusuf3 Brainfart bugs happen, and tests let you know right away.

@lotterleben @myusuf3 you detect bugs earlier, to assume you need less time to fix is … optimistic

@schwarzmaler20 @myusuf3 Not if you assume searching for the cause is part of the fixing?

@Lotterleben @myusuf3 How does writing good tests prevent you from searching the cause - beyond the trivial bugs?

@schwarzmaler20 @Lotterleben @myusuf3 Good design has never eliminated a bug ever. It may prevent certain classes of bugs, that's all.

@fresskoma @Lotterleben @myusuf3 Good design prevents you from a whole classes of bugs. External usage, internal interfaces, no cobbling.

@schwarzmaler20 @fresskoma @myusuf3 Why are you turning this into a question of either- or?

@myusuf3 @djm61 I would suggest that writing the tests first is even better, if somewhat idealistic...

@qole @myusuf3 if you're disciplined enough to write tests, it'll soon become habit. Regardless if you write tests first or as you go

@myusuf3 You forget the amount of time you need to fix the bugs in the test code… ;-) @musevg

@balu @myusuf3 @musevg you could write tests yo verify the tests..

@myusuf3 @seebrock3r what does that look like if the tests come first? :p