Skip to content

Instantly share code, notes, and snippets.

@ramirez7
Last active November 3, 2020 12:20
Show Gist options
  • Star 4 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ramirez7/e3df63c0b2f27951dd6791cedcac4279 to your computer and use it in GitHub Desktop.
Save ramirez7/e3df63c0b2f27951dd6791cedcac4279 to your computer and use it in GitHub Desktop.

haskell-effort-graph

  • Red area is a result of the upfront, fixed cost of learning Haskell vs Java.
    • The company pays this for each new hire.
  • Yellow area is the developer's productivity gain once they're "over the hump."
    • The company can benefit from this, but it must first reach a break-even point vs the cost of learning.
    • If average employee tenure is less than this break-even point, the company is taking an absolute loss on each employee.
    • For Haskell to truly be worth it from a business perspective, the average tenure must not just eclipse the break-even point, but it must go further to account for the opportunity cost of better productivity during that learning period.
    • However, employees always benefit from this regardless of turnover - they get to take the productivity gain with them. This - in my opinion - naturally results in some tension.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment