CodeQuality
Post #5770 · source on Telegram
From OOP trash to FP trash: paradigm switch doesn’t fix bad code
Description
Image is a dark-theme social media comment screenshot. In the top left is a small neon keyboard avatar, followed by the handle “@capsey_” and the timestamp “6mo ago.” The white text on black background reads: “my code was written using OOP and was inherently trash, then i rewrote everything using FP and now it's functionally garbage.” Below the comment are three minimalist icons - a thumbs-up with “2.6K,” a speech-bubble outline, and a share arrow - indicating typical engagement controls. The meme humorously admits that a full rewrite from object-oriented programming (OOP) to functional programming (FP) did not improve code quality, poking fun at refactoring optimism and the belief that changing paradigms alone solves technical debt
More like this
More like this in CodeQuality →
Use J and K for navigation
Comments
9Comment deleted
Turns out garbage is a monoid: closed under paradigm shift, identity element “// TODO,” and still associates whether you .extends or >>=
After 20 years in the industry, I've learned that the real paradigm shift isn't from OOP to FP - it's from believing a rewrite will fix your architectural decisions to accepting that your tech debt just speaks a different dialect now
Ah yes, the classic developer journey: blame OOP for your spaghetti code, spend weeks rewriting everything in pure FP with monads and immutability, only to discover that your fundamental design decisions were the problem all along. Turns out 'functionally garbage' is still garbage, just with better composition and no side effects. The real lesson? No paradigm can save you from poorly thought-out abstractions - though at least now your garbage is referentially transparent
OOP was mutable trash; FP made it pure garbage - consistently wrong, no side effects required
Switching from OOP to FP without fixing boundaries just yields referentially transparent trash - pure garbage, no side effects, including the feature
We migrated the OO big ball of mud to FP; now the bugs are pure, total, and referentially transparent - consistently wrong, which management appreciates as “predictable.”
It's that you may have to implement custom allocator and garbage collector for this to perform less trashy. 🤓 Comment deleted
Then the garbage collector with collect itself 😭 Comment deleted
Rewrite it in Forth and it will have a stack of problems. Rewrite it in Prolog and it will just not cut it. Comment deleted