|
The word "expert" is bandied about rather loosely these days. Just yesterday I download code from an article at this site from someone who has posted dozens of them and they are almost always very highly rated. This article was also rated very well but the code was horrendous. Even worse than what I have seen in Q&A posts. Seeing something like that removes all pressure what so ever since what I do is considerably better than that. I actually had to spend a fair amount of time bringing it up to my standards.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
 I know what you mean. I am not an MVP, but I have had to fix/rewrite published MVP code to bring is up to my standards. 
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
John R. Shaw wrote: up to my standards.
then you clearly are an expert. 
It's much easier to enjoy the favor of both friend and foe, and not give a damn who's who. -- Lon Milo DuQuette
|
|
|
|
|
some dictionary time:
first "Professional" - someone that gets paid for doing the job. Skill, knowledge (and connections) will dictate how much they get paid
Expert - a person who is very knowledgeable about or skilful in a particular area
- oh, so they could be "very knowledgeable" but just not good at implementing that knowledge.
It like any industry, once you start working with them, then you start to realise they just as fallible as you
|
|
|
|
|
I am just an average joe of the old school (still younger than many here), but I think the same as you. There are several very prolific authors where I facepalmed so hard several times...
I decided just to avoid whatever they write ever since... my head thanks me for that decission 
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.
|
|
|
|
|
then yes. 
|
|
|
|
|
I've written both, and seen both. "Good" doesn't really register with me, unless it *does* something amazing, and non-horribly.
If I can work with the code it is usable. If I cannot, it is horrible. 
Real programmers use butterflies
|
|
|
|
|
If you are new, then anyone is an expert. but if you have been doing what we do for a while, then most of us become "experts" (hate this word really) in more than one area of software development, etc.
So my answer was NO, no, and no again.
Cheers. 
It's much easier to enjoy the favor of both friend and foe, and not give a damn who's who. -- Lon Milo DuQuette
|
|
|
|
|
... but it's really not as bad as the code "experts" post online 
|
|
|
|
|
I can identify with your message, at least with some "experts"
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.
|
|
|
|
|
I don't know who you are referring to ?
It's rare to see production code written by expert in real world environment.
I'd rather be phishing!
|
|
|
|
|
Unfortunately that is all too true.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
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
