- Care about their work
- Want to produce quality work
- Treat their work as more than a dayjob
- Are proud to show off their work
- Strive to create work that they are not afraid to change
The only way to avoid being afraid of changing your code is to write tests.
If you don’t test it, you’re up a creek.
- Namespace your functions.
- Declare your vars up top.
- Encapsulate your code in brackets (IIFEs immediately invoked function expressions).
- Don’t use “with”, it’s ambiguous.
- Don’t abuse eval, almost everything you can do with eval you can do without eval.
Easy Jenkins integration copying path of the pom.xml file.