Things to commit just before leaving your job

#1

Post by diegolo » Wed, Aug 19, 2015, 10:17 AM UTC

Things to commit just before leaving your job
gist.github.com

Re: Things to commit just before leaving your job

#2

Post by yarper » Wed, Aug 19, 2015, 11:44 AM UTC

We've got a guy in the office that merges the past over the present all the time. He's not quitting but I imagine if you were to try to break things this would be a good way to do it.

Re: Things to commit just before leaving your job

#3

Post by Kenji » Wed, Aug 19, 2015, 11:45 AM UTC

#define volatile // this one is cool

Oh wow. This literally sent a shiver down my spine. Imagine debugging that.

Also love the randmoness based ones!

Re: Things to commit just before leaving your job

#4

Post by cjslep » Wed, Aug 19, 2015, 11:51 AM UTC

From "How to write unmaintainable code" [0], here is a function declaration that changes signature based on how many times the header is #included:

    #ifndef DONE
    #ifdef TWICE
    void g(char* str);
    #define DONE
    #else // TWICE
    #ifdef ONCE
    void g(void* str);
    #define TWICE
    #else // ONCE
    void g(std::string str);
    #define ONCE
    #endif // ONCE
    #endif // TWICE
    #endif // DONE

Granted, it isn't one line long.

[0] https://www.thc.org/root/phun/unmaintain.html (Cert issue shows up on FF unfortunately)

Re: Things to commit just before leaving your job

#5

Post by kevindeasis » Wed, Aug 19, 2015, 11:51 AM UTC

If only we can get a rosettacode version of this in all languages. I bet trolls will coming out left and right. It would be pure evil.

Re: Things to commit just before leaving your job

#6

Post by wil421 » Wed, Aug 19, 2015, 11:54 AM UTC

yarper wrote: post #2

We've got a guy in the office that merges the past over the present all the time. He's not quitting but I imagine if you were to try to break things this would be a good way to do it.

Got a offshore guy just like that. Constantly committing his whole project where most files are out of date and only the few he worked on are not.

There's no reason for him to commit javascript files he doesn't even work on the front end. It took me forever to figure out he wrote over my files the other day.

Re: Things to commit just before leaving your job

#7

Post by f00644 » Wed, Aug 19, 2015, 11:54 AM UTC

This is when the scriptkiddies start getting involved..

Re: Things to commit just before leaving your job

#8

Post by lfam » Wed, Aug 19, 2015, 11:57 AM UTC

Kenji wrote: post #3

#define volatile // this one is cool Oh wow. This literally sent a shiver down my spine. Imagine debugging that. Also love the randmoness based ones!

Will you explain what this would do?

Re: Things to commit just before leaving your job

#9

Post by masklinn » Wed, Aug 19, 2015, 12:01 PM UTC

kevindeasis wrote: post #5

If only we can get a rosettacode version of this in all languages. I bet trolls will coming out left and right. It would be pure evil.

Most languages don't have a purely textual and completely unsafe preprocessor running during the compilation process, so it would be quite hard.

Re: Things to commit just before leaving your job

#10

Post by mavelikara » Wed, Aug 19, 2015, 12:02 PM UTC

yarper wrote: post #2

We've got a guy in the office that merges the past over the present all the time. He's not quitting but I imagine if you were to try to break things this would be a good way to do it.

I am curious - wouldn't your Version Control system catch this and warn him that "file xyz has changed since you last checked it out, ..." etc?