Getting the Frog Out of the Well
summary
Argument: teams perform best when developers measure success by fun because enjoyment tracks efficiency and signals what to keep or change. Claims a personal library and a componentized, small-pure-function design philosophy exist but cannot be forced across teams. Notes concrete tools: Elm provides the most fun due to static typing and a strict compiler, Elixir/Phoenix and Rails are valid choices if the team enjoys them, and change starts at the team level.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:28Original talk idea
- 5:14What makes coding fun
- 8:27Efficiency and fun
- 10:34Frog, bird, and turtle
- 12:47Team fun over everything
- 13:31Subversive change
- 14:57Most fun coding experience
- 16:01Finding middle ground
- 17:04Q&A
related talks
29mRethinking All Practices "Building Applications in Elm"
56mSimplifying Web App Development With Elm and Functional Programming
39mGoing Evergreen
38mConfident Frontend with Elm
27mDesigning Even Larger (JavaScript) Applications
39mDeveloper Happiness on the Front End with Elm
25mDefault to Consistent
31mMake the Back-End Team Jealous: Elm in Production