ircmaxell: Framework Fixation - An Anti Pattern

ircmaxell: Framework Fixation - An Anti Pattern, short summary:
  • delegation of architecture decisions to frameworks may not be optimal or even wrong
  • only use frameworks when doing prototypes or projects you don't need to maintain
  • frameworks don't save time/money in the long term
  • frameworks don't make it easier to hire good programmers
  • using a framework prevents developers from understanding backgrounds
  • not all framework developers are super heroes (look at the bug trackers ...)
  • favor libraries over frameworks
Quotes:
  • Most of the monolithic frameworks are red herrings...solving problems of yesterday
  • The typical mantra of "just let a framework do it for you" helps nothing except creating brainless code monkeys. (source)
My opinion:
  • frameworks are not so bad, but you need to evaluate them very carefully before using
  • evaluation means checking code quality, features AND performance matching the specific problems of your business
  • choosing the wrong framework throws your business back for years
  • make sure that you can maintain the framework yourself without the maintainers
  • make sure how to upgrade to new versions of the framework
  • only use a framework if your code size gets smaller
  • writing your own framework to solve only your problems can be quite good
  • frameworks can be used very well to find solutions for problems in your own code

Comments

Popular posts from this blog

How to construct a B+ tree with example

How to show only month and year fields in android Date-picker?

Visitor Counter Script Using PHP