Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Re: Which comes first: design skill or TDD?
Hi Mauricio, You make an interesting point, saying that the JUnit 5 extensibility model "was clearly created by someone who profoundly understands object-oriented design principles and how to build elegant and flexible APIs. A non-expert in OOD, even with TDD, wouldn't be able to do it no matter how perfect their TDD sessions were." So, are you suggesting that TDD __ought__ to do that? Or possibly that some TDD practitioners / apostles have said it will do that? I'd be interested to know why that point comes up for you. For myself, I have believed since my first experiences with TDD (ca. 2001) that I never believed TDD could allow me to do things I don't already know how to do. Possibly more important, the folks I learned from (Jeffries, Beck, Cunningham) never downplayed the need for deep understanding in developing truly elegant and flexible software. The point (at least as I learned it) is that TDD comes very close(*) to guaranteeing __working__ software. Of course, back in the day, I worked in a context where other folks were already developing elegant designs... but the software didn't necessarily work. :-) I wonder if that still happens? Charlie * I think we all know that TDD, taken in isolation, doesn't guarantee that the software works the way the client wants it to work. Other practices are needed for that. On Tue, Jul 4, 2023 at 11:36?AM Mauricio Aniche <mauricioaniche@...> wrote: Hi, JB! Thanks for starting such an interesting thread. |
to navigate to use esc to dismiss