You only dev twice
June 13, 2014
JS Library Detection - Tom S
A useful Chrome extension to find out what JS libraries are being used on the website you are browsing.
Git 2.0 - Gavin
git log --show-linear-break is pretty cool. From the man page:
When --graph is not used, all history branches are flattened which can make it hard to see that the two consecutive commits do not belong to a linear branch. This option puts a barrier in between them in that case.
Why Docker? Why not Chef? - Murray
Recently I've been doing a lot of sysadmin work on our infrastructure. Which means I've been learning chef as that's what we use chef to manage it. I would say that, at best, it's been a bit of a frustrating process. I'm sure a large part of that is that I'm learning both chef the tool and our own chef application at the same time.
I don't know that I'm quite ready to throw chef in the bin and use a different tool, but the arguments in this article certainly resonate with me. Particularly the idea of never upgrading a server, just creating a new one and swapping it with the old one. I don't know enough about docker to say if it's something I'd like any more than chef, but this article certainly has me interested.
A first person game-engine in JS - Murray
- The blog post introduces the concepts used in the engine in a clear and understandable way; ray casting, collision detection, lighting effects, etc...
- The code itself is surprisingly simple, even without the blog post to explain the techniques I got a lot out of just reading the code.
A while back I wrote a terrible rogue game engine to randomise names for an LRUG lightning talk evening. I found implementing the game engine for that surprisingly simple (once I found the right resources), and this article has made me consider writing a 3D engine for wandering around in the generated "dungeons".
The Rails/Merb Merge In Retrospect - Murray
This article about the Rails + Merb merge could seem like it is 4 years too late, especially when you consider that Rails 3, the result of the merge, was released in August 2010, but it's hard to evaluate if the merge was a success without the benefit of time to see if rails developers are making much use of the features promised by the merge. Giles argues that mostly we aren't, and that the time it took to deliver the merge meant that Rails lost it's edge in other areas. I don't know that I fully buy the argument that Giles presents, but I'm definitely sympathetic to it.
Either way, I think it's a useful piece of writing and I'd like to see more articles that explore this sort of reflection on technology. So much of the writing about technology we see is just hype about the latest hot! new! cool! thing! that it's refreshing to read about critically evaluating those things much later to see if they delivered on their promises (spoiler: they probably don't).
My Top RailsConf 2014 Talks - Karl
Sandi Metz talks you through her refactor of Jim Weirichs’ Gilded Rose Code Kata. Sandi’s approach is extremely pragmatic and the talk is mostly focused on object orientation. If you haven’t seen it yet you should watch this talk; if nothing else it's a nice satisfying example of how to approach and conquer some really complicated interwoven logic.
“Science is important” says Aaron Patterson. I enjoyed the first part of this talk because it rebutted some of the comments DHH made in his opening speech. Aside from Aarons usual antics he also talks you through his latest creation AdequateRecord.
This one is less about software and more about wetware. Nickolas Means shows you why your impostor syndrome / status anxiety is so powerful and how you can break free from the grip it has on your life.