Agreed! Linq makes things easier to write, easier to maintain, easier to understand, and just makes code 'prettier'. I cannot stand ugly code!
M
Member 13046479
@Member 13046479
Posts
-
What book would you recommend to learn C# from 0? -
Acronyms and expressions -- give us your best!From Central Virginia -- FORD -- Found on the Richmond Dump
-
Acronyms and expressions -- give us your best!From Central Virginia -- FORD -- Found on the Richmond Dump
-
Acronyms and expressions -- give us your best!I use SNAFU and FUBAR both. Still.
-
Acronyms and expressions -- give us your best!Haaaaa. A few years ago, I was travelling with some coworkers every other week for "knowledge transfer" (aka "you're on OUR turf now! do this grunt work you persnickety perfectionist group of code monkeys who have made our lives ") at our vendor's HQ. At their location, temp offices for remote managers who had come in to work were named after colors. "Joe is in the magenta office this week", etc. Conference rooms were named after gemstones: "2 PM code review in Sapphire room". And the nine project work areas were named after the planets. We discovered we were *way* too juvenile to work in a place where every time we had to get up for coffee, lunch breaks, restroom, etc., we had to walk past Uranus. The jokes were plentiful, frequent, and totally immature.
-
Acronyms and expressions -- give us your best!I just realized I missed another one. We used to use PEBKAC. I just came upon PICNIC. Problem in Chair, not in Computer. Much nicer to say someone is a real PICNIC to work with!
-
Acronyms and expressions -- give us your best!I think I work there. Everything at my current job -- ESPECIALLY the brand new systems are WYSICUB. I'm going to start using that. Thanks for the laugh!
-
Acronyms and expressions -- give us your best!A guy who I used to work with had two infamous sayings. Sadly, he passed away a few years ago and left a huge gap here, but his wit and wisdom did not go to the grave with him. Two of the best: ~ If you're not causing production problems, you're not doing anything. (supervisor-types weren't fans of that one) ~ IIWD2WISBD2U * If it was difficult to write, it should be difficult to understand. [This, coming from one of two Computer Engineering folks, with everyone else in the shop holding DP/business degrees.] (Lazy developers who couldn't program their way out of a paper bag with a hole in it (or who had yet to master Google) were not particularly fond of that one)