"Thinked myself into immobility"
I agree.

"I observe the existence of familiar patterns of software-design but do not begin my work by "selecting a design pattern." "
I agree too, this is how things should be done. But it's also very teachful to me, to understand other peolpe's experiences and concepts.

Let me illustrate this with music: the important is to play something that you like, and you don't need to learn any theory to do that. But learning about music theory will transform the way that you listen to music, the way that you play it, and give you an accurate vocabulary to conceptualize it and speak about it. It will also enable you to play with other people more easily, and to share your experience with them with more accurate words. They are not the only "valid" words, nor is tonal music theory the only valid musical theory. But they are used enough so that people who use them can communicate accurately. And listen more accurately, in a way. Identifying and naming patterns trains the hear. And the fingers.

I guess, there is not "one way" to do things properly. But it's teachful to try and follow a method rigorously and with dedication. To then develop you own ways around it, change it, etc.

I used to never want to look at a programming book "i can figure it all out by myself". Now, maybe i'm a bit too much into books. But it's interesting !

Hopefully, through programming more and reading less, i will stop "thinking myself into immobility". But this thinking process feels very rewarding. Even if i get stuck into immobility here and there (^c^).

My problem here was not about TDD but about design, so i ordered a book about design. It will not help me "pick the right design among the valid ones", but rather "make me travel" through possible designs, think about them. It feels like good training. But it involves lots of reading and "being stuck in concepts", at first.

I guess my message feels defensive. It guess it is, in a way. But I agree with what you are saying.

PS : different people, different ways of learning

In reply to Re^2: Test Driven Development example + design question by mascip
in thread Test Driven Development example + design question by mascip

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.