http://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to
blog-post-write-code-easy-to-delete#less-dry-to-ease-deletion1 2 To write code that's easy to delete: repeat yourself to avoid creating dependencies, but don't repeat yourself to manage them. blog-post-write-code-easy-to-delete#less-dry-to-ease-deletion1 2
blog-post-write-code-easy-to-delete#duplicate-rather-than-wrong-abstraction1 Building reusable code is something that's easier to do in hindsight with a couple of examples of use in the code base, than foresight of ones you might want later. On the plus side, you're probably re-using a lot of code already by just using the file-system, why worry that much? A little redundancy is healthy.
It's good to copy-paste code a couple of times, rather than making a library function, just to get a handle on how it will be used. Once you make something a shared API, you make it harder to change. blog-post-write-code-easy-to-delete#duplicate-rather-than-wrong-abstraction1
TODO - not done reading yet. Left off at "Step 4: Don't write boilerplate"