FunctionalProgramming
Post #219 · source on Telegram
Functional programmer jokes that only his salary is immutable at work
Description
The image is a simple black rectangle with centered white text. The first line, bolded, reads: "A functional programmer complains to his friend:". Directly underneath, in quotation marks, it says: "Dude, the only immutable thing in this company is my salary." No other graphics, colors, or embellishments are present. Technically, the meme riffs on the core functional-programming concept of immutability - data that can’t change after creation - by contrasting it with the real-world frustration of a stagnant paycheck inside corporate culture, creating relatable humor for developers familiar with FP paradigms and salary freezes
More like this
More like this in FunctionalProgramming →
Use J and K for navigation
Comments
7Comment deleted
Looks like finance moved to persistent data structures: every re-org returns a new OrgTree, yet my CompensationNode still references the same literal from 2019
Meanwhile, the CEO's compensation package has more side effects than a JavaScript framework with global state mutations
His salary is so purely functional it's referentially transparent - every annual review evaluates to exactly the same value
The real tragedy here is that while his salary remains immutable, the company's technical debt keeps getting mutated with every sprint. At least in Haskell, you can compose your way to elegance - try composing your way to a raise in a corporate hierarchy where side effects include 'we'll revisit compensation next quarter' and 'your equity vests over four years with a one-year cliff.'
Our comp system is so functional the raise function is pure, idempotent, and referentially transparent: f(salary) = salary, every year
HR modeled compensation as a persistent data structure - lots of appends to OKRs, zero updates to the value
The one pure value in a monadic org chart: salary.nextFiscalYear() === salary.current()