Uri Guttman wrote: >>>>>> "SB" == Steve Bertrand <st...@ibctech.ca> writes: > > SB> I have found some benefit to having wildly changing API's... I've learnt > SB> better ways to manage the callers to minimize impact, and better ways to > SB> design parameter handling. I'm sure once I find my own style that > SB> conforms (even loosely) to what other coders deem readable, I'll settle > SB> so that API's are designed to not require change. > > what you are doing (but slowly) is learning about api design and > architecture. it is very hard to teach or learn from a book. it is best > learned from experience and that can take a long time. this is not > knocking what you are doing, but letting you know that you are in it for > the long haul.
[..snip..] I got to the point where the one-offs where becoming larger and larger, and wanted something different. I completely understand that this is a long-term thing, and have made up my mind that it is something I want to pursue. So, for now, I'm going to 'play' with different methods (no pun intended) to implement methods. Besides... do you know how many BGP configurations that I had to break before I actually knew what I was doing? :) Learning about what I want to learn about before I learn and try it is important to me. For instance, I don't at this point have any use for memoization, but I found this gem to be absolutely comical and thought provoking while reading High Order Perl... "I sometimes enjoy the mind-bending exercise of imagining the result of memoizing the Unix fork() function.". ...heh... Steve
smime.p7s
Description: S/MIME Cryptographic Signature
