ASP.Net MVC and LINQ Tutorials

I was running through several Asp.net MVC and LINQ tutorials when I ran into a problem; part of the code in the tutorial wouldn't compile. After an hour searching, I finally found the solution to the problem. This is fairly widespread, as far as I can tell.

This has occurred b/c these technologies were in beta and the tutorials were written then. Microsoft has made some changes to these frameworks, but some individuals have not made the effort to go back and update their tutorials (I don't mean this as a slam against these authors. There are plenty of reasons why these tutorials don't get updated.)

In an industry such as ours that is ever changing, we need tutorials to teach new technologies in a hands-on fashion. That's why I have started a wiki at

http:\\devtotorials.wikia.com

This is an ad supported site at the moment, but eventually this will be moved to another location once the site has a decent amount of traffic and content.

Staying Enthusiastic about Programming

I started in programming like many developers out there. I was a hobbyist as a kid. I picked up a book on BASIC as a kid and loved it. I enjoyed seeing something I wrote and created come to life on the monitor. It was because of this passion that I learned Computer Science at school, and this same passion kept me from directly pursuing a development job out of college. My reasoning at the time was that if I coded at work all day, it wold take all of the fun out of coding.

Sadly, I was right. Especially in the last six months, since I moved to a new project, this feeling has overwhelmed me.

The problem lies mostly within the project itself. There does not feel to be any guidance, project assignments made little sense, there were serious deficiencies with the database that I was not able to address, and there have been serious communication issues with one of the offshore offices. At times, I have really gotten the feeling that the US office and foreign office are competing, yet the metrics aren't fair. Sure, the foreign office I might have addressed more issues, but these were largely the easier issues and many of them had to be addressed multiple times as the first fix broke something else.

On top of all of this, I have had 5 different managers in 12 months. One of those transitions occurred without my knowledge. I actually sent my new manager an email asking him if I reported to him!

Through all of this, there is one way that I've found to recover the passion to code again; hang around others who are passionate about coding. The level of energy is amazing and has really allowed me to refocus on my craft again.

The what is easy, but how might be difficult. What if there is no one else at your company who shares your passion for coding?

One option is to attend a local developer group meeting. .Net and Java will often have user groups in major cities.

You can also try to find a local nerd dinner.

You can try to read some blogs of other passionate developers, but written text is poor at conveying emotions. The better electronic approach would be to listen to developer podcasts. I try to listen to Stackoverflow and Hanselminutes on a regular basis. Not only do I walk away from podcasts educated, but they are also motivating. (Unfortunately, I am now blocked from downloading them at work, so that in itself is demotivating.)

We can all lose our passion for our jobs, but engaging with others who still have that passion can help bring it back out in us.

Signs its time to find a new job

1.) There's no or few other developer who are passionate about what they do. This means they've all gone elsewhere.

2.) New policies and restrictions are placed on developers, hindering the work we do.

3.) A major contract falls through or a major client leaves.

4.) Reorganization or layoffs out of the blue. This could be a sign of things to come.