Evil Thoughts
-
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.
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.
-
Silverlight[^]???
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
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.
That's controlled by the font selected in the IDE - not by the programmer in the program.
".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 -
That's controlled by the font selected in the IDE - not by the programmer in the program.
".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, 1997Unicode 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.
-
That's controlled by the font selected in the IDE - not by the programmer in the program.
".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[to add to my previous post...] As a demonstration, copy those funky characters into Notepad and change the font. The characters will remain largely the same.
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
-
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
That is ... awesome!
If your actions inspire others to dream more, learn more, do more and become more, you are a leader." - John Quincy Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering” - Wernher von Braun -
[to add to my previous post...] As a demonstration, copy those funky characters into Notepad and change the font. The characters will remain largely the same.
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
And those characters in C# and the code will compile :)
-
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
-
fred_ wrote:
ROLMAO
Really Ostentatiously Laughing My Ass Off?
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
-
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 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
-
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:
but VB isn't case-sensitive unless strict is turned on
No it isn't :D
Option Strict On
Dim Hello As String
Dim hello As String ' Error, Hello is already declared in the current block.Did that make you plan any more evil? ;)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
John Simmons / outlaw programmer wrote:
but VB isn't case-sensitive unless strict is turned on
No it isn't :D
Option Strict On
Dim Hello As String
Dim hello As String ' Error, Hello is already declared in the current block.Did that make you plan any more evil? ;)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}I think this is precisely what John was saying. BTW: My avatar(profile picture) can kick yours all the way from here to Tatooine. :-D
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
Create the Silverlight application using C++ CLI instead of C# and you don’t need any further obfuscation. Unless they know where Nish lives, nobody in his right mind is not going to support this thingy.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
John Simmons / outlaw programmer wrote:
but VB isn't case-sensitive unless strict is turned on
No it isn't :D
Option Strict On
Dim Hello As String
Dim hello As String ' Error, Hello is already declared in the current block.Did that make you plan any more evil? ;)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}VB sees
Helloandhelloas being the same unlessstrictis turned on (at least I think that's the correct modifier).".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 -
VB sees
Helloandhelloas being the same unlessstrictis turned on (at least I think that's the correct modifier).".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, 1997Even with Strict On they are seen as one and the same. VB just isn't case sensitive as far as I know :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
I think this is precisely what John was saying. BTW: My avatar(profile picture) can kick yours all the way from here to Tatooine. :-D
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
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(); }
} -
VB sees
Helloandhelloas being the same unlessstrictis turned on (at least I think that's the correct modifier).".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, 1997Strict has nothing to do with case, at least as far as I've ever heard.
Somebody in an online forum wrote:
INTJs never really joke. They make a point. The joke is just a gift wrapper.
-
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.
