The Code Project vs. MSDN?
-
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
Very much so. The writing for code project is much better. Back in the early days, MSDN magazine had much more in depth articles with much more code examples to show. Now, they spend more time showing off their new (shiny) tools. Back then, it was more of a technical journal. Today, it is just a flashy magazine. Also, today, the price of paper to print the magazine articles is more expensive then web pages. Strange how certain companies dominate our thinking. Today, it is Microsoft. Back in the 80s, it was IBM. Corporate thinking was "If your hardware wasn't IBM (or IBM approved), then you could not program to it nor sell for it". But, until something better comes along, those of us in the Windows world will have Microsoft.
-
Make Searching Developers go Nuts.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
Agreed! Have you seen their help. Every Visual Studio after VC6, the help was pretty much useless. The examples were terrible to nonexistent. You really had to scratch your head on much of it, until Google came along. VC6 had excellent help with useful examples.
-
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 don't read too many MSDN articles. I do read MSDN documentation and I wince at the idea of finding what I am looking for in that pile of ... OK, after re-reading a passage about 5 times, half the time, I start to get what the idea they are trying to convey is. It is unfortunate that it is almost devoid of useful examples.
