The naming standards at my new job make my head hurt.
-
-
Replying to @random_eddie
It's not just that they have so many different ones, or that when one was used it wasn't used consistently. That's to be expected. Sadly.
1 reply 0 retweets 0 likes -
Replying to @random_eddie
It's the /actual/ naming standards that they chose. All of them. Even when each is used correctly, they're all WRONG.
1 reply 0 retweets 0 likes -
Replying to @random_eddie
esxnyc00prd esxnyc01prd esxnyc00dev a) Don't index from zero! WTF is wrong with you? b) The index comes LAST!! WTF is wrong with you? !?!!
1 reply 0 retweets 0 likes -
-
-
Replying to @MorlockP
@random_eddie here's my rant about filenames, etc. If there are fields in the name, most likely to change go last. Sorting should group them2 replies 0 retweets 1 like -
Replying to @MorlockP
@random_eddie in a way that both makes sense (grouping server fields then client, and only w/i those blocks iterating by version # or whatev1 reply 0 retweets 0 likes -
Replying to @MorlockP
@random_eddie and ideally for field X all possible values x1 x2 x3 should same char length serv_logg_1 serv_logg_2 serv_conf_1 serv_conf_22 replies 0 retweets 0 likes
@random_eddie
client_logg_1
client_conf_1
client_imag_1
client_imag_2
"big endian"
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.