Automating with convention: Introducing sub
And again the team that made Basecamp and Rails created something interesting, sub:
When I started my on-call shifts, we had pretty little in the way of automation for day-to-day issues. Tasks like SSH’ing into our cluster, starting a Rails console, or doing a deep search through our gigantic mail directories, were either shelved away in someone’s bashrc, history log, or just ingrained into someone’s memory. This pain was also felt by a few other of my fellow programmers, and we started cobbling together a Git repo.
Sub is the pattern how to organize all these. More on it in this article by Nick.