16 comments

[ 2.9 ms ] story [ 43.4 ms ] thread
I've seen this many times, but this is the first time I noticed the issues list. Absolutely hilarious.
gah, RxJava upgrade was proposed 5 years ago. No action.
This is enterprise Java, there are dead serious people creating software like this and demanding software like this. As a person who paid mental tool dealing with both, this codebase makes me anxious.
If you want code like this just demand 100% unit test coverage on any Java project. This is what will magically pop up at the end.
Hook up to the codebase a tool to automatically measure code coverage, assign to the project scrum master, POs, PMs, and few meek developers. Even enums will be tested. This duality is brain damaging for me - here you laugh but we meet in the office and it will be a requirement.
My favourite part of this satire is the code of conduct. Straight out of a Monty Python sketch!
It looks to me like the code of conduct is just a generic code of conduct that is commonly used on real projects.
We live in incredible times, don't we?
There's an open PR containing the following:

if (!myResultingStringFromIntegerToStringConversion.equals(myResultingStringFromIntegerToStringConversionThatIsUsedForChecking)) { final IllegalStateException myIllegalStateExceptionThrownBecauseMyResultingStringFromIntegerToStringConversionDidNotEqualMyResultingStringFromIntegerToStringConversionThatIsUsedForChecking = new IllegalStateException("myResultingStringFromIntegerToStringConversion did not equal myResultingStringFromIntegerToStringConversionThatIsUsedForChecking!"); loggerUsedToOutputPossibleErrorsFromMyResultingStringFromIntegerToStringConversion.error(myIllegalStateExceptionThrownBecauseMyResultingStringFromIntegerToStringConversionDidNotEqualMyResultingStringFromIntegerToStringConversionThatIsUsedForChecking); } return new String(myResultingStringFromIntegerToStringConversion);

Lol I enjoyed that.

(comment deleted)