Well of course you should, and now you can:
$ awesome-time start
Start doing awesome.
Everybody has their limits:
$ awesome-time stop
Stop doing awesome.
You can't yet. Readme Driven Development for the win.
It makes you productive, by limiting the sites you can go to in your time of Awesome
.
$ awesome-time add-site time-wasting-site.com time-wasting-site2.com
shouldnt-you-be-doing-something-awesome
SSH
you into your own machine (instead of changing /etc/hosts
which would require root access). All the blocked sites are in ~/.ssh/config.block
which temporarily replaces ~/.ssh/config
, whenever you should be doing something Awesome. ~/.ssh/config
allows you to modify hostnames; we can redirect time-wasting-site.com
to 127.0.0.1:1337
. At 127.0.1:1337
is a simple Sinatra application telling you to stop wasting your time, and start being awesome. To run the Sinatra application smoothly in the background, and for the overall awesome: It's handled as a deamon.
If you can handle not going to time-wasting sites without something like this, sure.
- Fork the project.
- Make your feature addition or bug fix.
- Add tests for it. This is important so I don't break it in a future version unintentionally.
- Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
- Send me a pull request. Bonus points for topic branches.
Copyright (c) 2010 Sirupsen. See LICENSE for details.