Economic Argument for Functional Programming
summary
Argues that adoption decisions hinge on concrete economics not ideology: shows math with birdhouse numbers (normal profit $65 vs golden $50, marginal cost $90 vs marginal revenue $75), an Alice valuation of $500 and Bob selling at $200, and a $100 neighbor externalities example. Recommends low‑risk moves first (bigger instances, measurable pilots, a Haskell microservice), warns against shouting “rewrite,” and frames choices as marginal cost vs marginal revenue, quantifying QA, hiring and risk to convince decision makers.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:57My background
- 14:49Everything has a price
- 19:11Externalities
- 20:54Tragedy of the commons
- 23:48Bananas
- 42:48Uptime
- 44:32Final recap
- 48:40Half the story
- 51:20How to fix it?
- 55:34Static type checking
- 57:07Acknowledge downsides
related talks
43mBringing Functional Programming to Work
57mMaximising Side Effects When Adopting Functional Programming
34mFunctional Programming: The Enterprise Edition
48mFunctional Programming: The Enterprise Edition
36mWhen to be Weird
03mTalks About His Talks
25mThinking Architecturally
45mDynamic vs Static Having a Discussion without Sounding Like a Lunatic