Surviving the Framework Hype Cycle
summary
Uses the Gartner hype cycle to pick frameworks by stage not buzz, maps concrete roles — pioneers, settlers, town planners — to actions at each phase, and gives a practical rule: keep one tech to ship and one to explore. Shows Rails surviving to a plateau of productivity and cites a real-world setup: a legacy Rails 2 in production system alongside an Elixir/Phoenix side project. Advises against shaming others for their choices and warns that stopping learning risks commoditization.
AI-written summary · about
chapters (21)
- 0:00WELCOME TO THE NAP TRACK
- 2:04Let's talk about mid-life crises.
- 2:33The web developer's career is entering an endless mid-life crisis.
- 3:49A prediction for those trying to stay up on the latest web technologies
- 4:04It's impossible to keep up with new tools.
- 4:30Choice Paralysis
- 5:10New stuff can't live up to expectations.
- 5:53The technology you love is now obsolete.
- 8:51A Movement in 5 Medium Thinkpieces
- 10:16RUBY ON RAILS A HISTORY
- 16:49Pioneers Settlers Town Planners
- 20:271. Being required to use outdated tools 2. Team members that try to rewrite your codebase in the latest "hipster stack" 3. Anything that gets in the way of shipping
- 20:371. Accepting a PR for an OSS library 2. Applying a technology in a way that makes the company money 3. Solving a tricky performance issue
- 20:471. Showing someone that there's a new, better way of doing things 2. Improving someone's documentation 3. Automating a tedious deploy process
- 22:39How to win depends on your preferences
- 26:06But Brandon! If Ruby isn't dead, why do you run a JavaScript consultancy?
- 27:06THE CAUTION
- 28:22Avoid tech that targets the peak
- 31:21How did Rails & Ember "cross the chasm"?
- 32:48Focus on things that add value
- 33:21And since you focus on business value
