Yeah, agree. It is subjective. This is what makes it hard. Also, how do you convey context in the correct way so that when you look at the code later it still makes sense?
Therefor it's a good idea to spell out with your team what the expected base level of the audience is.
Depending on that, you can decide what patterns, libs, styles etc... can be used.
E.g. I expect our team to know/learn entry level functional programming concepts like functor and monoid. I accept that monad is too abstract for most, so only introduce it sparcely and have it documented clearly.
Not taking it for granted us greatly beneficial to avoid lenthy 'yes/no' pingpong games.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, agree. It is subjective. This is what makes it hard. Also, how do you convey context in the correct way so that when you look at the code later it still makes sense?
The Clean Code book is a good read on this topic.
It is subjective.
Therefor it's a good idea to spell out with your team what the expected base level of the audience is.
Depending on that, you can decide what patterns, libs, styles etc... can be used.
E.g. I expect our team to know/learn entry level functional programming concepts like functor and monoid. I accept that monad is too abstract for most, so only introduce it sparcely and have it documented clearly.
Not taking it for granted us greatly beneficial to avoid lenthy 'yes/no' pingpong games.