This document provides advice on various topics related to hacking and coding in 3 sentences or less:
It encourages building your own LEGO blocks instead of balls, explains that REST is a good architecture style, and suggests drawing ideas before coding them. It also warns about password security, offers to build a mafia for protection, and says that edge cases are for a specific type of person. The document ends with a reminder that coding challenges aren't always easy.
Make a system that feeds itself. Silos are harder to explain.\n
I know there’s people who still think it’s cool to be clever. It’s not cool.\n
Naming conventions are awesome. Spell them out clearly and make sure everyone uses them internally.\n
Convenience methods are not evil. Reduce frustration internally and externally.\n
Convenience methods are not evil. Reduce frustration internally and externally.\n
Worry about security everywhere in your API. Trust nothing that comes in from the outside.\n
A solid core of developers that you can sound off against is worth its weight in gold. It also builds out your first evangelists.\n
Too often we worry about the various edges and corners we’ll run into. Unearth them by asking simple questions that everyone can answer. It’s easier to answer 5 simple questions than 1 hard one.\n
Error can and will happen. Be poised and graceful when they do. Make sure they know you thought of that already. Have a document on hand that outlines what’s supposed to happen.\n
It’s our job to do the hard stuff.. otherwise why would I need an API at all?\n