Wha....This is what i was looking for long time ago.I always get a common question directly/indirectly which is somthing similar to below.Thanks to —J.T.

How does an average developer win fame and recognition as a guru on the programming scene?

To make a long story short, today there are literally millions of people who are targeting Windows when they sit down to code. Still, there's a lot of opportunity for widespread recognition. Every author in this magazine started small, with their first submission.

If you want to make a name for yourself in the world of programming, the first commandment is to know exactly what you're doing. Nothing will make people ignore you faster than if they can't trust your work. One thing you'll find in the community of programmers is that people can smell B.S. a mile away. Software itself is really nothing more than the end product of a bunch of thoughts put together, and if the software isn't sound, it's a sure sign that the underlying ideas aren't either.

The second commandment is to have an idea. This sounds simple, but it's the toughest thing to do. If you want to demonstrate a concept, it should be unique and it should fill a need. We see submissions all the time from people who want to show how to create a form or how to write a simple Web service—these ideas are well-trod by now.

Most great ideas are born of necessity. People have written RAW file viewers for their cameras, mobile blogging tools, and all sorts of power toys for Visual Studio. If you get something started, you don't even need to perfect it yourself; put it up in a shared workspace on gotdotnet.com or elsewhere, and invite others to add to the project you own.

The third commandment is that you must express yourself clearly, both through your writing and your code. A bad cover letter, with spelling and grammatical errors, severely limits an editor's confidence in the care you take in the rest of your work.

Finally, the fourth commandment is to keep your options open. A magazine is one place to get started, but if you join the expanding community of dev bloggers, you won't have to wait for acceptance before you start sharing your ideas.

Think of your favorite source of development information. Is it a magazine? A blog? A column? A book? A chat list? What do you get from this source that's unique? There's no need to reinvent the wheel when you're getting started. If you have something to share, do it through your favorite source. Even if you're not an MVP, you can offer your expertise, creativity, and guidance.

For More ...

Cheers..

Suresh Behera