News for hackers. Stuff that matters.
Re:Attitudes That Lead to Maintainable Code by lacampbell on Wednesday March 08, 2017 @01:38PM (#13822447)
What's fancy to you? What's broadly understood?

Will you get upset if someone in your java codebase uses lambdas or optionals or even the ternary operator? All of the above are still considered black magic to many in our industry.

Re:Attitudes That Lead to Maintainable Code by AstralStorm on Thursday March 09, 2017 @07:34AM (#13828815)
If a standard feature in your language of choice confuses or upsets you when it is not misused... You may have a problem. The problem is typically lack of willingness to learn.
Re:Attitudes That Lead to Maintainable Code by verelo on Wednesday March 08, 2017 @05:29PM (#13824534)
It totally depends on the situation, is it something the whole team needs to work with on a regular basis? And is it really the most optimal solution (those two questions are highly interlinked)?

If that's the case then we might want to a) educate everyone else first or b) pick something we know will be less of a struggle for others to maintain.

I guess there is always option c) ask the original author never to leave and be available 24/7 to answer questions, but that, obviously, isn't realistic.

Edit: I answered the question poorly. Are you "writing art" or doing your job? I don't mind if the outcome is pretty, but your first priority is to do your best in your role within the organization. If the author or the code feels that is the case then generally I won't ever get upset with anything they do.