I'm just going to post one or two cool ones, and if you want to see more, just click here.

RULE 1:    There is ALWAYS a caveat!

I don't know how many times I stated this rule for Embedded Linux systems, but I've made a believer out of many people with this rule.  Now, don't take this the wrong way.  I am NOT discouraging the acceptance, advancement, and proliferation of Linux as an Embedded System.  In fact, I wholeheartedly encourage it.  But you have to know what you are getting into.

Some of the many promises I've heard (and made when I was more naieve) in regards to Embedded Linux:

1.) "Well, all you have to do is....."

This is the FIRST phrase you need to perk up on.  Unless you are working with standard x86(see, already a caveat), this is hardly ever a true statement.  As soon as you hear it, multiply the expected effort by 3 and you'll have a good estimate of the time required.  Why?  Well, lets just go through some standard processors:

ARM7: Oh look, usually only two serial ports (one used for console), and then you have to figure out if the other is really a full serial port or a 3-wire.

ARM9: Well, it's exactly like the ARM7...  Well, except for the boot procedure and having more serial ports

PPCXXX: Now these are really fun.  A 44X series is different from a 40X, but most of the Linux code is written for a 4XX series.  Oh, and don't forget about all those nice interfaces that actually require PHYs for operation.  You mean I forgot about the GPIO busses as well?  AND the ethernet MAC interfaces?  Well, why don't we just move to an 8XX series?  OHHHH!  Well hell, what do we do?

x86: What?  You mean we have to worry about north/south bridges now too?  Really?  The solid-state memory is an issue to?  Oh, lets just switch to a newer kernel and it will fix all that.  What do you mean the USB doesn't work anymore?!?!?

2.) Well, someone's done it before... it will only take a few minutes to google something up

AHHHHHHHHH!   Unless the person who uttered this ACTUALLY has seen something on the Internet pertaining to the discussion at hand, this person is putting up a smoke screen of  BS to the Nth degree.  Most likely, they have no idea what to do and are just expecting someone else to have fixed their problem already.

3.) "Yeah, I had a little trouble with 'X', but I'll have it fixed this afternoon..."

!!DANGER!! Will Robertson !!DANGER!! This person has probably had a major compilation error and has no clue about the solution.  They are likely searching google at a rate that would make a TSA agent blush.  Yes, they will likely find a solution, but multiply their expected afternoon by seven and you'll have a close estimate.

Yes, I'm exagerating this a bit.  But not much.  These are all issues I've run into in the last year.  Why am I telling you this if I am so much in favor of Linux?  Simply put... you need to know what you're getting into so you can plan your projects accordingly.  Linux is a WONDERFUL operating system... in general.  However, to make a sucessful product from it, you will face many challenges.... that your engineers will love (if they like Linux...  DOH!  ANOTHER caveat).  But don't let the cool, gee-wiz factor get in the way of realistic expectations.

Well, its that time of year again.  No, not the getting sick part(although that, too, did occur).  I turned 30.  Wow.... its hard to believe that I'm really 30 years old.  But then again, Duran Duran is now considered classic rock!  I used to think that 30 was ollllllllllld, but now that I am 30, what has really changed in the last 10 years?

• My hair is now a healthy salt&pepper black. (at least its ture silver and not grey hair)
• I have a wonderful Wife
• I have a lovely daughter who is 4 ("and a half" I get reminded often)
• My job is interesting and challenging
• I have a house, a car, and a lawn to mow that are all my own.

All in all, I think that my life has just grown, and in a good way.  Its a nice feeling.  Now what hasn't changed you might ask?

• I'm a geek (going to be REALLY hard to ever get rid of that...not that that I want to!)
• I am eaily amused
• I make really bad puns
• I still spell phonetically (my mother still threatens to get me a dictionary on reading my posts)
• I don't want to grow up

Well, its definitely been a while since my last update.  However, I do have a good excuse this time....  REALLY!

I acutally too a vacation!  Imagine that, a real honest, one-week vaction from work.  This included my freelancing on Odesk.com.  Pictures will be coming soon, but I have to weed out the family from the public ones.  You know how it is.

Quick Overview:

So, back to Odesk.com.  I've been looking at freelancing my embedded linux skills for a while now and stumbled upon the odesk.com site. Here is my profile on there if you are interested.  While there isn't a plethora of embedded linux jobs on there, the ones that I have seen are from knowledgable buyers who know what to expect and are willing to pay for real skill.  I did also sign up for getafreelancer.com and some other site, but with the nearly hourly email on those sites, its hard to sort the wheat from the chaff.  They just really annoy me. Odesk keeps a nice balance of updates that come out, at max, once a day.

Some of the other sites I've been to don't let you know anything about your likely employer, so you're just kind of throwing bids down a hole. On Odesk, you get an idea of the buyer you're dealing with as both the buyer and provider can leave feedback that is public.  There is also a ranking system and free online tests to help you show off your skill level.

Now, enough of the happy-go-lucky stuff.  There are some gotchas that you need to know about.  As compared to other sites, they aren't that bad, but its good to know up front.

Hourly Jobs:

This is what most providers prefer.  Basically, Odesk provides a client that you install on your computer that will take screen shots and append your current status (this is generally updated every half hour... VERY good idea to do this as it prevents chargebacks).  Each week, Odesk submits your work journal for review to your buyer.  You do have time to go in and edit the entries and remove any times you weren't actually working on their project (very unlikely, but it's there for you to work on).

At this point, the buyers payment method is debited for the work you've done and held in escrow.  The buyer then has a week to review your log and raise any concerns.  You have two days to review/respond to the buyer(I have, as yet, had no concerns raised).  If nothing occurs after this 9 days, your Odesk account is fully credited the pending payment.

That's right, you're practically garunteed payment in the hourly system.  Also, buyers have the opportunity to contest the issue before payment is rendered.  And if you're keeping track, this also means that 10 days after your week is done, you get paid.  Now isn't that nice?

Flat Fee:

Now, this one isn't preferred by providers simply because you are NOT garunteed pament.  With the client and review period for projects, you are.  However, the flat fee are more like your general freelancing contract.  I've yet to do a flat fee job, and I really don't intend to... but the opportunity is there if you want to break into the business, so to speak.

So, there you have it.  I recommend you at least check it out to see if there are jobs you'd like to apply for.  If not, just forget I mentioned it :D