Experimenting with Github to increase personal technical productivity
Lately I’ve realized how much more time I’ve been spending in a shell lately — for quick, one off “solutions” (like transforming a text based file, a quick report, etc) there’s really nothing that beats it. I run across a lot of one-offs that seem re-usable, but apart from sometimes throwing them into a ‘notes.txt’ file, I lose them. My solution to keeping this sort of tech knowledge is usually a blog post (I reference my own blog regularly) but these solutions don’t feel like they deserve a entire blog post. So from now on if I come across anything from a neat and re-usable one-liner up to a simple pipe-able Python script, I’m going to try to put in the extra 10% to polish it up and check it in to:
https://github.com/derwiki/scripts
I’ve got this set up on my path by adding `export PATH=$PATH:~/src/scripts/` in my .bashrc so I can easily access any of these scripts. I’m playing with Github’s Issues for the first time to keep a backlog of bugs and planned enhancements. One goal is to build a library of useful scripts that stay in sync across machines and that will make me (and maybe others) more productive. Another goal is to try and make one commit a day, no matter how small — it’s a good check to make sure I’m still learning something new every day.
