2 ms·
> Linus Torvalds I am not Linus. Maybe you are. The reason I am such a fan of this approach is that I wrote software without it for a long time (Objective-C
by mpweiher 8y ago
> Linus Torvalds
I am not Linus. Maybe you are.
The reason I am such a fan of this approach is that I wrote software without it for a long time (Objective-C pre-processor/runtime, Postscript interpreter + various RIPs + other pre-press stuff, content mgt. system when that was still a thing...), and the difference is...hmm..let's say "significant".
Without this sort of approach, you get that rush of making super progress quickly, of holding the entire state in your head and being just the coolest cat on earth. It just doesn't last. Things start deteriorating, you fix a bug only to have another one pop up, after a while of this you get a sense of deja-vu and notice you've been going around in circles. Pretty soon you are stuck.
When I was put in charge of the CMS, management wanted to know when we would ship the next version. I couldn't honestly tell.
With a TDD approach, you get less of that rush, less of the "I am the greatest". What you do get is steady progress without backtracking.
> drink the Uncle Bob Koolaid
You shouldn't drink anyone's Koolaid, not mine and certainly not Uncle Bob's.
For your reference, I was doing this long before Uncle Bob. At least I remember sparring with him on comp.object, when he was still claiming that "OO is just function tables" and not a peep about TDD from him.