Worderful object names
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
-
Wow...just wow. My Condolences. Thank you for making me feel better about my life though :)
Man, after reading that, my life is simply great!
--------------------------- Both optimists and pessimists are important in technology. The optimist invented the aeroplane; the pessimist invented the parachute. Regards, Hesbon Ongira Nairobi, Kenya.
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
At least they are using Hungarian notation I guess :doh: ?
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
Sounds like somebody needs to be dragged into a dark alley :suss:
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
I don't think your company employs humans. Get out before they notice you're not one of them! :)
- S 50 cups of coffee and you know it's on!
And run away as fast as he can, I might add.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Pssst.. I heard that they are soon running out of the 6 digits names, and going to migrate them to GUID...
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
Leave that environment as soon as possible :cool:. And thank god they havn't used chines Symblos Instead...
Believe Yourself™ :->™
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
Holy crap. Inbuilt obfuscation.
Deja View - the feeling that you've seen this post before.
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
I worked for a company many years ago that had the same type of moronic standard. They also had rules against nested loops & if's. They were too hard to read. You were supposed to break out the inner loop, stick it below the outer loop, then "goto" back into the upper loop. That was so stupid I didn't know how to respond. Please give us the name of this company so I can make sure they are on my blocking list for my resume.
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
This code is self documenting, right? :laugh:
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
mine is slightly better: a,b,c,d,e,f,g,h,i,j... asdf and qwer as variables names.
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
That just looks like generated code (albeit poorly generated unless it is also obfuscated). I say, get a new application for generating the stuff. That is atrocious!
Matt
(Find your own niche! This one's mine.) -
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
Do they also have a mandate that every second line should be blank, to improve readability?
Cheers, Vikram.
"If a trend is truly global, then that trend ought to be visible across ANY subset of that data" - fat_boy
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
-
My company has a well organized naming rule. It's a standard which has been developed for a few years. Look: Table names like: TB200010 View names like: VI600230 Procedure names like: USP980010_07R Web services names like: WS210080.asmx Web form page names like: UI400740.aspx Reporting service page names like: RPT1731.aspx There are thousands of objects like the aboves. Here the example (real one): // ???? public class UI200020 { // ??? ??? ?? string TabPageUrl01 = ...; string TabPageUrl02 = ...; string TabPageUrl03 = ...; string TabPageUrl04 = ...; string TabPageUrl05 = ...; // ??? ?? private WS980010.XD980010 xd980010UserInfo; // ??? ???? WS200010 wsProxy = ...; WS100010 wsProxy2 = ...; // ? ??? protected System.Web.UI.WebControls.DataGrid dgListSub01; protected System.Web.UI.WebControls.DataGrid dgListSub02; protected System.Web.UI.WebControls.DataGrid dgListSub03; protected System.Web.UI.WebControls.DataGrid dgListSub04; protected System.Web.UI.WebControls.DataGrid dgListSub05; protected System.Web.UI.WebControls.DataGrid dgListSub06; protected System.Web.UI.WebControls.DataGrid dgListSub07; protected System.Web.UI.WebControls.DataGrid dgListSub09; protected System.Web.UI.WebControls.DataGrid dgListSub10; protected System.Web.UI.WebControls.DataGrid dgListSub11; protected System.Web.UI.WebControls.DataGrid dgListSub12; // ???? ?? ?? ?? protected System.Web.UI.WebControls.ImageButton ibtnTabMore01; protected System.Web.UI.WebControls.ImageButton ibtnTabMore02; protected System.Web.UI.WebControls.ImageButton ibtnTabMore03; protected System.Web.UI.WebControls.ImageButton ibtnTabMore04; protected System.Web.UI.WebControls.ImageButton ibtnTabMore05; protected System.Web.UI.WebControls.ImageButton ibtnTabMore06; protected System.Web.UI.WebControls.ImageButton ibtnTabMore09; protected System.Web.UI.WebControls.ImageButton ibtnTabMore10; protected System.Web.UI.WebControls.ImageButton ibtnTabMore11; protected System.Web.UI.WebControls.ImageButton ibtnTabMore12; // ? ?? ?? protected System.Web.UI.WebControls.Label lblSUBTITLE01; protected System.Web.UI.WebControls.Label lblSUBTITLE02; protected System.Web.UI.WebControls.Label lblSUBTITLE03; protected System.Web.UI.WebControls.Label lblSUBTITLE04; protected System.Web.UI.WebControls.Label lblSUBTITLE05; protected System.Web.UI.WebControls.Label lblSUBTITLE11; protected System.Web.UI.WebC
I should work with tons of code like THAT. Fantastic, isn't it?
More like Craptastic...
Could be worse though. I knew a guy who only used the characters Q,O,0,1,I,l in his variable names. He evidently believed they should be hard to understand as well as hard to type....
'droid