Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Framework Fanboys
Causes, effects, and what to do about it
by Neil Green (@neilfeyn)
Future Framework Fangirls
We can make
bad framework
choices too!
What is a
Framework Fan-person?
Those who would adopt
Frameworks, or continue to show
loyalty to Frameworks, without
Valid Justification.
Valid Justifications for Adopting
or being Loyal to a Framework
• Performance
• Security
• Stability
• Scalability
• Maint...
What are Invalid Justifications?
We better get on
this Angular
bandwagon before
we get left behind!
Fan Adoption
Real developers
just need jQuery.
Everything else is a fad.
Fan Loyalty
Causes of
Fan Adoption
Admiration
Google makes the very
best frameworks!
Angular 3.0 will be
written in Fortran!
Bidirectional
data binding we
love you!!!
Curiosity
Industry Trends
Boredom
Nonconformism
Peer Pressure
He still uses Postgres.
Everyone’s moved on to
Mongo Idiot!
It’s stupid to have an ORM
layer – just store JSON
objects as-is!
Mongo uses a global lock?
And you say Postgres has
JSON data types?
Solution Fixation
Job Mobility
If only I had learned
Spring and Hibernate…
Causes of
Fan Loyalty
Fear of the Unknown
But what if it leaks
memory???
Am I going to have
to change my build
process???
I don’t even
understand our
current build
process!!!
Fear is the
path to XML XML leads to
SOAP
SOAP leads to
Suffering
Comfort with the Familiar
Hell yeah!
Hell Yeah!
Hell Yeah!
Lack of Managerial Support
Say
refactoring
again.
Just so I
understand…
We’re not going to
release features while
you fix something
that’s not broken?
Lack of Perceived Benefit
Job Preservation
Not Wanting to Admit Fault
I was against
ExtJS from the
start!
I wanted to
use Flex!
How as I supposed
to know Angular 2.0
would be a breaking
upgrade???
You are utterly
incapable of picking
any framework under
any circumstances
ever!!!
Fear of Learning
What to do about
Fan Adoption
Admiration
(It’s not their frameworks we admire)
Curiosity
(Do that on your own time)
Industry Trends
(Don’t listen to the hype)
Boredom
(Find a better job)
Nonconformism
(Find better ways to be yourself)
Peer Pressure
(Form your own opinion)
Solution Fixation
(Define your problem first)
Job Mobility
(Don’t be unethical)
What to do about
Fan Loyalty
Fear of the Unknown
(We never know until we try)
Comfort with the Familiar
(Get outside of your comfort zone)
Lack of Managerial Support
(They don’t know what you know)
Lack of Perceived Benefit
(Get better at selling)
Job Preservation
(Be more afraid of obsolescence)
Not Wanting to Admit Fault
(We all make mistakes)
Fear of Learning
(Learning is a skill, not an ability)
Closing Thoughts
The End
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Framework Fanboys: Causes, effects, and what to do about it
Upcoming SlideShare
Loading in …5
×

Framework Fanboys: Causes, effects, and what to do about it

5,902 views

Published on

Developers will often adopt a framework long before it is prudent, or will cling to a framework long after it has become irrelevant. This phenomenon of picking and sticking with a framework for all the wrong reasons affects everything we do, from the estimates we give, to the people we hire, and the companies we want to work for. Attempts to mitigate the risk of poor framework choices are often thwarted by the ability of a single developer to introduce a questionable framework that then gets adopted by their peers. The effect is magnified by the fact that many developers would rebel and quit if they could not use their framework of choice.

This talk will explore this phenomenon in an attempt to find it’s root causes. This meandering journey will take us down the dark paths of the recruiting industry’s keyword obsession, academia’s attempts to prepare graduates for the real world, as well as the natural human instinct to play with new and interesting things - regardless of the cost. Once we understand the nature of the problem, an attempt will be made to identify potential solutions.

Published in: Software

Framework Fanboys: Causes, effects, and what to do about it

  1. 1. Framework Fanboys Causes, effects, and what to do about it by Neil Green (@neilfeyn)
  2. 2. Future Framework Fangirls We can make bad framework choices too!
  3. 3. What is a Framework Fan-person?
  4. 4. Those who would adopt Frameworks, or continue to show loyalty to Frameworks, without Valid Justification.
  5. 5. Valid Justifications for Adopting or being Loyal to a Framework • Performance • Security • Stability • Scalability • Maintenance • Needed Features • Faster Time to Market • In-House Expertise • Developer Community • Ease of Recruiting • Business Alignment • Boilerplate Removal • Enterprise Support
  6. 6. What are Invalid Justifications?
  7. 7. We better get on this Angular bandwagon before we get left behind! Fan Adoption
  8. 8. Real developers just need jQuery. Everything else is a fad. Fan Loyalty
  9. 9. Causes of Fan Adoption
  10. 10. Admiration
  11. 11. Google makes the very best frameworks!
  12. 12. Angular 3.0 will be written in Fortran!
  13. 13. Bidirectional data binding we love you!!!
  14. 14. Curiosity
  15. 15. Industry Trends
  16. 16. Boredom
  17. 17. Nonconformism
  18. 18. Peer Pressure
  19. 19. He still uses Postgres. Everyone’s moved on to Mongo Idiot!
  20. 20. It’s stupid to have an ORM layer – just store JSON objects as-is!
  21. 21. Mongo uses a global lock? And you say Postgres has JSON data types?
  22. 22. Solution Fixation
  23. 23. Job Mobility
  24. 24. If only I had learned Spring and Hibernate…
  25. 25. Causes of Fan Loyalty
  26. 26. Fear of the Unknown
  27. 27. But what if it leaks memory???
  28. 28. Am I going to have to change my build process??? I don’t even understand our current build process!!!
  29. 29. Fear is the path to XML XML leads to SOAP SOAP leads to Suffering
  30. 30. Comfort with the Familiar
  31. 31. Hell yeah!
  32. 32. Hell Yeah!
  33. 33. Hell Yeah!
  34. 34. Lack of Managerial Support
  35. 35. Say refactoring again.
  36. 36. Just so I understand… We’re not going to release features while you fix something that’s not broken?
  37. 37. Lack of Perceived Benefit
  38. 38. Job Preservation
  39. 39. Not Wanting to Admit Fault
  40. 40. I was against ExtJS from the start! I wanted to use Flex!
  41. 41. How as I supposed to know Angular 2.0 would be a breaking upgrade???
  42. 42. You are utterly incapable of picking any framework under any circumstances ever!!!
  43. 43. Fear of Learning
  44. 44. What to do about Fan Adoption
  45. 45. Admiration (It’s not their frameworks we admire)
  46. 46. Curiosity (Do that on your own time)
  47. 47. Industry Trends (Don’t listen to the hype)
  48. 48. Boredom (Find a better job)
  49. 49. Nonconformism (Find better ways to be yourself)
  50. 50. Peer Pressure (Form your own opinion)
  51. 51. Solution Fixation (Define your problem first)
  52. 52. Job Mobility (Don’t be unethical)
  53. 53. What to do about Fan Loyalty
  54. 54. Fear of the Unknown (We never know until we try)
  55. 55. Comfort with the Familiar (Get outside of your comfort zone)
  56. 56. Lack of Managerial Support (They don’t know what you know)
  57. 57. Lack of Perceived Benefit (Get better at selling)
  58. 58. Job Preservation (Be more afraid of obsolescence)
  59. 59. Not Wanting to Admit Fault (We all make mistakes)
  60. 60. Fear of Learning (Learning is a skill, not an ability)
  61. 61. Closing Thoughts
  62. 62. The End

×