Details
-
AboutSW engineer in java. Like gaming, hockey, anime
-
Skillsjava, c#, c, xml, soap, rest, html, css, js, php
Joined devRant on 11/3/2017
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
-
Friend1 (being lewd): I'll merge you in to my git repository
Me: When you try to merge but she has her special days of the month it's called a merge conflict
Friend2: It's not a merge without a little blood1 -
FUCK YOU EA. FUCK YOU AND YOUR CRAPPY SELLOUT GAMES. HOW CAN YOU BE SO BAD AT WHAT YOU'VE BEEN DOING FOR SO LONG.10
-
when someone judges you for lines of code. and all you do is "please tell my boss to pay me like that".
-
!rant
I fucking hate maven and its shitty principles and the pain in the ass it fucking is to fucking use a dependency from another fucking repo that isn't in your fucking artifactory yet and how it can't fucking resolve it even when you downloaded it manually to your fucking m2 cache2 -
First Rant here.
So I was working on some integration test issues when I found this by accident made by a professional level SW engineer:
@Test
public void testMethod() throws ApiException {
Response res = null;
try {
res = serviceToTest.callMethod();
} catch(Exception e) {
assertNull(res);
}
}
Was wondering why tests were being green after some code changes I've made cuz tests could have not been green afterwards.
Together with a senior (I'm also professional only) I've tried to explain him for a good 1-2hrs why this code is useless and he still did it. Good thing there are no errors in the real implementation from him after fixing the tests as it's code freeze here and we are having go live in a few days 🙃
Also luckily he isn't working on our code anymore and has only been doing so for a few weeks.
Wasted a day with it and gonna check all of his code now before I run in the next surprise.1