Thursday 13th February, 2014
Week 265 - Interesting links
This is roughly in line with the themes discussed at TICOSA. The author gives some useful git tips to help with digging into the story of the code, as well some general tips to help you be nice to your future self and colleagues. — CR
I haven’t tried this but it looks like it could be useful shortcut for finding the commit history for a specific line of code. The author says they were inspired by the Every line of code is always documented post. — CR
Following on from Chris’ links above, this article by Phil Potter is a good explanation of how to use git to do software archeology. This relates quite closely to something I’m currently working on. — JM
This reminded me of a thought I’d had about linking web pages (e.g. blog posts or news articles) to their source in version control (assuming that’s how they’re stored). I can imagine that such a machine readable link would make it possible to add something to the browser to give a nice view of the history of the page over time. — CR
I’ve spent quite a bit of the last week researching various Ruby parsers for converting Ruby code into an AST of S-expressions. Libraries in this space appear to have gone off in a few different directions, so I was interested to read about Unified Ruby. — JM
Someone who habitually digs deeper than strictly necessary is worth listening to. When they know, they will say so. When they don’t know, they’ll say so and then, if they are curious, go do the work to find out.