Phrases
I was talking a while back about symmetrical code but it is not just individual code blocks that benefit from symmetry it is also the whole structure of the code. For example, if you've got lots of screens each then it's a good idea that the code follows the same structure across them all so if you were to compare them side by side they'd look symmetrical e.g. the validation code is in a method with the same name in each screen and initialisation / validation / etc. are done in the same order in each screen*.
Of course another way of looking at it is they all follow the same pattern, which is why "Patterns" is a big thing in coding nowadays. Going further out you could say that the screens always do X, any custom controls do Y and the business layer always does Z etc. leaving everything nice and ordered and neat and it was talking with a mate the other week when I first heard this expressed as the phrase "separation of concerns".
I heard the phase again on the MIX09 videos on ASP.NET MVC so I think this must be a new phrase of the moment** and I can see why 'cos it put succinctly*** the need to know what should go where when coding to make sure maintenance and debugging happen as easily as possible.
In other news lunchtime footie has been cancelled again today, gutted.
UPDATE (04-06-2009): I heard the phrase "separation of concerns" again today.
* and if they are not there is a comment to say why not.
** though I see the wikipedia page was initially created some time ago
*** I suppose I've previously asked which layer is responsible for what when being asked to extend existing code.
(Read comments)
|
