dev-handbook
dev-handbook copied to clipboard
A guide to the processes, conventions, and philosophies of the Clever dev team.
Assessing the effect of code changes on other people/systems @schimmy and @mohit working on this
Adds type check. See https://github.com/Clever/sd2/pull/610 for details.
Should cover: - why version? - semver!!! - bump version each time you deploy - tips by language (e.g. for node, use `npm version`) Questions: - Should we dictate a...
I think a lot of READMEs could benefit from documenting the limitations of the tool, e.g. "X has been tested with a size N input" or "X does not work...
Lots of principles, but no examples
Also might be good to elaborate on strategies to avoid this (e.g. git add -p, git commit -v)
@mohit and @ericavonb working on this
To tie together some of the content we're working on it'd be great to have a guide for code reviewing.