The answer, nothing. The problems are still the same.

Whats happened in my opinion is everybody including tools developers are wanting to come up with the majic framework that does everything and base a whole load of junk theory around it. What you end up with is you have this huge framework, complex classes and hierarchies, all to do the same thing, which lets face it is working with a back end database in most cases.

Dont get me wrong, design patterns are good, and i’m a keen advocate of good OO techniques, but we’ve all forgotten the art of writing simple, clean, optimised, and fast code in my book, and rely too much on out the box frameworks.

X X X

“Use them because is easier to use them than to implement their functionality by ourselves. If you need a unit testing, don’t write your own, use any of the xUnit or TestNG, for example.”

I think a lot of frameworks/libraries can be added to a project in the name of it being harder to implement something by hand, and those frameworks could add a lot of complexity that isn’t needed.

I think using a framework because it is easier than coding the functionality yourself can conflict directly with other points you made:

“The more things that can fail, the more things that will fail.”

“The more prepared is your code for change, the more difficult is to change your code.”

Do you have any further advice in this area? How to resolve these conflicts?