10,000 Foot Developer

In the last few years of this tentative economy some of us have decided to “hunker down” and take FTEships.  Others of us got laid off and went back to consulting.  Some of us started companies, some of us stopped companies.

Myself, I’ve been a consultant/contractor most of my career.  Also, I have been an FTE twice for product companies I truly believe in.

Anyway.  What exactly do I think of when I think Consultant (= Contractor for my use) versus and FTE?  It’s very simple to me:

FTE

1. Primary Focus:  the business (i.e. manufacturing) but not necessarily the craft (i.e. developer).
2. Is on a tract for usually management, maybe architect.  Become better at the business.
3. Feeling of “job security.”
4. More easily obtained benefits packages.
5. Lower pay for more hours.
6. Usually educated through the workplace.

Consultant

1. Primary Focus:  the craft/profession of developing.
2. Tract is usually more knowledge or leadership roles on projects.  Become a better developer.
3. Accepts risk of short-term project employment.
4. Usually takes care of own benefits.
5. Better pay for hours.
6. Usually self educated.

So there you have it.  The experience in the two realms produces two different types of developers.  Probably a myriad of inputs cause a developer to choose on path over the other.  From my experience and discussion with people it kind of boils down to this:

• People who need to feel secure become FTE’s.
• People who want higher pay at greater risk become Consultants.
• People who need new things and experiences become Consultants.
• People with long-term business objectives become FTE’s.
• Many times I find Consultants to be more motivated after hours to work on new technology and solutions.
• I find that more FTE’s want a life balance and a J-O-B job, which is a good thing too.

Now, a dirty little secret in the development world is that 90% of the time you don’t even talk about what the actual “business” of the applications you are working on might even be.  Most apps are a domain, garbage in and out, and screens designed by God knows who.  You are just a brick layer.  Will the building be a tire store, or a puppy mill?  Don’t know.  But I can lay the bricks.

The Bias Point

My personal bias point, and why I hesitate to become an FTE, is that it really requires a commitment to the business goal that forsakes the profession of coding.  Its almost a conflict of interest.  I find it curious that FTEships are even offered out front — except that they probably save money due to the weird and unresolvable “pay less for an FTE than a Consultant” paradox that has all of us scratching our heads.  The craftsmanship all places are seeking comes from within the individual, not a Director “demanding” a person become a craftsman.  Many times the FTEship is a throat collar to those types.

So I have only this advice:  if you believe in the product like a crazy man, or need a steady job, certainly become an FTE.  If you are dedicated to your craft, stay a consultant.  Some places afford the best of both but its rare.