4 ms·
When you program on a team choices like using procedural vs OOP vs FP aren't up to you since they impact others. You should be coding for your maintenance progr
by phibz 4y ago
When you program on a team choices like using procedural vs OOP vs FP aren't up to you since they impact others. You should be coding for your maintenance programmer, the person who will come behind you, need to quickly understand the code and make changes or bug fixes. The maintenance coder may be you, it might be a team mate or it might be someone yet to join the company.
Use your own time or projects foe exploring programming styles.
- bern4444 4y agoThat's what this article is discussing: A means of writing code in an FP style that is easy for others less or unfamiliar with FP to maintain, debug, and refactor.
- xupybd 4y agoFunctional programming if done well is much better for maintenance. I find a strictly typed functional code base very easy to maintain. It's far less a house of card.
- PointyFluff 4y agoReading someone else's FP is like reading Perl, aka line-noise.
- xupybd 4y agoHaving worked in Perl for years I agree that Perl is most often hard to read. I've also seen some horrific FP. Generally that's because it either FP stuffed into a language that doesn't support it or it's some crazy meta programming that you need a PHD to follow. Boring well written FP is much easier to read IMO than most OO.