Sometimes my code

Jun 11, 2017 5:21 PM

Puitulo

Views

74886

Likes

1168

Dislikes

40

Sometimes my code is like...

Is there a bell above that ghost balcony?

8 years ago | Likes 1 Dislikes 0

Sometimes my code

8 years ago | Likes 2 Dislikes 0

Not sure how this translates to coding. I'd call the police if I found a bright red circle painted on my house.

8 years ago | Likes 3 Dislikes 0

ya thats probably blue byte

8 years ago | Likes 1 Dislikes 0

Thank goodness for the red circle, I would never have noticed that

8 years ago | Likes 2 Dislikes 0

documentation :D

8 years ago | Likes 1 Dislikes 0

DLC

8 years ago | Likes 1 Dislikes 0

Good use, of comma.

8 years ago | Likes 5 Dislikes 0

I, know right?

8 years ago | Likes 3 Dislikes 0

You could always comment it out until you notice something's broken and then put it back in.

8 years ago | Likes 3 Dislikes 0

Commented code is broken code. Delete that shit, let source control hold your records. Comments are for comments.

8 years ago | Likes 2 Dislikes 1

If(balcony!=important) {delete balcony;} else { cout << "fuck" << endl; }

8 years ago | Likes 54 Dislikes 2

I C++ what you did there.

8 years ago | Likes 16 Dislikes 0

Not sure whether it's kosher practice, but I always name objects like this "1originalname", then I know I where it is in case figure a use.

8 years ago | Likes 1 Dislikes 0

That entire wall will collapse if you remove that balcony. Just don't.

8 years ago | Likes 1 Dislikes 0

I get the referencr, but don't know enough code to leave a witty comment.

8 years ago | Likes 2 Dislikes 0

I read the yellow text like Chris Walken because of that comma.

8 years ago | Likes 1 Dislikes 0

Non mais j'anticipe ! Si vous voulez construire un deuxième étage paf vous pouvez parce qu'il y a déjà un balcon pour y accéder

8 years ago | Likes 1 Dislikes 0

looks like where the condenser would go for the hvac to prevent theft but they changed their minds

8 years ago | Likes 8 Dislikes 1

You prevent theft by punishing criminals.

8 years ago | Likes 1 Dislikes 7

Ok, what if I just... and now line 4, 7, 100, and 200 arn't working. Mother FUCKER!

8 years ago | Likes 1 Dislikes 0

To the SDD. Away!

8 years ago | Likes 1 Dislikes 0

It's part of a Catch.

8 years ago | Likes 20 Dislikes 1

Dammit I wanted to say this, maybe next time I'll Try

8 years ago | Likes 9 Dislikes 0

Maybe next time, you will...catch...him

8 years ago | Likes 1 Dislikes 0

But wait! There is a catch

8 years ago | Likes 1 Dislikes 0

just make it nullified. half the time 3 of my methods only exist because without them the code doesnt work even though i shouldnt need to

8 years ago | Likes 1 Dislikes 0

run a method through another method...

8 years ago | Likes 1 Dislikes 0

Comment it out and the code compiles. Delete it and it doesn't.

8 years ago | Likes 44 Dislikes 2

Makes me scream

8 years ago | Likes 3 Dislikes 0

The worst bugs are the ones not immediately caught at compile time

8 years ago | Likes 4 Dislikes 0

Except it could be called in runtime for something you had no clue it did

8 years ago | Likes 8 Dislikes 0

Just comment out and leave forever

8 years ago | Likes 11 Dislikes 0

Ya, one compile doesn't mean there are no circumstances it would ever be needed for...

8 years ago | Likes 2 Dislikes 0

wall.appendChild(balcony)

8 years ago | Likes 97 Dislikes 3

Erm, cntrl + z ?

8 years ago | Likes 3 Dislikes 0

wall.getChild("balcony").xOffset(5)

8 years ago | Likes 28 Dislikes 0

wall.getChild("balcony").yOffset(-1)

8 years ago | Likes 6 Dislikes 0

balcony.setBarrier(STD_WAISTHIGH, STD_TOOWIDE)

8 years ago | Likes 1 Dislikes 0