Saying "Welcome!" to the 'next' guy (or gal) who replaces you
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;PIt really should depend upon whether they sought your job or were offered a job that happened to be yours. I had no problems with the guy that replace me at my last (non-contractor) job. He took a job offered to him. Wouldn't anyone? Target your punishment to the deserving.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
It really should depend upon whether they sought your job or were offered a job that happened to be yours. I had no problems with the guy that replace me at my last (non-contractor) job. He took a job offered to him. Wouldn't anyone? Target your punishment to the deserving.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Then choose the last last option offered!
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;PI see your company doesn't have code reviews or source control. If you tried to do something like that to my code base (although would be easy for me to reverse since I use source control), I'd do my best to make sure the only code you wrote again was HTML. Why burn bridges? Why make it hard for the next guy? Why not just burn the place down, or put stricnine in the guacamole? Do that at a couple places of employment and I assure you it will become very difficult to find a job. Just because people have gotten rid of me in the past, most come back and pay me for things in the future, mostly because I make transition easy for them.
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;PWhy then 'next'! How he should be punished. How it his fault you lost your job. If it's not yours than find the who and fire on him!!!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;POK, people. If someone *really* were going to do this, they shouldn't have been given that job *in the first place*. This is "The Lounge", is it not? You know, a place where ya go for a break, maybe down a soda or something, and banter with others about things just to slip yer mind out of 'code mode' for a few minutes before ya dig back in?! It's not like I'm saying go add yellow food coloring into the clear-see-through water dispenser. And, with all the postings submitted here about having to "take over someone else's crappy set of code", if the last option isn't actually truth, if even to a simple degree, then a) quit posting about having to take over someone else's code, b) vote down the post, or c) delete the OP, for Pete's sake (then post an explanation as to who "Pete" is and why it's for his "sake"), then d) take a few dozen chill-pills. OH, wait, I forgot an emoticon in the OP denoting it's HUMOR or adding such the disclaimer. Sheesh! ==== EDIT: There, Emoticon added to the OP denoting it's proffered as humor/silliness and not some actual recommended action. Again, Sheesh!
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;P -
OK, people. If someone *really* were going to do this, they shouldn't have been given that job *in the first place*. This is "The Lounge", is it not? You know, a place where ya go for a break, maybe down a soda or something, and banter with others about things just to slip yer mind out of 'code mode' for a few minutes before ya dig back in?! It's not like I'm saying go add yellow food coloring into the clear-see-through water dispenser. And, with all the postings submitted here about having to "take over someone else's crappy set of code", if the last option isn't actually truth, if even to a simple degree, then a) quit posting about having to take over someone else's code, b) vote down the post, or c) delete the OP, for Pete's sake (then post an explanation as to who "Pete" is and why it's for his "sake"), then d) take a few dozen chill-pills. OH, wait, I forgot an emoticon in the OP denoting it's HUMOR or adding such the disclaimer. Sheesh! ==== EDIT: There, Emoticon added to the OP denoting it's proffered as humor/silliness and not some actual recommended action. Again, Sheesh!
If it makes you feel better, I could tell you were not being serious about it but just "shooting the breeze." :) Written communication can be terrible because you miss a lot of little nuances of communication.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
If it makes you feel better, I could tell you were not being serious about it but just "shooting the breeze." :) Written communication can be terrible because you miss a lot of little nuances of communication.
There are only 10 types of people in the world, those who understand binary and those who don't.
So, my post has a slight chance of being nominated as "Post of the Year", then?! Oh, OK. You're gonna nominate it for "Post of the Decade" instead, then? :wtf: Fair enough! :omg:
-
Nothing to do, actually: your code is pretty ugly as it stands, already.
Veni, vidi, vici.
Was obviously lookin' at someone's profile pict when coding that day ... perhaps even my own! ;P
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;PHahaha, this is fantastic. I've definitely found some interesting comments in my own code a few months later on a day I was feeling particularly snarky or quirky. One of my favorites was for a calendar control. It's just a few lines of 'Brand New Day' from Doctor Horrible with some ♪ ♪ ♪ for good measure.
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;PMacSpudster wrote:
Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?Definetely i will add this to my code files! :laugh:
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;P -
Some ways to say "Welcome!" to the 'next' guy (or gal) who takes over (or replaces) for you. * Insert 30, 50, or, hey, even 1,000 blank lines at the top of each code file; .... - for added effect, comment on the last blank line:
Remove these above blank lines ... someday..... - Better comment:Above lines reserved for 'smarter' / 'more effecient' code I'll think of... someday.* Everywhere you didn't comment, but should have, putHey, new guy, consider adding comments here.* Create a Do/While loop that doesn't run except on the 3rd Tuesday of the 4th month, or exists only when 'Blue' is chosen from a list, then add a commentNeed to add 'Blue' to the list...; (put an Application.DoEvents() in there, though; well, if you want!) (Technically, this would be disruptive. So, use a counter and iterate a max # of times; 1,000,000 comes to mind....) * Put in 30+ or, hey, 300+ "Start" class files, with .Net calling the first, the creating & calling the 2nd, which creates & calls the 3rd, which creates & calls the Nth & so on. The final Nth class's top comment:Start each day anew. .... - Or, put a random number chooser between 1 and N and call that random class with a commentFinal Nth Class will eventually be called ... hopefully.(Technically, this would be disruptive. So use a counter and don't go past the actual # of N start files.) * Create a quick .exe called "CriticalComponentTester.exe" which merely pops up a window readingGet a cup 'o coffee & start testing there, Buddy-Boy (or Gal)!* A comment at the top page of the most critical app:Taking over someone else's code is like taking over another pirate ship. Let the Treasure Hunt begin! Map? What Map?!?;PReplaces me ... ? Replaces me ... ? Oh, you meant "The guy (or gal) who will occupy the post that you have vacated." Now I get it. Replaces Me! :laugh: :laugh: :laugh: :laugh: :laugh: :laugh:
All that is necessary for Evil to succeed is for Good Folks to keep voting for their Party. - Cornelius Thirp
-
Replaces me ... ? Replaces me ... ? Oh, you meant "The guy (or gal) who will occupy the post that you have vacated." Now I get it. Replaces Me! :laugh: :laugh: :laugh: :laugh: :laugh: :laugh:
All that is necessary for Evil to succeed is for Good Folks to keep voting for their Party. - Cornelius Thirp
A.k.a. ... Comment at top primary code page:
So, your the "Refactored" Employee they came up with? ROTFLMFAO!!! -
OK, people. If someone *really* were going to do this, they shouldn't have been given that job *in the first place*. This is "The Lounge", is it not? You know, a place where ya go for a break, maybe down a soda or something, and banter with others about things just to slip yer mind out of 'code mode' for a few minutes before ya dig back in?! It's not like I'm saying go add yellow food coloring into the clear-see-through water dispenser. And, with all the postings submitted here about having to "take over someone else's crappy set of code", if the last option isn't actually truth, if even to a simple degree, then a) quit posting about having to take over someone else's code, b) vote down the post, or c) delete the OP, for Pete's sake (then post an explanation as to who "Pete" is and why it's for his "sake"), then d) take a few dozen chill-pills. OH, wait, I forgot an emoticon in the OP denoting it's HUMOR or adding such the disclaimer. Sheesh! ==== EDIT: There, Emoticon added to the OP denoting it's proffered as humor/silliness and not some actual recommended action. Again, Sheesh!
I found the people taking you seriously even funnier than the original post!
.dan.g. AbstractSpoon Software
email: abstractspoon2(at)optusnet(dot)com(dot)au
