The Code Project vs. MSDN?
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
Screw the dumb clod. Take him off your mailing list, he obviously can't or won't learn, so he'll be obsolete soon and you won't need to worry about him.
"People who bite the hand that feeds them usually lick the boot that kicks them." Eric Hoffer "The failure mode of 'clever' is 'asshole'" John Scalzi
-
I have to agree... :laugh:
-
I don't judge a book by its cover - so I don't care if an article is on MSDN, CP, C# Corner, SlashDot or Mr. Pinkies House of Pain... There are good articles and bad articles. **EDIT see the message below for a link to a blog that contains no useful information whatsoever :)
___________________________________________ .\\axxx (That's an 'M')
very true... have to judge for yourself with each case...
-
Two words: Sacha / Josh. Point him to their articles and see if he changes his mind.
CG is the only person whom he needs to meet to change his mind about Microsoft. :)
My Blog *cough* My Achievements: *cough* * Posted 25,000th message in GIT O_O * Official supporter of the "thatraja's GIT Meet Sponsor Foundation" :D What you do, when you don't know what to do is what you do when you don't want to do what you do.
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
What ever I believe is never compare one thing with another because both has some unique advantage. It's upto developer to whom prefer, Where they fill that this is the good for them they can prefer that way.............. Dot Net Stuff
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
They're not competing, as they don't offer the same content. I love my codeproject As it has article's on topics that Microsoft simply wouldn't touch (think ICSharpEditor and DotMSN), and there's an option to contact the author of the article. I love my MSDN Because it has complete walkthroughs, tutorials and how-to video's. It's written by people who got paid to write that documentation, and that's noticeable as they're consistent in phrasing and the use of definitions. They're focussing on the framework, and how to use it in a Windows-environment. Block either site, and my productivity will suffer :)
I are Troll :suss:
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
CP = 100 MSDN = 5
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
-
Yep, this guy sounds like a knob. Microsoft fan-boys are almost as painful as Apple fan-boys... ( almost :) ) If all he knows is MSDN maybe he thinks half-complete, poorly structured, poorly explained ramblings (abounding with outdated information and broken links) pass as valuable?
Naerling wrote:
Just thought I'd ask the community directly
And there you have it - if you're interested in investing in something you don't go to the salesman for information, you go to his customers.
Only that CP isn't selling anything, it's free. Whereas MS does sell, and his boss is singlemindedly following their advice only!
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
Honestly, I use both. I use MSDN for how M$ thinks it should be done and generally this works well. Then I'll use CP, to find out how to actually get it to work in my project. I find many of the articles in CP that actually apply the methods that I seek, and I find that useful. There are a few resources I use on the internet, but I find myself back here or referring co-workers to Code Project. Mostly I find the posters and regulars here very accommodating. :cool: The information here is applied by people who need to use it in real world situations, and often times using programming languages they're not altogether fond of but are required to use them due to duty and need of a paycheck.
It was broke, so I fixed it.
-
My expression is that the articles on MSDN are more theoretic while that on CP more practical.
TOMZ_KV
I would tend to agree. User articles on sites like CP are individual interpretations and practical implementations of the technology. MSDN is a hugely valuable resource as it provides excellent background information on that technology.
I wasn't, now I am, then I won't be anymore.
-
I've found much more relevant and technically correct articles on CodeProject than what I ever read or found on MSDN. That said, MSDN does have good stuff, but CodeProject has much more. Consider this: CodeProject has thousands of contributors. MSDN has far, far fewer (in the hundreds). Why? MSDN is a print publication. It doesn't scale. There are 12 issues per year with maybe a dozen articles each, so that's 150 articles a year. Over ten years, that's 1500 articles. CodeProject has literally thousands of articles. Admittedly some of them are not so great, but many are excellent articles. What you need to do is show your boss some articles from MSDN that refer to CodeProject articles. There are some. Beyond that, I agree with Hans, find a new job. That guy is an idiot and a disaster waiting to happen and it will be blamed on you.
"If your actions inspire others to dream more, learn more, do more and become more, you are a leader." - John Quincy Adams "Let me get this straight. You know her. She knows you. But she wants to eat him. And everybody's okay with this?" - Timon
I have to agree, my Former Bitch Supervisor From Helltm was the same. She believed the sun rose and set on Redmond. Once we ran into a compiler error that was generating bad code. Normally her attitude was that program bugs were like roaches, if there was one in your code, there had to nine others. And no program was bug free. We showed her the C code and the compiler output. She still believed the problem was ours. But, we said, you stated the belief that all programs had bugs, what's different here? It's a compiler she said. To her mind compilers were not programs. Besides, this one was written by Microsoft and they could do no wrong. The alternative is to wait it out. Incompetency like this will either get them promoted or they will find greener pastures. In my case she was promoted and then finally downsized after management finally realized she was an idiot.
Psychosis at 10 Film at 11
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
My friend, recently I had a discussion with a colleague about the big mistake of to be extreme fan of a technology (Java/.Net/C), brand (Samsung, Dell, RIM), or methodology. As Professionals we CAN NOT, be attached to anything, Always there is something better in five or ten years, sometimes even less. MSDN is good, because have almost all .net features covered, but codeproject have many articles from people that have gone more than basics, giving solutions and codes about problems of real life.
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
Wow, that is a lot of replies. This topic was even mentioned in the daily mail :omg: I think I can agree with most of you that both are useful and that one site may be more convenient at some times and the other at other times. Thanks everyone! I hope I can convince my employer of this too one day :)
It's an OO world.
-
not to mention that there are several very active CP members who are also Microsoft MVPs
Steve _________________ I C(++) therefore I am
I C Sharp, therefore I am!
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
I remember your background and the background behind the job. Obviously, I wouldn't quit at this stage. It's not easy to find an opportunity like you have, plus you just got that raise. Anyways, just take him off your mailing list, and add him back on when you start forwarding the articles you will soon start writing.
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming "Wow! What a Ride!" — Hunter S. Thompson
-
I remember your background and the background behind the job. Obviously, I wouldn't quit at this stage. It's not easy to find an opportunity like you have, plus you just got that raise. Anyways, just take him off your mailing list, and add him back on when you start forwarding the articles you will soon start writing.
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming "Wow! What a Ride!" — Hunter S. Thompson
Thanks, you are right! I was not planning on quitting my job, although it is quite tempting sometimes ;p And I actually already wrote an article, it's on the list for best VB article of the month februari. One of the reasons I wrote it is because I see so many wrong exception handling at my company. Though the only one who read it was a freelancer my company is currently hiring (and he liked it). My employers said "it was a nice article, but they already mastered the subject so they did not need to read it." I beg to differ though, the only person at our company who mastered exception handling is the freelancer! :laugh: But well, the very fact that I wrote that article on CP after only six months of programming experience is half of the proof that CP articles cannot be very good. The fact that it was nominated as best of VB feb 2011 (and is actually getting quite some votes) is the other half of the proof... According to my employer of course :) And I apologize for the self-promotion of my article :^)
It's an OO world.
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
Well.....Personally I avoided MSDN like the plague until the redesign. Now if I want to look at the members of an object I hit up MSDN. FOR EVERYTHING ELSE like learning how to use the object....it is first: search of code project if that doesn't work search Google if that doesn't work ask questions on code project. Humble Programmer
-
Hi all, I have been sending quite some emails with interesting Code Project articles to my co-workers and employers lately. One of my employers is an absolute Microsoft lover. Everything that Microsoft does is GOOD and everything else is good if Microsoft does it too. In fact, when I first told him about OOD and Design Patterns he said (somewhat angry) that "I read some (Code Project) articles and now I thought I knew everything, but he had never seen Microsoft do it so he did not believe me nor the articles I read." I think he was quite shocked when he found out that Microsoft uses many OOD principles and Design Patterns :laugh: Anyway, I send him those emails and he walks into my office saying "well, that is nice, all those articles about this and that, but they are not from Microsoft, anyone could have written them." So I try to tell him that the people here at The Code Project are also professionals and are at least as good as the people over at MSDN. But he will not believe that articles that are written here can be really very good and helpful. Basically, to follow his line of thought, the people here write 'nice articles about some spare time hobby stuff' while MSDN writes really good and professional articles that provide Microsoft best practices etc. etc. Clearly, I do not agree with him! :-D I have read quite some Code Project articles and I find them generally easy to understand, many provide good test projects, and at the end I almost always feel like I have learned something valuable. So how much better (if at all) do you think MSDN (blogs in particular) really is? And how much value can we put in Code Project Articles? Just thought I'd ask the community directly (although results may be opposite when asked on MSDN) :laugh:
It's an OO world.
Just cobble together a small (non-working - as usual) sample app from bits of MSDN sample code - email it to him and ask for his help debugging it! That'l learn 'im! ;-)
