Showing posts with label Career. Show all posts
Showing posts with label Career. Show all posts

Monday, July 14, 2008

What I did on My Summer Vacation

So it's not so much did as still doing but here's just a little update on what I'm up to at the moment, it's quite a bit.

Moving

moving Many of you already know this but I am in the process of selling my house and moving out of Ohio.  It is with mixed feelings that I do this as I have really come to love the emerging sense of community in the Cleveland development arena and the help we've had in building it from the twitter tribe.  On the other hand I'm taking this opportunity to move to anywhere I want, anywhere at all. 

I've been searching for a specific type of company for the last several months and finally decided on one that I feel is a perfect for for me at the moment.  I'm not going to say who yet, I don't want to jinx it, but it's a great web firm out of Seattle and they are flying me out for an in-person interview in a week or two.  I've already had a couple phone conversations with them as well as did a "home work" coding assignment.  So far it would seem like they like what they see, I know I do.  This is a great chance to be a full time Silverlight developer, and I'm more than a little excited at the prospect.

As part of this process we're also selling our house.  If you've ever sold a house before you know how much work it is getting and keeping everything perfect.  It's not a great market to be selling a house but we're optimistic that we'll get an offer soon.  We hope so anyway.

Writing

campbell_cover150 The writing on Silverlight 2 in Action is still ongoing.  I now see how much effort goes into the writing of a book.  There is probably a hour of research and coding for every five minutes of actual writing.  We are waiting until the release candidate comes out to finalize everything but I still have a ton of work to do even before that.  It's all worth it though.

It is known among people that teach or present that committing to do one of those actions is a good way to learn a technology.  I would argue that writing a book is even better.  You have to ensure that you know the material good enough to stand up to the criticism of peers, and trust me, we can criticize quite well.

Speaking

microsoft_silverlight_c Remember a minute ago when I said that presenting is a good way to learn a new technology?  Well, watching a presentation can be a good introduction as well, so come watch me talk.  I'll be the speaker at the August 12th meeting of the Cleveland .NET SIG.

Here's my abstract for the talk: Now that most people know that Silverlight can do fancy animations and play videos, lets look at how to make it do some real work.  In this presentation we will demonstrate connecting to web services, using returned data, binding data to controls and discuss some limitations Silverlight currently has.  And of course, since it's Silverlight, we'll try to make it look good in the process.

Coding

stacked_small_slbc_08 Hopefully you have all heard about the Silverlight Control Builder Contest by now but if not, head over there and read up on it now.  Basically, you build a templateable custom control, submit it to the contest, and win prizes.  Well, you can try to win prizes anyway, a whole bunch of other people will be entering as well.  The prizes are getting better and better and include books, software, gift certificates and more.  Wait a second, the more people that enter the less my chances of winning.... Never mind, don't enter :).

Thursday, June 5, 2008

How I got started in software development

So a twitter friend, Michael Eaton, started something that sounds like fun, and before I could get my answers posted a few others have as well.  So here it is, the Reader's Digest version of how I became a programmer.  Please post your own answers as well, this is a fun way to get to know each other.

How old were you when you started programming?

I think I was about 13 when my dad bought a TRS-80 Model III.  That awesome machine had dual 5 1/4 floppy drives, 48k (yup, 48k) of RAM and no hard drive.  I learned BASIC so I could program simple little animations and things.  The only problem was that if you forgot to boot from a floppy, the drives weren't initialized and you would have no way to save the tiny program you just spent hours coding.  I don't miss those days.

How did you get started in programming?

I don't know, maybe I was always a big dork? :).  I learned it as a teenager since it was the newest thing around, I think that even at that age and time (would have been around 1984) I knew that computers were going to be big. 

In college though I spent the first couple years as a History major, not taking a single programming class.  I did have a laptop though, which was unusual in 1995, and do simple desktop publishing and stuff for friends at the coffee shop.  Finally after the 100th person asked me if I were a computer science major I realized that maybe I should be.

What was your first language?

That would be BASIC, not QuickBasic or Visual Basic but plain old BASIC.

What was the first real program you wrote?

The earliest real program I can remember was a phone number database built using VBA on top of Access.  It was for a small college where I was doing tech support and started as a way for the switchboard operator to have quicker access to find the correct numbers.  Eventually I even built a web interface for it and added it to the school intranet (which also didn't exist before that).

What languages have you used since you started programming?

Lets see (I'll be generous in my definition of language to make the list longer :) )

  • Basic
  • VB
  • C++
  • Java
  • HTML
  • JavaScript
  • VBScript
  • BHTML (Who out there know where this comes from?)
  • XML
  • C#
  • XAML
  • ANSI SQL
  • T-SQL
  • PL/SQL

I know I'm forgetting some but that should be most of it.  I know that some of those aren't 'real' languages, but they seemed to fit for this list.

What was your first professional programming gig?

At the college I mentioned above I ended up doing quite a bit of programming of little utilities and the school website but I was never officially a programmer.  It wasn't until 1999 and I was hired by a web design/consulting company called Mozes Cleveland & Company.  That company grew like mad, had a ton of clients and promptly went out of business in the summer of 2001, like so many other companies of it's type.  I still think fondly of those days, they were fun.

If you knew then what you know now, would you have started programming?

YES!  Six months ago I don't know if I would have had the same answer but two things have really rekindled my programming spirit: Community & Silverlight.

If there is one thing you learned along the way that you would tell new developers, what would it be?

Never be satisfied.  Always work actively to improve yourself and your code.  Never consider a project complete until your manager tells you to stop, it can always be made better.  Never stop learning, complacency is what lets you get passed over and allows boredom to set in.

What's the most fun you've ever had ... programming?

I actually already wrote about this one in a old post.  Basically being sent to the Netherlands, working on a truly international team and writing some cool code, nothing else has come close... yet.

Monday, March 10, 2008

How Dinosaur Web Developers Can Regain Their Shine: Step 3

Rebrand Yourself

This one some people won't agree with but with new web technologies coming so fast and each having such potential, I think it's time to specialize.  I'm not advocating ignoring the other facets of our field, just picking one and knowing it inside and out, becoming an expert in a single field of study.

There are many options:

  • Web Standards (Don't just say CSS)
  • AJAX
  • Silverlight
  • Data Access (Linq, ADO, SQL 2008, etc.)
  • Web Services
  • ASP.NET MVC

That list is not even close to complete and is focused on MS technologies but you can get an example from it on how many different ways you can specialize.  I think we should all have a basic understanding of all of these technologies, but I also think we should find one technology that we really get into and specialize in it. 

Pick something that excites you.  Something that you can really get into so deeply that it rubs off on others.  Learn this technology so deeply that your peers regard you as a true expert in it.

I know this post is short and probably incoherent but better content will be coming soon.  Hopefully.

Friday, February 22, 2008

Poll: What is most important to you in a job?

The recent rash of people changing jobs has really made me think about reasons to switch jobs and about what makes a job worth the switch. 

So I would love to hear from people what they desire in a job.  So I'm going to throw out some items that are desirable in a job and why don't people rank them as to what they want/desire.

  • Interesting project(s)
  • Good co-workers (Talented)
  • Good co-workers (Likeable)
  • Good environment (City/Region)
  • Good environment (Office)
  • Cutting edge technology
  • Difficulty of project
  • Company size (Big)
  • Company size (Small)
  • Variety
  • Salary

I've changed jobs for a lot of these reasons but here is a crack at my personal rankings.  My personal rankings will change from one moment to the next btw.

  1. Interesting project(s)
  2. Good co-workers (Likeable)
  3. Difficulty of project
  4. Cutting edge technology
  5. Variety
  6. Salary
  7. Good co-workers (Talented)
  8. Good environment (Office)

I also believe that any of these can be so good or so bad that it sways the rest of the list.  For instance, if the project is boring but the difficulty and co-workers are high, it still might make the cut (and in fact has).  Also, none of this is set in stone, numerous things can sway a job for good or for bad, I'm just trying to add some science to this chaotic habit of changing jobs. 

So let me hear your thoughts.  Feel free to add as much as you want to these items also.  Or use something completely different, I'm just curious.

Tuesday, February 19, 2008

How Dinosaur Web Developers Can Regain Their Shine: Step 2

Get Involved.

That's it. Step two is just to get involved.

Ok, there's a little more to it than that, it takes a commitment to stay involved. But luckily, just being involved helps you to stay involved, more on that in a second.

In-Person Events

User groups (UG), special interest groups (SIG) and conferences large and small are wonderful ways to learn new information than you would normally get through your normal 8-5 job. The Cleveland area has a bunch of disconnected user groups that cover many areas of web (and other) technologies. The Greater Cleveland PC User Group (GCPCUG) is an umbrella organization of which many smaller, more focused groups are members. It is a good starting place to find what you are looking for. Not all groups are part of it though which can make finding them difficult at times.

A few groups to note are:

There are also events thrown by some of the large companies like Microsoft. Being a MS focused developer myself the events I'm most familiar with are events like Arcready, DevCares and MSDN Events but there are bound to be others for other technologies / companies. Some larger organizations also have their own internal groups that do the same things. I helped start an ASP.NET user group at the Cleveland Clinic and I know that Progressive has one as well, National City was starting an architect's book club when I was there last.

UPDATE: I forgot to mention a Google group set up to help find events: NEODevEvents

Online Tools

As much as social networking is a Web 2.0 buzzword (or should that be buzzphrase) it is truly a good way to meet and communicate with people of similar interests. Just like with Web Standards I can't say that I am great at this, or know everywhere to 'hang out' but I can say that just from the last couple of months I've already begun to know a wide range of developers, architects, managers and others in the field that have similar thoughts and ideas to my own. These people are at companies large and small are young and old, are experienced and beginners. What they all share though is a passion for what they do. And it's contagious. This is the part that helps keep you involved, everyone inspires/motivates each other. And you do it without trying.

My favorite at the moment is twitter. Everyone in the tech field it seems uses twitter, from all fields really but I only care about tech. When you first hear twitter described your (at least my) first thought is "what's the big deal?" and for the first week or two you still fail to see the allure. But then once you've found a group that's like yourself, then it all changes. Then when twitter is down (which unfortunately happens frequently) you will seem lost. One odd thing about twitter is that opposed to IM and similar things twitter does not seem to negatively affect productivity. It could be due to the asynchronous nature of it you don't need to reply right away, or even read things right away. Not only is the non-time sensitive nature of twitter capable it seems to be just the way things are done, it's very common to replay or receive a reply hours or even days after your message. One last thing about twitter that makes it unique is that you don't actually have to know someone to interact with them. You can follow nearly anyone you want to and see their messages. They don't see yours in normal conversation unless they are following you too but if you reply to them, they will see your post anyway. This lets unknown developers in Ohio respond and interact with 'big' names from around the world.

A few other relevant networking sites:

Collaboration & Networking

What I've talked about are of course not the only ways to get involved, it's just a starting point. Another good thing to do is to participate in an open source project at sourceforge or codeplex. There are also professional organizations like ACM or IEEE among others. If you have another way you like to be involved pass it along, I'd love to hear about it.

The best things about being involved locally and online are that you are constantly exposed to new technologies and people that are passionate about using them. Typically the more active members of these groups spend time experimenting and learning new technologies long before they are widely used and as such are great contacts for when you too are trying to learn those same things. Getting involved with other people passionate about technology is by far the best way to keep yourself motivated. Just be careful not to spend so much time that the WAF (or HAF I suppose) dips too low.

Disclaimer: Due to severe neck pain I'm currently taking a few meds that have um, dulled my senses so if this is less than legible that's why :)

Wednesday, January 23, 2008

I WILL be an MVP

Now maybe this isn't a practical goal but I truly think it is possible for me to be named a Microsoft MVP in ASP.NET when they are announced in December.

Wanna know how I'm going to do it?

Basically I'm doing the same things that I've been preaching that we all need to do:

  • Learn the newest stuff
  • Evangelize to peers
  • Be active in the community (online and in person)
  • Make yourself known
  • BE AN EXPERT

So that last one is the hardest, but I'll talk about that a little later. First I'm learning the newest stuff and catching up on stuff I've fallen behind in. For me this means getting up to date on dynamic positioning, learning ASP.NET AJAX and finding the limitations with Silverlight and trying to find ways to get around them. It means not just reading about these things online but also watching videos, reading books, building sample apps on my own time and also trying to convince my employer to use them in production. I'm well into this phase already, the only trick is going to be able to keep up the momentum.

Evangelizing to peers is something I've always done so that's not a hard one for me. When there is something I'm passionate about everyone around me knows it. I tend to talk a lot when I find something cool and want everyone else to see how cool it is.

Being active in the community is also not a hard one but takes a time commitment. For the last couple of week I've been all over the forums at asp.net answering questions about asp.net left and right. I've also learned a few things as well which is a great thing about forums, you may have a solution but someone else may know of a cleaner / cooler / more elegant solution. The in person community is a little harder just because of the time / distance issue. This is also something that I've done in the past so I need to get back at it. I had a contract gig at the Cleveland Clinic that was only a few months long but still was able to get an internal ASP.NET monthly lunch discussion going which had pretty good turnout. I also try to get to the .NET SIG at the MS office but that's about it at the moment. I really need to offer to speak at one of these groups to really push me to get involved more.

Making myself known kind of comes along for the ride if you do the "be active" item from above. You you are active enough and vocal enough then people will notice. You just need to make sure they notice you for your wisdom and insight instead of for your ignorance and stupidity.

Be an expert. This one is hard to quantify. What makes a person an expert? Is it a certification? Nope, I've seen plenty of people disprove that. What about an advanced degree? Again nope, that may give you academic knowledge but I don't think that makes anyone an expert. Personally I think you are an expert when someone else calls you one. Preferably numerous people. You can't name yourself an expert and expect it to mean anything unless you have people that truly think that you are one. Some people call me an expert in .NET web development already but I don't think I'm there yet. I will be before this year is up though, because I WILL BE AN MVP.

Friday, January 18, 2008

Web Development Is Dead! Long Live Web Development!

Everything is about to change.

Some would say it already has, I would argue that the changes that have taken place in our industry during the last 5-10 years are nothing compared to what's going to be happening over the coming few.

New technologies combined with better tools are making the kinds of things possible that we laughed at when sales people / clients suggested them a few years ago. Silverlight, Flex, AJAX, Web Services, Ruby are just a few of the technologies that are enabling this change. Tools like the Expression Blend / VS 2008 combination allow unprecedented cooperation between designers and developers. Now we CAN do what the designers want us to do, if they can draw it, we can build it.

The time of the RIA is fast approaching. The seventh principle of Web 2.0 as written by Tim O'Reilly in 2005 requires "Rich User Experiences". Regardless of what you think of Tim O'Reilly, Web 2.0 or 'cool' websites, it's happening now. Even the corporate world is noticing. I work for a major Japanese electronics company building a mundane management application and a couple months ago a senior executive mentioned Web 2.0 and mashups. This is not going to be a passing phase.

I know there have been some RIAs created today but they are far from mainstream. Nearly prediction list for 2008 by prominent web development bloggers name 2008 as the year of the RIA. I agree. I think it is time for 'classic' web developers to learn and embrace the new technologies or risk becoming outdated. Those of us who were writing cutting edge apps in the first big Internet boom (1998-2000) risk becoming the online equivalent of COBOL programmers unless we get off our butts and start learning again. While it's great that we know the intricacies of HTML, CSS, JavaScript and the .NET framework, now we need to learn XAML, JSON and some design skills.

Most importantly we need to learn how to think differently. All the rules we knew about what could and couldn't be done in a browser are being thrown out the window. Unless you want to be the one that is dismissed as 'stuck in the past' and be passed up but the young kids with all the cool ideas (exactly who we were ten years ago) we need to learn the new capabilities and learn them fast. Just think about it this way, how do YOU feel about COBOL programmers?

Web Development Is Dead! Long Live Web Development!

Tuesday, January 15, 2008

Dream Job: Myth or Reality

If any of you are like me you've changed jobs a few times. Maybe more than a few times. Sometimes this was not our choice (read, web company circa 2001), most of the time however job moves are in part, motivated by a search for the perfect job: The Dream Job.

There is definitely a problem with most good programmers I know that we get bored easily. As soon as we know everything there is to know about the site/product/industry we are currently in, we want something new. At first this is just an idle though and then over time it turns into a desire to 'right' things and you move on. This is why I've spent a lot of time as a contractor, it's easier to change jobs without hurt feelings and such.

But what I'm really writing about tonight is the 'Dream Job' that we think we lost out on at some point early in our careers. For most of us there have been times where we had to make a choice between two (or more) companies, each with their draw. We made our decision and hopefully were satisfied with it. But you always wonder about 'what could have been.' Or maybe you did work there and for some reason left it and always wish you were still working with those people or in that industry.

Have you ever gone back and looked at the company again? I have. A couple of times in fact.

For me, there was this company I worked for back in the Internet heyday, times were good. I traveled the world writing cutting edge code and strategizing cool solutions for clients. We had writers, designers, information architects, programmers and all the other things a company like that should have. Times were good.

Then came the downturn and the owners decided it was a good time to split. No more company. No more good times. I always dreamed of that job, that perfect job which was no longer. I found new work quickly but it wasn't the same. I stagnated. No more cutting edge. No more cool.

Eventually I left this gig for a new one, in search of the perfect job, as always. This job was much better technically. It definitely honed my skill from a technical perspective. Real experience in OO programming and some of the intricacies of the .NET framework. But it still was lacking in that one criteria that the perfect job must have: cool. After a while I left this job too, still looking. After a couple of other gigs though I came back. What this job lacked in cool it made up for in tech.

And now the dance begins again. An old co-worker, now a partner in a new incarnation of that old dream job, called me the other day to basically offer me a job. We talked about this a couple years ago as well and while the company had cool it had little to no tech. This time though things seem to be different. I went and talked to them again and found that they are doing some OO development, some multi-application integration, some SharePoint work, some e-commerce work. And it still is cool.

I would be writing specs, managing off-shore development, writing code, architecting solutions; all good stuff. I would be encouraged to stay cutting edge. I would get to help steer the technical face of the company. And it is cool.

Would this count as a dream job? Would I burn bridges if I left the good job for the possible dream job? I still need to talk to both the new people and the old people but this may be a tough decision. Very tough.

Stay tuned, I'm not sure what I'm going to do.

UPDATE: Well, it may be an easy decision after all. I'm expensive.

Wednesday, January 9, 2008

We should all be Evangelists

Wouldn't it be great if we were all evangelists for the technologies we care about?  Going around telling other technical types about the benefits of the tech and the 'how to' you need to get started.  To be the person that people come to with questions about technology X.

Well why aren't we?  We should be.  I will be.

I'm not saying that we all quit our day jobs and try to get hired on by Microsoft or Sun or whomever and do it for a living, what I'm saying is what is stopping us all from staying up on the most current aspects of something we feel is cool and 'preaching' those items to other people.  If you don't try to know everything about everything then it doesn't take a huge time commitment to be an expert on some aspect of technology. 

So how do you do it?  I've got a few suggestions.

  • Read relevant books.  All technologies get books published about them as soon as the tech is announced.  Many times before platform / tool / technology has been released.
  • Subscribe to and read relevant blogs.  It's amazing how much information you can gain just by reading the blogs of the technology makers and implementers.  There are a ton of blogs out there dealing with pretty much every topic you can think of.
  • Play with it.  Download the betas and trial editions and work through samples.  Look at open source projects on the topic.  The best way for most people to learn something is by using it, so do it.
  • Attend events.  Microsoft and most other technology makers sponsor user groups, SIGs, technology overviews and other types of events where you can see real people talking about the newest technology.  Many of these events are small enough to ask relevant questions and talk one on one with the experts.
  • Speak Up.  Whenever there is a conversation about your area of concentration, let your voice be heard.  No one will no you are an expert if you don't let them hear you talk about it.  This can happen in person or in online communities, wherever you feel comfortable.  But remember, if you hope to gain respect at your place of employment you need to speak up in person sometimes.

This list is far from complete but it's a start.  Add to it, do only a subset, whatever, just do something. 

So get out there.  Be an Evangelist and let people know it!

Friday, January 4, 2008

Certification - Is it worth it? - Part 3

I've done some research on what others feel about Microsoft certifications. Here are the results.

First is the perspective of a development manager:

I spoke with a former manager of mine who has been hiring developers for a number of years, some good, some not so good, and asked his feelings on this topic. He was very much in favor of certifications (he does not have one that I know of btw). Basically in his opinion certifications tell him two things that increase the chances that the candidate will get an interview.

1st: The candidate probably has the initiative and drive to achieve this for himself (or herself). He stated what we all know which is that no matter what most employers say at hiring time, they will not give you time to study nor will they provide an incentive strong enough to make it "worth your while" to achieve a certification with great personal effort.

2nd: It does indicate a certain level of knowledge in the candidate. He was quick to point out that knowledge and competency are not the same thing as he and I both know a former hire that had a certification and was less than stellar.

Next we have someone who has managed to set himself apart:

A former Microsoft consultant, Patrick Santry of wwwcoder.com, last year posted his advice on how to get ahead in this field which had some decent information (read: his thoughts are similar to mine). This is more geared toward the consultant role but I think it is relevant for most people in our field. Included was a bulleted task list, notice the first item:


  • Get certified! You have to start somewhere, and getting certified helps provide some credibility for you on a technology area. [bold added for emphasis]
  • Never turn down an opportunity; you never know where it will lead.
  • Always follow up and build from your experience. If you write a book, then promote yourself as an expert.
  • Participate online. Build a website, be active in the forums, and get your name out there. Opportunities will arise just from being out there.
  • Create a career plan. You need to set goals and objectives of where you want to be five, or ten years down the road and try to stay on the path to those goals.
  • Stay current! Probably the hardest aspect of being a consultant, but necessary.
  • Work with your local Microsoft reps. Go to the presentations, and free training opportunities in your area. This helps build your knowledge and your network.
  • Support the local user group community. If you don’t have a SIG locally, start one. Contact INETA for more information about your area.
  • Build the network. Contact every user group, or organization to see if you can promote your book, presentation, or whatever it is you want yourself to be recognized with.
Finally, we have the words of someone who has been in the field longer than some of us have been alive. I won't call him out by name but my co-workers should know who he is.

While he worked at a consulting company a few years ago, this gentleman was asked to get his certification by the company he worked for. He was told that this was mostly so the company could retain partner status with Microsoft (I too have been asked for this reason at a previous position). At first he was excited about the supposed benefits of certification including access to software, exclusive messageboards and other items.

So he studied and tested and eventually achieved his NT certification (see, I told you he was older). He took the test seriously as well, instead of just memorizing the information he truly understood the WHY of things, not just the HOW. Still, he was disappointed. The access to 'exclusive' materials was underwhelming and the messageboards were full of people complaining about how even after achieving certification they still couldn't find a job.

In the end he was glad he went through the process but was quick to caution that the end results may not be what you dream of them to be.


So basically all three of these perspectives back up what I was already thinking. Now I'm sure if you dig into it you can find opinions that directly contradict these but this at least gives me confidence that what I am thinking is valid. I probably won't post any more in this series until I have achieved something, I really need to stop typing and get to studying... I mean working :).

What do you want to be when you grow up? - Response

In response to Dave's post on this topic, I thought I would jot down a few of my own thoughts as well.

I have also struggled with this same question for several years and have even made some bold moves in response to what I 'thought' I wanted to do. I've bought self-help books on the topic, signed up for college classes and created a reputation among my friends as someone who changes their career path monthly. One month I'm going into Aerospace engineering, the next it's GIS, followed closely by architect, robotic engineer, landscape designer and then as the frustration increases I land on ditch digger. Maybe I should have just stayed as an Infantryman, at least there the goal is clear (point gun that way and shoot).

In the end (well, currently at least) I think that radical changes (like switching fields entirely) is probably not something I want to do, mostly due to the time involved in getting qualified in the new field as well as the time I have invested in this one. So what I am pursuing at the moment (sure to change in a month), is to figure out how to move to the next level in the field I am in currently (which happens to be creating web applications for those joining late) and acting on those items. Maybe that way I can at least feel satisfied in my career.

I'll be posting shortly about how I'm trying to advance my career from average ho-hum developer to super programmer extraordinaire, or at least to happy respected developer.

Thursday, January 3, 2008

Certification - Is it worth it? - Part 2

Since my last post on this topic I have received mixed feedback from various people. In general the responses tend to vary based on the person's expectations.

If someones expectation was that by having a certification they would magically get a better, higher paying job, then they were usually disappointed and don't feel that certifications are worth it. On the other hand, if a person already had knowledge and experience and achieved a certification more for their own professional growth (with no pre-conceived notions of salary increases), they were happy with the results.

I don't have a certification yet so I can't speak to the aftereffects of achieving it but I can say that during my studying I'm learning that my 'expert' knowledge of ASP.NET web development isn't as all-encompassing as I thought it was. I knew that I didn't know everything but there are things that I thought I knew pretty well where I'm learning new things. Methods and attributes on controls that I didn't know about but have had occasion to use.

So for me, even if my getting a certification doesn't translate directly to better job/pay, the increased knowledge will help me do my job better, which will make me more employable at a better rate and so on. Basically, I think achieving a certification is a good thing professionally.

Just do it.

Friday, December 21, 2007

Certification - Is it worth it?

For years I've toyed with the idea of getting a Microsoft certification. Usually I haven't actually done so because of time issues but also there has always been the question of "is it worth it". I know that ten years ago there was a huge problem with "Paper MCSEs", basically people who would go to brain dump sites and memorize the answers, take the test and get a ton of certs in a short time.

My thought on this is that times have changed and the new generation of certifications is worth pursuing. Now, to be honest, much of my belief comes from reading Microsoft's own marketing materials. Personally though, I've decided to pursue the MCTS: .NET Framework 2.0 Web Applications on the way to the more advanced Professional Developer: Web Developer. In fact I'm working through the MS Press study material now.

My question to everyone out there though are several:

  • What are your thoughts and experiences with Microsoft certifications?
  • Do they help you get a job or are they just resume fodder that no one pays attention to?
  • In the process of studying for the exam do you expand your knowledge into areas you didn't know a lot about (This is what I'm finding)?

So hurry up and answer, my career may depend on it :)