This morning, I created a new repository on Github called toolkit. I’m using it to keep track of the tools I use every day, in order to benefit others who are interested in how I work, and for my own benefit, to be able to easily refer to documentation, source code and links for tools that may be useful for a particular situation.
I’ve tried to do this type of thing many times in the past - sometimes by writing a blog post, or forking or ‘starring’ a repository on Github. There are a few reason’s why I’ve started off with Git repository this time though:
My toolkit is, in many ways, performing a similar function to blog post or ‘liking’ or ‘starring’ something, but I think that the semantics are important. Writing a post about something is all well and good, but it tends to get outdated, and buried amongst all the other things that I might blog about - it’s too much work to trawl through a bunch of posts looking for one particular link. Similarly with starring something - just because I star it, it doesn’t mean I use it - it just indicates that I find the project interesting and might follow up on it. My toolkit ONLY contains things that I have already found useful, or know that I’ll need, and doesn’t include any other extraneous material to get in the way when I need to find something.
I’ve made a start by adding a bunch of submodules to projects that I could think of off the top of my head, but I’m already coming up with ideas for more. If you like the concept, head over to Github and check it out - and feel free to contribute your favourite tools for me to try out!