There is something universally awesome about watching people be rewarded for their dedication and audacity. A huge congrats to the ones behind this! (despite a mixed result)
In theory, you should still have to wait the full period. But in practice, it depends on whether the software actually counts elapsed time like a stopwatch (unlikely) or just calculates a future date for release of the gun. As long as the system clock got updated, it would probably OK your gun a day early.
Also worth noting, RescueTime has a "Get Focused" feature that blocks any sites that you have marked as unproductive (for a specified number of minutes).
This one small idea completely changed my life a few years ago. I always keep a list containing my next actions. If I find myself procrastinating, I don't even have to think, I just glance at the list and do whatever is on top.
FWIW, I just switched from Textmate to MacVim 6 days ago, and am already nearly as productive in it as I was on Textmate (no prior vim experience)
I personally found it best to just embrace the vimness (with cheat-sheets beside my monitor). I barely accomplished any work on day 1, but by the end of day 2 I was moving along pretty comfortably.
Very true, but although these optimizations may not increase the actual speed of a database-heavy app by much, they can certainly improve the perceived speed. I've found this to be especially true if you can leave the expensive queries until after the initial page load.
My point is more that I've known more than a couple of frontend developers who leap on nifty frontend profiling tools like these before they've even tried a couple of well-placed table indices, or asking the database developer or systems guy about them. In my experience it's a lot easier to wrest 500ms from a bad query than 5ms from some bad JavaScript.
In reality however you will usually wrest 50ms from DB and can shave off seconds in front-end. It's usually not about Javascript loops optimization, it's about optimization of resource loading and minimizing the effect of network latency.
Even you if shaved 500ms of DB request, hardly anyone will notice if page waits 15seconds before it has everything fetched to be able to render.
It uses Amazon S3 for storage, has versioned backups, very lightweight and fast, and leaves all Mac metadata/permissions intact. I've had 0 crashes or problems in a year of constant use.
They also supply an opensource tool you can use to restore your backups, in the event that you don't have access to your licensed copy of Arq (like if your laptop gets stolen)