Wow! Can't even begin to say how much this helped me today!

Me: Can you do the javadocs comments
Coworker: I've never done that, *looks for it on google*, I can't do it, I don't know how.
Me: Did no one asked you to comment you code at school?
Coworker: Yeah, but only the ones with '//'
Me: Ok, bring me coffee

Explaining what a method does:
"""Python has docstrings"""
/** Java has javadocs */

SwiftHasSuperFreakinLongMethodNames()
Seriously Apple...

Dynamically typed languages suck. God I hate them

It's like one big clunky free for all. I don't understand how people can work in Python or even JavaScript and tell me that they're good languages with a straight face

Not having proper autocomplete or documentation (a somewhat seperate issue of Python) is a kick in the stomach for productivity.
I've seen people advocate for using EXTERNAL DOCUMENTATION VIEWERS. WHAT

I hate not being able to enforce types so I can reason about little parts of my program. I hate not having an IDE that can actually help me. I hate having to see stupid grep'ed code snippets instead of nicely formatted javadocs. I hate having to double and triple check everything when trying to code. I hate handling effectively opaque values where I don't know anything about the type without looking it up. And I especially hate not knowing what types function parameters need to be.

Dynamic typing doesn't remove types. That, although completely unfeasible, I could respect.
Oh no, the types are still there. Just not for you

It's like solving a jigsaw puzzle with a blindfold on

Last 4 days, struggling to get ship it from a Dev who is reviewing my code.

The comments have already piled up more than the LOC submitted.

The code review consists of just 2 interfaces and a pojo. Hardly 20 LOC in total, excluding javadocs.

I hope it gets ship it soon.
Wish me luck.

Who else uses JavaDocs on their own code and never releases that code...? I do 😂

TGIF... And once again solved another issue brought up by another dev by just reading the javadocs on the problematic Spring annotation

How senior do you need to be to finally learn the first step to solving most problems is to RTFM....

TLDR: RTFM...

My dad (taught me how to code when I was a kid) was stuck serializing a Java enum/class to XML.... The enum wasn't just a list of string values but more like a Map(String,Object>.

He tried to annotate it with XMLEnum but the moment I saw this enum, I'm thinking that's unlikely to work.... Mapping all that to just a string?

He tried annotating the Fields in it using XMLAttribute but clearly wasnt working...

Also he use XMLEnumValue but from his test run I could clearly see it just replaced whatever the enum value would've been with some fixed String...

Me: Did you read the documentation or when the javadocs?

Dad: no, I don't like reading documentation and the samples didn't work.

I haven't done XML Serialization for years thought did use JSON and my first instinct was... You need a TypeAdapter to convert the enum to a serializable class.

So I do some Googling, read the docs then just played around with the code, figured out how to serialize a class and also how to implement XmlTypeAdapter.... 20 mins ...

Text him back with screenshots and basically:

See it's not that hard if you actually read up on the javadocs and realized ur enum is more like a class so probably the simple way won't work...

Chuck Norris could use anything in java.util.* to kill you, including the javadocs.

Found @ Twitter

So for my software engineering class we have to write a game in Java, and let me tell you, it has been a time.

The worst part so far has been the transition over to using a JLayeredPane, so that we actually have a background and a foreground. I offered to handle it, since I've done a bit with swing before now.

So I put together something that I thought should work, only to find that layered panes and layouts do NOT like to work together. So it was off to google...after sooo many hours of pouring over tutorials and javadocs I finally got the layers to draw...only to find that our Buttons had stopped working!

For some reason, putting the buttons inside a JPanel stopped them from actually informing their ActionListener (since the random test button I just added had actually still worked). So OF COURSE that meant I had to rework the buttons too, since their logic relied on that panel.

All in all, what should have been a relatively simple refactoring of our view was tranformed into almost a week's worth of frantic googling and pain through the magic of Java Swing.

Twas the moment while i was exposed to java on the commandline and windows editor and needed to grasp the shit to read input with bufferredReader and Inputstreamreader while my head was constantly spinning between the javadocs and the screen. In that moment my friend opened his eclipse and showed me code completion! And the fucking Screenreader class. I immediatly realized it was not only important to finish the assignment but also as fast and as lazy as possible!

Procrastination Level: Adding Javadocs to my code

Writing javadocs for interfaces with quite complicated methods all day is so fucking exhausting. Programming itself is so much easier than documenting the written code clearly and precicely so that everyone understands it.