|
No one person can know every best practice or every best technique, I do think that some people can occasionally write expert code, but that doesn't make them an "expert". It makes them good in one small field. I never call anyone an expert, no-one is.
|
|
|
|
|
What? No ... you're serious? 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
My sentiments, exactly.
/ravi
|
|
|
|
|
There is a race between the engineers, attempting to design more foolproof devices, and the Universe, attempting to design more subtle fools. So far, the Universe is winning.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I do write well laid out formatted code, I was taught Fortran a long while ago so it kind of became an obsession to make the *@&^^* stuff work at all 
What annoys me is being told to put my braces at the end of the function definition. I will not do that I will place my brace at the start of the next line properly indented, and I will get very, very angry at any "intelligent" editor that tries to "helpfully" correct it for me.
|
|
|
|
|
Oh yes, I have to agree. Whitesmiths is the right way!
private void MyMethod()
{
... body ...
}
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I am more "classic" and only indent the things within the brackets, not the brackets themselves.
private void MyMethod()
{
... code ...
if (condition)
{
... code ...
}
}
But this is only some esthetic aspect and personal taste. Nothing to say about quality.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
The good thing about not making end-of-line comments is that in VS you can set all the newline and indent rules exactly as you prefer them, go to the end, delet and reinert the final brace. If you need to hand the code over to someone with different ideas, change the newline and indent rules and repeat, before you hand over the code.
Of course you can do this even with EOL comments. But EOL comments should be nicely lined up, e.g. from col 70, not to draw the attention away from the code statements. Reformatting tends to mess up the nice lineup. But then again, in many current development environments, the fashion is to frown at EOL comments. If you adhere to that, there is no problem.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
