Coding pet hates
-
Near the top of my list of pet hates is unnecessary white space changes. You're looking at a piece of code thinking *why?*, so you go and look who last touched the line. Then you look at the rest of that check in and think this is totally unrelated. So you go and look at what they actually changed in the line of code only to find they added a tab on the end. Arrrrhhhhhgggggg. Start again with revision number-- What gives you the shits on a friday afternoon?
What gives you the shits on a friday afternoon? An enema?
Everything makes sense in someone's mind
-
Near the top of my list of pet hates is unnecessary white space changes. You're looking at a piece of code thinking *why?*, so you go and look who last touched the line. Then you look at the rest of that check in and think this is totally unrelated. So you go and look at what they actually changed in the line of code only to find they added a tab on the end. Arrrrhhhhhgggggg. Start again with revision number-- What gives you the shits on a friday afternoon?
I hate that my pet Python [^]ate my Mouse[^]. That wasn't Nice[^]. I tried to talk it out of the Action![^] but I'm no Shakespeare [^]and all I could muster was Smalltalk[^]. I tried to keep Cool[^] and not spill my Cola[^], this was not going to be easy[^]. As I was thinking, it found a gap[^] and attacked a Squirrel[^], all I could hear was a squeak [^]as it rose an Octave[^] or two.
-
Marc Clifton wrote:
I have a few, but at the top of the list are using "this." to get Intellisense to trigger, which is an obsolete habit from older IDE's.
Marc, It's part of the .NET framework guidelines to use
this.to distinguish type members from locals. So maybe not everyone uses it merely for intellisense. The default Style Cop rules will warn you if you forget to prefixthis.to a member field/method.Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
Nishant Sivakumar wrote:
It's part of the .NET framework guidelines to use this. to distinguish type members from locals.
Good point, and I march to a different drummer. :) Marc
-
Nishant Sivakumar wrote:
It's part of the .NET framework guidelines to use this. to distinguish type members from locals.
Good point, and I march to a different drummer. :) Marc
Marc Clifton wrote:
Good point, and I march to a different drummer.
Fair enough. But the few times that I tried to be StyleCop compliant, I actually found that prefixing
this.made the code more readable (for me). Of course it's a very subjective thing so I am sure not everyone'll have the same experience. :)Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Marc Clifton wrote:
Good point, and I march to a different drummer.
Fair enough. But the few times that I tried to be StyleCop compliant, I actually found that prefixing
this.made the code more readable (for me). Of course it's a very subjective thing so I am sure not everyone'll have the same experience. :)Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
Nishant Sivakumar wrote:
I actually found that prefixing this. made the code more readable (for me).
I suspect I could adapt to it, as long as I wasn't coding in VB. Prefacing everything with "My." would be a bit too narcissistic for my tastes. :) Marc
-
Nishant Sivakumar wrote:
I actually found that prefixing this. made the code more readable (for me).
I suspect I could adapt to it, as long as I wasn't coding in VB. Prefacing everything with "My." would be a bit too narcissistic for my tastes. :) Marc
Marc Clifton wrote:
I suspect I could adapt to it, as long as I wasn't coding in VB. Prefacing everything with "My." would be a bit too narcissistic for my tastes.
:-D My is their namespace, Me is their this-pointer!
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Marc Clifton wrote:
I suspect I could adapt to it, as long as I wasn't coding in VB. Prefacing everything with "My." would be a bit too narcissistic for my tastes.
:-D My is their namespace, Me is their this-pointer!
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
Nishant Sivakumar wrote:
Me is their this-pointer!
Oops. I was thinking "My" wasn't right! Marc
-
I hate that my pet Python [^]ate my Mouse[^]. That wasn't Nice[^]. I tried to talk it out of the Action![^] but I'm no Shakespeare [^]and all I could muster was Smalltalk[^]. I tried to keep Cool[^] and not spill my Cola[^], this was not going to be easy[^]. As I was thinking, it found a gap[^] and attacked a Squirrel[^], all I could hear was a squeak [^]as it rose an Octave[^] or two.
-
digital man wrote:
5 cups of coffee and 6 Krispy Kremes[^]... Smile
ha We had a Krispy Kreame eating contest at the office once. The challenge was to be the first to eat a dozen orginials in 5 mins, spectators paid $5 to watch with the winner taking all. It's not as easy as it sounds, I came 2nd with 8.5 eaten and I've never felt so sick. Talk about a sugar rush.
Let me introduce you to a couple of the graduates who are on our shooting club's committee. It'd be a snack to them. I've been a couple of times with them - once which will always stay in my mind is when we went to Bodeans[^] and the waiter thought they were joking when they ordered two plates of ribs a piece for their starters.
I doubt it. If it isn't intuitive then we need to fix it. - Chris Maunder
-
Curses on you. :) I just went shopping (Tesco) and you'll never guess what was on special. Yup, Soreen Fruity Malty. 2 for a quid and well........ I mean I just had to.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
Hope you got plenty of good butter too - not that "mock butter" stuff, it never tastes right!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
Ugh, I hate those kinds of standards... I use #regions for logical groupings, not categorization by type... If a code file is so large that it really needs to be broken down into "Fields" sections and "Properties" sections, then it's time to split it into multiple files... Partial classes are your friend. And if you find yourself making more than a few partials, then MAYBE it's time to split that class up into smaller components.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Its not a question of size - I agree with you on the partial classes wholeheartedly. It's more a "visibility" thing - outlining can collapse a region to a single on screen line, and since you can't open two proper windows on the same source file (Split Window doesn't do it for me, I used Brief for DOS) that helps a bit. It's a personal preference thing, I think.
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
Its not a question of size - I agree with you on the partial classes wholeheartedly. It's more a "visibility" thing - outlining can collapse a region to a single on screen line, and since you can't open two proper windows on the same source file (Split Window doesn't do it for me, I used Brief for DOS) that helps a bit. It's a personal preference thing, I think.
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
Right, but I find it more useful to collapse/expand things based on their logical function, not just based on whether they're a function or a property... If you have a property with a few fields behind it, put the fields with the property... If you have a few functions and properties dealing with rendering, put those in a region... Makes more sense to me.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
Right, but I find it more useful to collapse/expand things based on their logical function, not just based on whether they're a function or a property... If you have a property with a few fields behind it, put the fields with the property... If you have a few functions and properties dealing with rendering, put those in a region... Makes more sense to me.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)
