| « Real Time Photo: Mmm, bready | Real Time Photo: Cup nearly runneth over » |
Cool new-to-me stuff from the past few whiles
As part of my efforts to increase efficiency and productivity, I've found a number of things on the Internet lately that are, in my opinion, totally awesome.
- Joule (joule.marnanel.org): This site keeps tabs of who is following/friending you on a variety of social mumblemrf sites, such as Digg, LiveJournal, and Twitter. It produces a daily summary of changes (optionally sent via Twitter direct message) as well as a handy chart showing you the lifespan of some of your more ephemeral followers.
- Hiveminder (hiveminder.com): From the makers of Request Tracker comes this web-based to-do manager. It's got plenty of features for the geek crowd, and is designed with collaboration in mind. I'm still getting used to it, but I've already moved my to-do list over with great rejoicing. Thanks to mikegrb for attending YAPC and telling me about this.
- GitHub (github.com): I am not a programmer. Well, actually, I take that back: I've written a number of tools to make my life better. I've now realized that I'm enough of a programmer that I can extract value from "real programmer tools" like revision control and online repositories. Based on the Git distributed revision coontrol system, GitHub allows programmers (and people who write code) to store stuff online and work collaboratively on it. Git's decentralized nature makes something like GitHub both essential and possible, and for that I enjoy it. You can find me on GitHub as rtucker.
- The Fucking Weather (thefuckingweather.com): Sometimes you just need to know what the weather is doing, without all that hubbly-bub and happenpants of real, professional weather people. Thanks to thefuckingweather.com, I know that it's fucking nice outside, and I may now safely remove my ball-mittens.
2 comments
Comment from: James Sweet [Visitor] · http://nojesusnopeas.blogspot.com
So what exactly is the difference between GitHub and something like SourceForge?
On Jun 28, James Sweet wrote "More thoughts on gun control".
06/29/09 @ 08:16
The simple and most accurate answer is "my friends use github, so I might as well too."
I find git's concepts rather appealing, especially for the sort of off-the-wall, rapid, niche projects I like to do. GitHub feeds into this by being built *for* git: I can fork a project in seconds flat, hammer away at it for awhile, and fling it back to them quickly and easily.
Why git over CVS/Subversion/etc? A tough question to answer. I've tried pretty much every free revision control system that has come along over the years, and never really latched on as well as I could have. I think my problem is that I want to have One Tool for both local revision control (homework, documents, workstation configuration files, etc) and "real" projects hosted on a centralized server. RCS was the former, CVS was the latter, and Subversion tried to bridge the gap but it still smelled like CVS. Git has gone with the local-revision-control-first approach, which is nice for how I work.
I was also very happy when the initial GitHub signup process requested my ssh public key. I've invested some time into making my ssh infrastructure practically automatic, and it's nice to see that being put to work ;-)
I find git's concepts rather appealing, especially for the sort of off-the-wall, rapid, niche projects I like to do. GitHub feeds into this by being built *for* git: I can fork a project in seconds flat, hammer away at it for awhile, and fling it back to them quickly and easily.
Why git over CVS/Subversion/etc? A tough question to answer. I've tried pretty much every free revision control system that has come along over the years, and never really latched on as well as I could have. I think my problem is that I want to have One Tool for both local revision control (homework, documents, workstation configuration files, etc) and "real" projects hosted on a centralized server. RCS was the former, CVS was the latter, and Subversion tried to bridge the gap but it still smelled like CVS. Git has gone with the local-revision-control-first approach, which is nice for how I work.
I was also very happy when the initial GitHub signup process requested my ssh public key. I've invested some time into making my ssh infrastructure practically automatic, and it's nice to see that being put to work ;-)
06/29/09 @ 09:22