Welp, I'm having a great start with Android Studio...

It would be much easier when a NullPointerException would log also what is null. Instead of just the line.... with multiple possibilities........

Was recently asked if our team wanted to change from Java to Kotlin so I looked over the feature lists but don't see much that's impressive.

One argument was less boilerplate code but I think they're are libraries like Lomboq that can write that stuff for you.

The other was smart type casting and type inference and to that I'm like this sounds like giving monkeys a hammer.

Our JS codebase looks like shit... And our Java app just crashed in prod.

Getting a ton of text messages this morning and thankfully I'm on vacation still...

The error is not caused by NPE... but how some or logic spammed the db..

A new language isn't going to fix this.... And a team that writes this sort of shit logic clearly shows they are incapable of learning a new one probably...

They are already script kiddies... Don't need them to become babies...

OKAY WHAT THE FUCK JAVA.

At school we were assigned the task to do Huffman's algorithm. Since I am way ahead of all the others, I made a GUI for that. (Btw, we use BlueJ for Java, it's just painful)
Now... I made a JTextField to put the output, which would be any character from 0x0 to 0xFFFF, into it.
Apparently, there is a bug in the setText method, which throws random NullPointerExceptions right into your face if you give it those Unicode characters.
So I looked it up:
It was a Bug, in JDK 1.6.something, where putting a 0xFFFF together with a 0x10000 would cause this. Now you may think, do we still have 1.6? No, we have 1.8 v171, WHY THE FUCK DOES THIS SHIT GIVE ME A NPE?! THE WORST PART IS I CAN'T DO ANYTHING ABOUT IT!
AND IT HAS THE WORST UNDEFINED BEHAVIOR:
1. NPE, nothing else happens
2. The Text box just gets invisible, but the border stays visible + NPE
3. The box completely disappears + NPE

Try-catching it doesn't do anything, everytime I fill the box with text, one of those options happens, and the box was never to be seen again! NOT EVEN CREATING A NEW TEXT BOX AND ADDING IT TO MY WINDOW WORKS.

There was MCQ test based on Java we were required to give by our degree college, partnered with this firm.
The image is not even the tip of the iceberg.
3 of the four options in every question were same.
Select A and later come back to the question, you'll find option C as selected.
Never was I ever this frustrated, not even all the times I've encountered a NPE.
Shitty shitty shitty as fuck.

This guy keeps insisting there’s a bug in my code, on a specific line. The stack trace shows that a NPE is thrown in his code, before that line is reached, but he won’t be persuaded by this argument and won’t send me the class.

Somehow he’s certain that Java would throw a NPE on trying to iterate through an empty list, as if his code was even returning an empty list. Can you imagine the chaos.

Sweet Zombie NullFuckingPointerException...

New Rule: When creating an API (I'm looking at you, Java), designers must include a boolean flag in the parameter list of any method which throws a NullPointerException.
If TRUE, this means that a NULL result is non-trivial and the method should therefore THROW an NPE.
If set to FALSE, this means that NULL is completely f*cking trivial so whenever there's a NULL result, just instantiate a new instance of the return type and return that, 'cause that's what was gonna happen in the catch block of the NPE anyways.

Hit into NullPointerException on production then I saw this in the source code,

entity.getKey().getValue().contains("a string"):

When I don't code with IDE support, I will be like is it NullpointerException or NullPointerException