Yes and no. Sometimes people try to write a short implementation to be clever (code golf) and the result is another liability. Code should 1. Function as need

Yes and no. Sometimes people try to write a short implementation to be clever (code golf) and the result is another liability. Code should 1. Function as needed 2. Be clear to read and understand 3. Perform well enough Possibly even in the order listed. Performance is the trickiest one of course. Sometimes it's not negotiable and messes with #2. But one should always benchmark and profile to see what needs to actually be done before sacrificing clarity and cleanness.