How to Become a Good C# Programmer, Part 9

This is part 9 in my 10-part series on How to Become a Good C# Developer. If you need to reference the full list of steps to take to be a good C# programmer, you can find those here.

• Part 1 - Overview of a System for Becoming a Good C# Programmer
• Part 2 - Steps 1 and 2: Picking a Language and Picking a Pet Project
• Part 3 - Steps 3 and 4: Picking a Book or Class to Get Started
• Part 4 - Step 5: Implementing Your Pet Project
• Part 5 - Step 6: Minimizing the Trough of Disillusionment
• Part 6 - Steps 7 and 8: Finish your Book/Class and Start a New One
• Part 7 - Steps 9 and 10: Begin Answering Questions and Pick a New Project
• Part 8 - Steps 11 and 12: Review more apps and Start Contributing!
• Part 9 - Steps 13 and 14: Write a few articles and the Bonus Step
• Part 10 - Next Steps and What Does It Take to Be a Great Programmer?
  

Step 13: Write a few articles on subjects you enjoy

Remember back in Step 9 when I suggested that you start answering other people's forum questions because it helps you learn? Well this is similar: writing an article about a difficult topic will force you to spend a good deal of time on areas that you thought you knew but, upon delving into them, you realize that you've only scratched the surface. Pick topics that you like - don't worry if the topics have already been covered by others; your goal is to help yourself learn to become a good C# programmer, right? So write articles that force you to learn and that force you to simplify complex topics.

"Any fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction." - Albert Einstein

You want to do one thing: make complex topics seem simple to the reader. Why? Because if you can do that, you have shown you have a deep understanding of the topic. Another great quote is from one of my musical heros:

"Making the simple complex is commonplace; making the complicated simple, awesomely simple, that's creativity." - Charles Mingus

Other Reasons to Write Articles

At this point in your career, you likely either have a decent programming job or are eligible to get one. If you want to move up the career ladder as quickly as possible, you need great communication skills. Just like being a good C# programmer takes practice, being a good author (or trainer) takes practice. Writing comes natural to some but is difficult for others. Here's the truth: developers who have "the knack" for creating readable documentation, succinct emails, and who can empathize with their audience will generally move up the career ladder faster than those who can't. By forcing yourself to write articles, you'll not only learn things but you'll learn how to communicate complex topics quickly and succinctly - and that will pay dividends over your entire career.

Writing articles also gives you a public persona which can be a positive thing provided that your articles are quality. Potential employers will do a quick Google search (ahem - or a Bing search) to see what you've written, what you've posted online, and generally to see what they can find out about you. Make it easy: provide them with links to your articles in your resume. I've seen people who go so far as to put their forum user names in their resumes so that potential employers can see their participation!

Where to Publish Your Articles

I suppose "articles" is a bit of an officious word - these could be blog posts if you wish. You have several options:

• You can create your own blog and host the articles there (employers *love* this)
• You can find popular blog aggregation sites and post them there
• You might even be able to post them here (just ask us over at LearnItFirst)
• You could publish them in printed magazines.

Personally I favor creating my own blog and posting things there. I've always been that way although I'm not sure its the best thing for you. Check out some of the popular blog sites and see what it takes to have your blog hosted by them. You'll give up certain publishing rights yet you'll be given an audience (and that's important).

Step 14: The Bonus Step!

If you're still wanting to know what it takes to be a good C# programmer, the final bit of advice I can offer is to start your own business! Whether you want to sell commercial software, have an advertiser-supported ASP.NET website, or do consulting, having your own business is a great way to get better. It forces you to listen to your users - if you don't, they won't pay you. And you don't have to start full-time; most developers have side projects in addition to their day job. 

So start your own business - if you've followed the previous thirteen steps I outlined, you've got enough experience to design apps and to help others. You likely don't have the experience to be considered a "great" programmer but hopefully that will come with time for you!

Next up

Let's take a look at Part 10 of 10! Of course, you are welcome to go ahead and dive into my C# video tutorials at any time!

Article Index:

• Part 1 - Overview of a System for Becoming a Good C# Programmer
  
• Part 2 - Steps 1 and 2: Picking a Language and Picking a Pet Project
  
• Part 3 - Steps 3 and 4: Picking a Book or Class to Get Started
  
• Part 4 - Step 5: Implementing Your Pet Project
  
• Part 5 - Step 6: Minimizing the Trough of Disillusionment
  
• Part 6 - Steps 7 and 8: Finish your Book/Class and Start a New One
  
• Part 7 - Steps 9 and 10: Begin Answering Questions and Pick a New Project
  
• Part 8 - Steps 11 and 12: Review more apps and Start Contributing!
  
• Part 9 - Steps 13 and 14: Write a few articles and the Bonus Step
• Part 10 - Next Steps and What Does It Take to Be a Great C# Programmer?