Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
[Brief description ]
- [more description]
- [more description]
- [more description]
- After making changes, ALWAYS make sure to start up a new server so I can test it. | |
- Always look for existing code to iterate on instead of creating new code. | |
- Do not drastically change the patterns before trying to iterate on existing patterns. | |
- Always kill all existing related servers that may have been created in previous testing before trying to start a new server. | |
- Always prefer simple solutions | |
- Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality | |
- Write code that takes into account the different environments: dev, test, and prod | |
- You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested | |
- When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we d |