How to to analyze your app design?

Question

During the implementation, or even after it I sometimes find a better design solution. I think it`s quite common thing for all developers as software once written can always be done better.

But how to analyze your mistakes to prevent similiar mistakes in future? I know 2 things for that: Code reviews and post mortal meetings.

Can you name more and describe how you do them. Also I`m interested in the way you checking that your method works and really reduces the number of design errors, making you a better designer.

Answer 1

One thing my experience has shown me is that writing unit test for your code will show you whether your architecture is decent or not. If you have to put some amount of work into a single test, your architecture may not be ideal :)

You may in the process find you have too much coupling and-or too little cohesion. In my case, in one project, both.

Answer 2

There is alway better design. I never afraid of Second System Effect. It's necessary. I always used Tracer Bullets.

Most of my design ideas came from the book The Pragmatic Programmer: From Journeyman to Master. These Tips from early chapters of that book could help for better design...

• Good Enough Software
• Dry
• Orthogonality