ooad suggestion
in [OOP]
|
From: RedLars on 22 Apr 2008 01:52 Thanks for your input. On 22 Apr, 04:59, "Phlip" <phlip2...(a)gmail.com> wrote: > RedLars wrote: > > Do you mean Refactoring: Improving the Design of Existing Code by > > Martin Fowler? > > Unfortunately yes. Why unfortunately? > > >> And how have you been designing for these few years? > > > Just looking for ways of improving my design skills. Buying a good is > > one approach. > > Write unit tests for everything you do. Their effect on design cannot be > understated. Thats another approach, which I had not thought about. > > -- > Phlip
From: Phlip on 22 Apr 2008 05:52 RedLars wrote: >> > Do you mean Refactoring: Improving the Design of Existing Code by >> > Martin Fowler? >> >> Unfortunately yes. > > Why unfortunately? Inside joke. Refactoring is about cleaning up a design if (by some chance!) its first incarnation was not perfect. This is why some people give up on early design altogether, and they just write their code explicitly to be refactored! >> Write unit tests for everything you do. Their effect on design cannot be >> understated. > > Thats another approach, which I had not thought about. Tests force everything to be decoupled, because each test case must be simple and illustrative. -- Phlip
From: kevin cline on 22 Apr 2008 16:09 On Apr 22, 4:52 am, "Phlip" <phlip2...(a)gmail.com> wrote: > RedLars wrote: > >> > Do you mean Refactoring: Improving the Design of Existing Code by > >> > Martin Fowler? > > >> Unfortunately yes. > > > Why unfortunately? > > Inside joke. Refactoring is about cleaning up a design if (by some chance!) > its first incarnation was not perfect. > > This is why some people give up on early design altogether, and they just > write their code explicitly to be refactored! > > >> Write unit tests for everything you do. Their effect on design cannot be > >> understated. > > > Thats another approach, which I had not thought about. > > Tests force everything to be decoupled, because each test case must be > simple and illustrative. I completely agree with Phlip. I just started a new position, and my first task involves developing tests for legacy code so that it can be refactored for reuse.
From: Phlip on 23 Apr 2008 23:48
kevin cline wrote: >> This is why some people give up on early design altogether, and they >> just write their code explicitly to be refactored! >> Tests force everything to be decoupled, because each test case must be >> simple and illustrative. > > I completely agree Tx! And note that a few years ago, this forum would have screamed for a week or two at anyone suggesting testing could replace up-front design. These days... >>crickets<< (-; |