Evil Thoughts
-
Unicode characters aren't controlled by font. Sure, they look different in different fonts, but they are the same characters.
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
-
Deyan Georgiev wrote:
I think this is precisely what John was saying.
Actually, he was saying the exact opposite :)
Deyan Georgiev wrote:
BTW: My avatar(profile picture) can kick yours all the way from here to Tatooine
Haven't seen it (yet), but I am completely sure that's not the case. Actually those Starship Troopers look like wussy RoboCop clones ;p
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Naerling wrote:
Haven't seen it (yet), but I am completely sure that's not the case. Actually those Starship Troopers look like wussy RoboCop clones ;-P
Yes but they are moving fast and know how to shoot! Not like your clumsy guys who was devastated by an unorganized band of teddy bears with sticks and rocks. ;P
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
At my current job, I work for a defense contractor. When I started at the job, there were five positions on the contract. Last may, one of the guys on the contract deployed to Afghanistan, and is due to return this coming May. This guy WAS the lead on the contract, and declared that all code would be written in VB. This is the same guy that had me convert a silverlight module from C# to VB to C# and finally back to VB (the last conversion was performed right around the 95% completion point. When the contract was renewed this year, one of the five seats was eliminated. Since our company has to give him a job back when he returns from deployment, there is some speculation as to what might happen, given the removal of one of the positions. The company will probably reuqest that he be put back in the spot he was in, thus forcing the customer to remove one of us. Since I'm the new guy, the likelihood that it will be me is high - unless the customer doesn't want to let the other guy back on the contract. At that point, our company has nothing to say about it. Fast forward to today. I was given a task to create a brand new application to track service change requests. I asked our current contract lead if I could do it in Silverlight, and he said yes. I then asked oif I could do it in C#, and he said yes. This is where the sarcastic speculation kicked in regarding the other guy's return and his hatred of anything not VB. It was decided that no matter what happens, I won't be affected because if he doesn't come back onto the controact, I'm gold, and if he does, I won't be around to take the heat, so we discussed the worst case scenario (he's allowed back onto the contract and I'm forced out), and what I could do about it. The answer is "obfuscation". It was generally decided that all identifiers, class names, and method names be made from GUIDs. Even more evil, the same GUID should be used whenever pissible with a single letter having a different case. Since C# is case-sensitive, it will be perfectly fine, but VB isn't case-sensitive unless strict is turned on, so converting it will cause any conversion effort to take a lot longer than is feasible, and it would probably cause any conversion utility to go into terminal spasms trying to keep up. All I have to do now is write an app that will convert all of the identifiers to guids.
".45 ACP - because shooting twice
I was never your biggest fan, JSOP, but on this one I have to take my hat off to ya... That is machiavellian, macabre and genius.
Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. In the face of ambiguity, refuse the temptation to guess.
-
Naerling wrote:
Haven't seen it (yet), but I am completely sure that's not the case. Actually those Starship Troopers look like wussy RoboCop clones ;-P
Yes but they are moving fast and know how to shoot! Not like your clumsy guys who was devastated by an unorganized band of teddy bears with sticks and rocks. ;P
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
I'm sure Starship Troopers have bad days too. And when they have they don't even look cool having it :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
I'm sure Starship Troopers have bad days too. And when they have they don't even look cool having it :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Mine look like Dina Meyer and Denise Richards in uniforms, yours like a shaved Wookiee and are all with the same ugly faces. ;P
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
At my current job, I work for a defense contractor. When I started at the job, there were five positions on the contract. Last may, one of the guys on the contract deployed to Afghanistan, and is due to return this coming May. This guy WAS the lead on the contract, and declared that all code would be written in VB. This is the same guy that had me convert a silverlight module from C# to VB to C# and finally back to VB (the last conversion was performed right around the 95% completion point. When the contract was renewed this year, one of the five seats was eliminated. Since our company has to give him a job back when he returns from deployment, there is some speculation as to what might happen, given the removal of one of the positions. The company will probably reuqest that he be put back in the spot he was in, thus forcing the customer to remove one of us. Since I'm the new guy, the likelihood that it will be me is high - unless the customer doesn't want to let the other guy back on the contract. At that point, our company has nothing to say about it. Fast forward to today. I was given a task to create a brand new application to track service change requests. I asked our current contract lead if I could do it in Silverlight, and he said yes. I then asked oif I could do it in C#, and he said yes. This is where the sarcastic speculation kicked in regarding the other guy's return and his hatred of anything not VB. It was decided that no matter what happens, I won't be affected because if he doesn't come back onto the controact, I'm gold, and if he does, I won't be around to take the heat, so we discussed the worst case scenario (he's allowed back onto the contract and I'm forced out), and what I could do about it. The answer is "obfuscation". It was generally decided that all identifiers, class names, and method names be made from GUIDs. Even more evil, the same GUID should be used whenever pissible with a single letter having a different case. Since C# is case-sensitive, it will be perfectly fine, but VB isn't case-sensitive unless strict is turned on, so converting it will cause any conversion effort to take a lot longer than is feasible, and it would probably cause any conversion utility to go into terminal spasms trying to keep up. All I have to do now is write an app that will convert all of the identifiers to guids.
".45 ACP - because shooting twice
Go the whole hog and write it in brainfuck :suss:
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Mine look like Dina Meyer and Denise Richards in uniforms, yours like a shaved Wookiee and are all with the same ugly faces. ;P
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Well, I must admit you've got a point there. BUT! You're forgetting one very important detail here. Mine is Star Wars, and you just can't beat that period :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
I was never your biggest fan, JSOP, but on this one I have to take my hat off to ya... That is machiavellian, macabre and genius.
Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. In the face of ambiguity, refuse the temptation to guess.
You may as well just come over to the dark side. That's where everyone else is... :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
At my current job, I work for a defense contractor. When I started at the job, there were five positions on the contract. Last may, one of the guys on the contract deployed to Afghanistan, and is due to return this coming May. This guy WAS the lead on the contract, and declared that all code would be written in VB. This is the same guy that had me convert a silverlight module from C# to VB to C# and finally back to VB (the last conversion was performed right around the 95% completion point. When the contract was renewed this year, one of the five seats was eliminated. Since our company has to give him a job back when he returns from deployment, there is some speculation as to what might happen, given the removal of one of the positions. The company will probably reuqest that he be put back in the spot he was in, thus forcing the customer to remove one of us. Since I'm the new guy, the likelihood that it will be me is high - unless the customer doesn't want to let the other guy back on the contract. At that point, our company has nothing to say about it. Fast forward to today. I was given a task to create a brand new application to track service change requests. I asked our current contract lead if I could do it in Silverlight, and he said yes. I then asked oif I could do it in C#, and he said yes. This is where the sarcastic speculation kicked in regarding the other guy's return and his hatred of anything not VB. It was decided that no matter what happens, I won't be affected because if he doesn't come back onto the controact, I'm gold, and if he does, I won't be around to take the heat, so we discussed the worst case scenario (he's allowed back onto the contract and I'm forced out), and what I could do about it. The answer is "obfuscation". It was generally decided that all identifiers, class names, and method names be made from GUIDs. Even more evil, the same GUID should be used whenever pissible with a single letter having a different case. Since C# is case-sensitive, it will be perfectly fine, but VB isn't case-sensitive unless strict is turned on, so converting it will cause any conversion effort to take a lot longer than is feasible, and it would probably cause any conversion utility to go into terminal spasms trying to keep up. All I have to do now is write an app that will convert all of the identifiers to guids.
".45 ACP - because shooting twice
John Simmons / outlaw programmer wrote:
All I have to do now is write an app that will convert all of the identifiers to guids.
Bitchin' ! Look forward to the CP article. best, Bill
"Anyone who shows me my 'blind spots' gives me the gift of sight." ... a thought from the shallows of the deeply shallow mind of ... Bill
-
At my current job, I work for a defense contractor. When I started at the job, there were five positions on the contract. Last may, one of the guys on the contract deployed to Afghanistan, and is due to return this coming May. This guy WAS the lead on the contract, and declared that all code would be written in VB. This is the same guy that had me convert a silverlight module from C# to VB to C# and finally back to VB (the last conversion was performed right around the 95% completion point. When the contract was renewed this year, one of the five seats was eliminated. Since our company has to give him a job back when he returns from deployment, there is some speculation as to what might happen, given the removal of one of the positions. The company will probably reuqest that he be put back in the spot he was in, thus forcing the customer to remove one of us. Since I'm the new guy, the likelihood that it will be me is high - unless the customer doesn't want to let the other guy back on the contract. At that point, our company has nothing to say about it. Fast forward to today. I was given a task to create a brand new application to track service change requests. I asked our current contract lead if I could do it in Silverlight, and he said yes. I then asked oif I could do it in C#, and he said yes. This is where the sarcastic speculation kicked in regarding the other guy's return and his hatred of anything not VB. It was decided that no matter what happens, I won't be affected because if he doesn't come back onto the controact, I'm gold, and if he does, I won't be around to take the heat, so we discussed the worst case scenario (he's allowed back onto the contract and I'm forced out), and what I could do about it. The answer is "obfuscation". It was generally decided that all identifiers, class names, and method names be made from GUIDs. Even more evil, the same GUID should be used whenever pissible with a single letter having a different case. Since C# is case-sensitive, it will be perfectly fine, but VB isn't case-sensitive unless strict is turned on, so converting it will cause any conversion effort to take a lot longer than is feasible, and it would probably cause any conversion utility to go into terminal spasms trying to keep up. All I have to do now is write an app that will convert all of the identifiers to guids.
".45 ACP - because shooting twice
-
At my current job, I work for a defense contractor. When I started at the job, there were five positions on the contract. Last may, one of the guys on the contract deployed to Afghanistan, and is due to return this coming May. This guy WAS the lead on the contract, and declared that all code would be written in VB. This is the same guy that had me convert a silverlight module from C# to VB to C# and finally back to VB (the last conversion was performed right around the 95% completion point. When the contract was renewed this year, one of the five seats was eliminated. Since our company has to give him a job back when he returns from deployment, there is some speculation as to what might happen, given the removal of one of the positions. The company will probably reuqest that he be put back in the spot he was in, thus forcing the customer to remove one of us. Since I'm the new guy, the likelihood that it will be me is high - unless the customer doesn't want to let the other guy back on the contract. At that point, our company has nothing to say about it. Fast forward to today. I was given a task to create a brand new application to track service change requests. I asked our current contract lead if I could do it in Silverlight, and he said yes. I then asked oif I could do it in C#, and he said yes. This is where the sarcastic speculation kicked in regarding the other guy's return and his hatred of anything not VB. It was decided that no matter what happens, I won't be affected because if he doesn't come back onto the controact, I'm gold, and if he does, I won't be around to take the heat, so we discussed the worst case scenario (he's allowed back onto the contract and I'm forced out), and what I could do about it. The answer is "obfuscation". It was generally decided that all identifiers, class names, and method names be made from GUIDs. Even more evil, the same GUID should be used whenever pissible with a single letter having a different case. Since C# is case-sensitive, it will be perfectly fine, but VB isn't case-sensitive unless strict is turned on, so converting it will cause any conversion effort to take a lot longer than is feasible, and it would probably cause any conversion utility to go into terminal spasms trying to keep up. All I have to do now is write an app that will convert all of the identifiers to guids.
".45 ACP - because shooting twice
JSOP You might also try 6 or 8 character ids which include numbers 0,1, upper case letters O,L and their lower cases o,l, then add two randomly selected other alphabetic characters, then use all permutations of the letters and numbers, then all permutations of numbers and reversing the case of the letters except for O and l, one at a time, then as pairs then triplets then all four - the number of combinations is huge. Note, an alphabetic must be first, then anything goes. obtw - you better keep a conversion table so that this can be reversed to meaningful code since you will have to maintain it. Dave
-
I like it. That reminds me of an evil idea I had once too of building some sort of functionality locking/unlocking mechanism, controlled solely by myself, into apps that I build for clients so that in case they screw me I can turn off whatever piece of the app I want and hold it hostage for ransom. I believe something like this probably already even exists but I don't know if I would ever have the heart/professional conscience to use it (I guess depending on how badly they were trying to screw me).
"... having only that moment finished a vigorous game of Wiff-Waff and eaten a tartiflet." - Henry Minute "...who gives a tinker's cuss?" - Dalek Dave "Let's face it, after Monday and Tuesday, even the calendar says WTF!" - gavindon It's plain that they do not yet know what true fear really is. - JSOP 2011
We did this before at a company I worked for, but we made sure to let them know in writing in the contract that "x functionality will expire on x date if the payment schedule is not met". When each payment was received we pushed out a new version of the software with a new expiration date a set length of time after the next payment was supposed to be due. If you make known ahead of time your expectations and the results of them not being met, it goes a long way in terms of satisfaction of both parties and getting what you want/need. If you surprise them with loss of functionality, you're more likely to be sued.
-
We did this before at a company I worked for, but we made sure to let them know in writing in the contract that "x functionality will expire on x date if the payment schedule is not met". When each payment was received we pushed out a new version of the software with a new expiration date a set length of time after the next payment was supposed to be due. If you make known ahead of time your expectations and the results of them not being met, it goes a long way in terms of satisfaction of both parties and getting what you want/need. If you surprise them with loss of functionality, you're more likely to be sued.
-
We did this before at a company I worked for, but we made sure to let them know in writing in the contract that "x functionality will expire on x date if the payment schedule is not met". When each payment was received we pushed out a new version of the software with a new expiration date a set length of time after the next payment was supposed to be due. If you make known ahead of time your expectations and the results of them not being met, it goes a long way in terms of satisfaction of both parties and getting what you want/need. If you surprise them with loss of functionality, you're more likely to be sued.
Very cool. Yes obviously the agreement on this type of thing in writing would be imperative to eliminate the moral as well as legal issues... Cheers!
"... having only that moment finished a vigorous game of Wiff-Waff and eaten a tartiflet." - Henry Minute "...who gives a tinker's cuss?" - Dalek Dave "Let's face it, after Monday and Tuesday, even the calendar says WTF!" - gavindon It's plain that they do not yet know what true fear really is. - JSOP 2011
-
John Simmons / outlaw programmer wrote:
All I have to do now is write an app that will convert all of the identifiers to guids.
Why GUID's if you have 2^21 Unicode codepoints? ;P Just look at the variety here[^]! :rolleyes: ௵ ୈ ௌ ഔ ൠ ઑ औ ڵ Ѿ Ѭ წ ᙶ Or how about braille? ;p ⢪ ⢫ ⢬ ⢭ ⢮ ⢯ ⢰ ⢱ ⢲ All which I know is perfectly valid as C# identifiers.
-
I actually used a Greek lower-case sigma as an identifier (for standard deviation). My project manager made me change it :sigh:
BobJanova wrote:
My project manager made me change it :sigh:
What a dick!
-
MFC was dead in '94 but lingered a 6 year death, silverlight, WPF will be around for a long time, since XAML is part of the Windows 8 presentation layer.
Software Kinetics Wear a hard hat it's under construction
Metro RSSMFC is dead? I interviewed for an MFC job yesterday!
Pete
