Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
I have to deal with code written by an Idiot that thinks the else statement is a luxury and should not be used. Rather write code like:
if { return; } if { return; } -
A dev writing 400+ lines of code functions to avoid context switching…
Also writing long af conditions inside if statements cause otherwise “we use extra memory” -
fhaji863y@EdoPhoenix early return is more clean than if else but idk, in your case seem like the second if have the negative result of the first if statement so the if is unnecessary.
-
@johnmelodyme cause srp doesn’t stand for single responsibility principle, it stands for singles raving party
💯%
Related Rants
What was the most rubbish developer you had worked with?
I will go first , once I worked with a Dev who used dashes for naming variables (eg _ = 'a' , __ = 'b', ___='c'), placing every everything in the main class . We were working on android (java) project back then. He decided to place everytime in the main activity, rewriting redundant functions. And he never use git, he literally use hard-disk and Google drive to back up his code which made us difficult to know which part of code he wrote. I quit working there because he was the Senior Project Manager.
question
dev
rubbish
curious.