|
|
|
|
|
by antoaravinth
3567 days ago
|
|
>> 5. Can be easily extended by any other developer I can remember a instance, when I started my carrier. I was a JS developer. I wrote a module with Functors, Compose, Partial etc. In code review my team told they didn't understand anything and reading such a code is not pleasant for them. I was upset, I was thinking why my team is not happy with it. Today I can make lot of sense; stick to the pattern/design of your team. If your team follows / loves functional programming in your project, stick to it. If not try to advice them why functional programming would be better than normal approach. End of the day, all it matters is writing simple, elegant code which others can understand. |
|