JackDanger

This is brilliant and I love that it relies almost entirely on Linux primitives already in place.

Having read the article I half-agree with the author. Yes, learning arcane and inconsistent APIs is not the work the students signed up for and studying command-line tools doesn't materially help them in the near-term. However, the things that make the command-line so difficult also make it easy to package tools together underneath simpler apis. I suspect the students are struggling with having to use tools that aren't supported by their department or industry community. Otherwise they'd have a shared script that they all maintain that turns a bare PC/Mac/*nix box into one that's capable of doing great work.

This happens with every single engineering team. Those who understand the tools wrap them up into something solid so new folks have a great experience on their first day.

I second the interest in a blog post. Jennifer, it's rare that someone develops an art background before programming so I'd love to hear your thoughts on the similarities and differences.

In practice the tool doesn't have any blame feel to it. When I commit code that causes problems Squash correctly identifies me and lets me know what to fix. And when I was mistakenly chosen I'm still a good candidate for triaging the bug and sending it off to the appropriate developer.

It currently has clients for Java, Objective-C, Ruby and Javascript. So it most likely supports any application you're working on as long as that application has a git repository. Feel free to contribute a Python client.