It’s time for the compulsory end of the year post about everything that changed in my life. Instead of going too in depth on that front, I’d like to comment on what I think I’ve done this year to make me a better developer. I’d think of it as advice I’d love to have received myself.

Use an RSS Reader to get the News you Want

It’s important to get the information you want, without wasting too much time. Having the news at your fingertips is great, but it’s important to remove the feeds that are just wasting your time as well. You can always add those to Del.icio.us and grab them later without the feeds of course.

Use Subversion for everything you can

Getting a subversion setup in your home PC often isn’t worth it. You reformat every now and again, you wouldn’t be able to use it outside of your home and you have to do a lot of work to get it setup. There are plenty of Subversion servers out there cheap now though, and your webhost may even offer svn access, Dreamhost does for instance. Play around with SVN, get the basics of working with source control down, learn about tagging and branches and how to use them with deployment for even more benefit. Putting your personal code behind a private svn repository helps in case something happens, but just as importantly gives you some experience with it for when you really need it later. A few Eclipse plugins for subversion matured this year as well.

Embrace what you know, embrace what you don’t know

Chances are there’s a community around the development work you do. Find and and embrace what you love working on! But don’t close your mind to other languages, frameworks or methodologies or you’ll never benefit from them.

Don’t just read about your language of choice

Refining skill in your primary language is important, but there is a higher level than code where knowledge doesn’t rely on a specific language. Books like The Pragmatic Programmer, Code Complete and Peopleware can make you a better developer and better at managing regardless of what language you’re working with.

Read other peoples code

Reading code from other people at your workplace is important for a lot of reasons, but reading other professional code outside is a great way of learning. With Google Code Search and RiaForge it’s easy to find examples to learn from.

Embrace OpenID and Microformats

OpenID and MicroFormats will be making a big splash in the new year as their adoption rate grows. In the end it’s all dependent on the developer community whether or not these make it big or not though. If they can help you out, use them, if they can’t, support someone else who is.

Join the community!

In the Adobe community there are more ways than ever before to join the community. You can go to conferences like Frameworks Conference, CF Objective or CF United. You can start an open source project over at RiaForge or at Google Code. You can respond to questions on the many House of Fusion mailing lists.

The most important thing is just to take pride in what you do. If you don’t you won’t enjoy it as much, and chances are you’ll wish you were doing something else. Love what you do!

Model Glue Unity examples have been few and far between, mainly because it’s still in it’s first beta phase. It’s actively being changed, with Joe hinting at an early 2007 release for beta 2, and it’s recent Divorce from Reactor, but hard time finding code. There are at least two projects over at RiaForge using Unity though, CF Email Campaign and User Group Manager. If anyone knows of other Unity code examples, feel free to chime in!

About a year ago I was infatuated with Ruby on Rails, the Prototype Javascript library and just about any other cool css/js hot topics. I was reading everything I could get my hands on that was in the beginner to intermediate range. There was only one Rails book out at that time, Agile Development with Rails, and almost no Prototype support (well, there’s still not too much for Prototype unfortunately). The biggest help at that time were blogs like Encytemedia, ParticleTree, nano RAILS and Ordered List. Up until around this time, I hadn’t started reading blogs outside of my friends list at Livejournal, but Google Reader changed that!

So throughout all these great sites I noticed the trend of 9Rules affiliation, and although I didn’t dig into what it was at the time, it stuck with me. That was until one of these guys mentioned that 9Rules was allowing new submissions back in October. Now, throughout all the time when I was digging into the Rails community, I never saw much notice of Coldfusion. The 9 rules community, as well as a lot of the programming community just doesn’t see the many many Coldfusion bloggers that are out there. Doing a search on 9 Rules for Coldfusion, the only post that came up was one title Is Coldfusion Dead? (Note: I swear that’s what the title was; even it’s changed now, but I could be wrong). I chimed in of course, but one other comment stuck with me.

You guys are in your own little world of open-source/9rules love.

And it’s true! Not to put down anyone in the 9rules/open source/rails community, but as a note of just how far from the popular culture the Coldfusion blogosphere is. There are a LOT of coldfusion bloggers, just check out the Macromedia Weblogs List. If i had to give a turning point of when I went from being a regular Coldfusion programmer, to a more advanced one I’d say the interest started right there. I started reading all the Coldfusion feeds I could find, started removing Rails feeds from Google Reader and yes, starting this blog.

So with that said, I was happy to see my name on the last list of 9Rules entries for the year! Hopefully I can bring a little more exposure to Coldfusion and Flex to the rest of the programming world without getting too deep into the Coldfusion world where things stop making since to outsiders. It’s also very humbling to be a very small group of programming blogs on 9Rules which I held in such high regard.