joecomotion
I spent 10 years between 1997 and 2009 (took a break for grad school) working on semi-automated tracking systems for ports up and down the West Coast (and other places), including one in Oakland. The recent surge in interest in intermodal container ports sure brings back memories!
My company developed niche systems for tracking container location within the terminal by instrumenting and tracking any crane/truck/etc. that could move a container. Even though longshoremen were still operating the equipment, it helped to have a real-time (and historical) picture of what happened, because planning systems were now less subject to clerical mistakes.
Here's their (sort of terrible) website: http://www.nowsol.com/
These guys pretty much own the market for the terminal-planning systems we fed: http://navis.com/
Optimal State Estimation by Dan Simon helped, too: http://www.amazon.com/Optimal-State-Estimation-Nonlinear-App...
- Share from Dropbox: when composing an email, insert a link to a file already in your Dropbox.
- Save to Dropbox: when reading email, save a received attachment to your Dropbox.
- Upload to Dropbox: if you try to attach file over the 25MB attachment size limit, you're given the option to upload it to your Dropbox and link to the file on Dropbox.
If everyone is responsible, no one is responsible.
Principle #15 here weighs in on this: http://www.greenwichharborpartners.com/uploads/Principles_by...
https://www.projectslice.com/mail_app
Full disclosure: I work for Yahoo! and supported them building this on the Yahoo! Mail app platform.
Also, I believe safari will ignore your caching/expires headers if you use GET params.
(defun force-revert-buffer () (interactive) (revert-buffer t t))
(define-key global-map "\C-cr" 'force-revert-buffer)
Most of the people who code this way that I've met don't do it b/c they're trying to be 'pure.' Most of them say it was coding standard some manager mentioned somewhere else long ago and now they just do it w/o thinking.