>To be honest though I feel out of step where software development has been heading. All this talk about agile development (most hypocrisy in real life) and extensive discussion of 'proper style' is leaving me with a really bad taste in my mouth. More and more technology is downplayed and taking second fiddle to abstract patterns that are IMHO not making life easier for developers - quite the contrary. Especially the insane focus on testing with its mocking and faking and IOC results in code that is maybe testable but extremely difficult to implement and much worse for anyone to follow. The amount of waste of time that goes on with all of this is monumental. The same goes for various patterns that gain favor for a while before they fall out of favor for something new or 'better' a year or two later only to be obscure hints of a past that nobody understands 3 years down the road. > >The concepts are good for many of these things but ultimately the implementation to date has been sucky. I still believe that classic patterns - basic abstraction of 'business' logic, some 'basic' abstraction in the UI layer buys you 95% of what all these other solutions buy you at a much less painful learning, design and implementation curve.Add in some basic unit testing against real-world scenarios and you get nearly to 100%. For the tiny remainder hacked solutions are Ok... > >In the end I feel what matters are solutions that are easy to build and easy to follow without a huge level of abstraction so that they are dog slow. Maintainable code that doesn't take a CS degree to understand just the concepts of. Solutions that can be maintained by someone that isn't clued in to the latest fad technology/pattern and can understand it. Efficiency doesn't have to be complex - and that seems to be a point missed by many of the solutions today. > >+++ Rick ---
