Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
sharktits3877598dId rather read ugly code than one liners
Ugly code > one liners
I still don’t understand why would someone decide for one liners when there is no significant performance gain. Code should be written in a way that helps the next developer understand what you did.
Now... don’t confuse ugly code with stupid code
billgates1831498dWell the reason I hate technical interviews is because I have to solve problems elegantly that are in the end useless.
LoC don't matter honestly... It's how efficient the code is and how much time it saves....
I'll figure out an O(N) solution if you actually gave me **a real problem that needs it** A few milli/seconds saved ain't worth the brain power...
@matteusbrevik given that its not production code, being able to use one liners shows that you know all the fancy constructs. Lambdas, maps, zips...
Voxera497598d@matteusbrevik in many code wars the point is not readable code but either fast, short or obfuscated code depending on the challenge.
Most of those solutions, except the fast one, would qualify as the wrong solution in most production scenarios.
-vim-359298dThere’s a problem where someone did:
from *some default module* import *a function that solves the problem* as *the name of the function needed*
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job