I don't know what to say

The first rule of the tautology club is the first rule of the tautology club... -xkcd

...the longest way to cast an int as a long

Can't help thinking that needs to throw a NotImplementedException!!

clearly missing the comment to be perfect

//given the position returns the position

"You can be whatever you want to be. Just tell me, and I'll make it happen." - getItemId

@Lukas

long value = new Long(Integer.toString (739));

I saw this one in production code once

this is funny..

refactor that shit!

I actually see it as a valid abstraction (that type conversion is still wrong though). I can imagime scenarios wjere that abstraction could be useful, wih subclasses having different indexing methods for example.

again, the type change is still wrong.

I cringed.

return items.get(position).getId();

to be fair, in Android that function is provided by abstraction to allow the developer to customize list adapters. it is actually quite useful. though I can't remember why it would return a long.

@aimanb Yeah I did - deleted it for good!

Everytime I see something like this I wish for a comment from the OP such as:

"Plot Twist: the lead of the project requested it. "

Now if only the stress ball limit was still at 150++ :/
#stress

@olpe did it move up again?

@brettmoan Yes. I think it is 175

To the upvote mobile batman!

@Knossos could be because resource IDs are longs?

@olpe and the ball has been earned!

I sense this code is from recycler view

I like the dark IDE theme 😂😂

thingking

setter and getter?

yay?

I hate stuff like

public int getID() {
return id;
}

Good example of the identity function used wrongly.