Ditto. Hit the job boards and find somewhere competent. The people you're working for will be out of business soon at this rate, anyway.

The oddest thing I've written - code that crashed, deliberately, in different ways based on use selection.

I was working a project where we built atop an "abstraction layer" designed to insulate us from OS changes (this was the 90s, such things were in vogue). The team doing the abstraction layer, at another site, rolled out a new version. The best I can say of it is, it compiled.

Different parts of my code started exploding. Almost literally - I had one test case cause a kernel panic in AIX, which was no small challenge. Of course, it was all blamed on my "bad code practices" and couldn't POSSIBLY be flaws in their update.

Over the course of two weeks of core dump analysis, discussion with the AIX team at IBM, and heated exchanges going up the chain of command, I crafted a 200-line program which three different options to crash the system. Pick your choice, guaranteed crash, including the kernel panic. Once I delivered THAT through channels, they got silent quick. It took them another month to fix their internal bugs and re-deliver. The memory leak I found in that version required another "prove it!" program, but my management had my back by then.

I recall a rash of home burglaries when a certain company in Florida was using cheap materials under the siding, before the inner walls were finished, where burglars were removing the siding, punching through the outer walls, opening doors from the inside and making off with copper piping, wiring, and appliances. They were keeping track of the progress of the new homes and would wait until the appliances were installed before going in at night and removing them. They were even replacing the siding to make it harder for security to notice the holes until the work crews showed up to finish the drywall and install carpet.

Gosh, I wish I had mod points for this one :)

An iOS, and Android app for tablets and phones, Simple Physics works very well to educate kids on forces, leverage, relative strength, etc. Build a bridge and drop rocks on it to see how many it can hold. Build a dam to withstand a flooding river. Build a shelter to withstand a bomb blast, all from the same simple "wooden" materials. My kids play this for hours when I let them.

There's also an excellent Wind Tunnel app for iOS that acts as a simple 2-D wind tunnel, with particle streams, smoke, pressure differentiation, etc.

Fun toys, and the kids learn while they play 'em.

You forgot:

6. Profit.

There will still be graphics overkill. There will also be actors "acting" and a plot that might make sense outside King George's skull.

It's the rolling bags of charts they have to carry with them whenever they fly. There are regulations that specify what charts they have to carry; all in all, a "Jep Bag" is about 35 pounds, and both pilots carry one. If they're using a Electronic Flight Bag app for the iPad, that's a pretty straightforward conversion of mass and very specific savings.

Consider setting up several servers and GlusterFS, auto-replicating the data when it's mounted and presenting a infield shared file system. You can run CentOS or RHEL6 for the OS, and the FS will take care of data persistence, replication, and presenting a CIFS or NFS view.