This is the type of quality submission that keeps me coming back to /.

Where are my mod points when I need them? Mod it up to 11.

Maybe the MAC was wired to a buggy PHY. It would be veeeeery surprising for lspci to show a different device than what is really there, though it isn't impossible.

You are a braver rider than I. The first day I had my SWB recumbent I pulled up to a red light next to a pickup. There was no way the driver could have seen me below his right bumper, and a trike is lower. If the driver had decided to turn right, I would have been crushed. I got a flag the next day. But now I've given up on the recumbent for commuting in my small town -- I just don't feel as safe as I do on the more nimble and visible upright. Perhaps a trike, being statically stable, would provide more confidence. And perhaps the body of a velomobile would stand out more. But you are still very low down.

Obviously no one here has ever ridden a recumbent bicycle in traffic. If you had, you'd see how rediculous it is to even think of taking one of these on pavement shared with cars. YOU ARE ABSOLUTELY INVISIBLE TO CARS in a vehicle this low. And because of the enclosure you have no peripheral vision so you cannot look out for other vehicles -- even other velomobiles. I didn't see one "safety flag" in any of the pictures, which tells me that none of these vehicles are used by anyone who cares for their life, or they are just toys for a weekend cruise. As other posters have said, these are only practical with a different road system, and I argue a different bike path system. How would you handle passing a group of 15mph standard bicyclists in your vision impared wide wheelbase trike wheeled monster? You wouldn't, it wouldn't be safe on bike paths of today for you or the other riders.

A Computer Engineering curriculum is much better than a traditional CS degree for this type of work, so you might look at what texts are being used in high quality CE programs. The Embedded Systems Conferences from UBM are also a good source of training for low level firmware implementation.

The developer that uses the right tool for the job will be more productive.

That means using a language with static type checking and a productive debug environment. Learning a new system infrastructure takes time, but only finding out about easily preventable failures during testing instead of compile time costs more.

... April 1st was almost two weeks ago.

I have to agree here. You say you are a small company, in my experience requirements for even modest size projects are generally easy to manage with human language documents, just label everything for traceability. If a word processor is too awkward switch to a spreadsheet, or use them in combo. But I do highly recommend using a defect tracking database. I like Jira.

My bank is similar when it comes to CSV/QIF/OFX files, only 90 days of history. But they have years of online statements in pdf format. Recently I got behind on my imports, and found that pdftotext and a little perl was all I needed to create .qifs from the pdf statements. .csv should be easier.