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
-
@gitpush i think then you have to kill me for the crimes I'm going to commit, because I have to Change a Java Applikation to Spring and Most of the things I have to do right now are ugly fixes because it has to be finished as fast as possible and the Application is "only" going to be used for around 3 or 4 Years depending when my company is upgrading to MQ Series 9..
-
@2xCmet this is called bad management, what I said applies if time and resources are given and ugly fixes are the result.
But hey, management rarely gives enough time as if we are doing ABC's -
@2xCmet over promising is the worst kind of PR. Always under promise and over deliver, I know it's not easy but be aware of exactly what you are capable of in any given time span.
-
@Zaphod65 Will remember that for the next time, but hopefully it all works our this time.
For me, the worst co-worker is one who works by the principle of quantity over quality or a person who thinks quick and ugly fixes are a valid way to solve problems. Also: If there are unittest, don't fucking dare to change or remove them, just so your code runs without errors.
But in general, I just can't work with people who don't really think about what they are coding, people who just code straight ahead without making the simplest plan about how to solve something. Most of these people realize too late, that their approach was rather shitty, unreadable and unmaintainable.
I often see memes about "I forgot what I coded last [insert timespan here]". Though it is kind of normal, if it takes you too long to find out what you wrote, you should consider overthinking your coding approaches.
Just my 50 cents.
Damn I miss coding... 4 weeks of learning & exams is too long...
rant
wk87