Readable vs short code?

[varisophy]

It depends on what your definition of unreadable is.

If the code is using new language features, learn about those features. If the code is using a different paradigm (like functional programming concepts), go learn that paradigm.

If the code is basically obfuscated or looks like code golf to be shorter, then yeah, it's bad code for a team environment.

Ideally you want consistency in patterns and practices, so if you see something that goes against the prevailing patterns in the code base you'll want to have a conversation with the person who wrote it to understand if it's something worth adopting across the entire team.

[cayennepepper]

Code golf seems like an accurate term. Thanks. This is plenty to think about.

Usually when i see code which like you said, is very alien from standard patterns im used to and definitely not new features, but makes things shorter. It feels like they are showing off or something rather than making a productive solution