The slides to my lighting talk at .concat() 2018 at FH Salzburg.

1. Boost. Confidence.
Quality. Namics.
Salzburg, 03. MARCH 2018
Chris Stuff. Senior Frontend Engineer.

2. Namics.
About me.
Chris Stuff.
Senior Frontend Engineer.
Since 2013 @Namics.
Lead of Skill Group Frontend.
Frontend Enthusiast. Musician. Dad.

3. In order to get to a sane
code base it needs a
proper setup assuring the
desired code quality.

4. Namics.
Tools.
🐶
Husky

5. Namics.
Workflow.
Change code git add git commit git push

6. CI Build failed.

8. Namics.
Workflow.
Change code git add
test failed npm test
git commit
test passed
git push

9. Commit failed.

11. Namics.
Cons.
● No instant commit
○ Optimize your linting and testing performance
● Your dev's might punch you first

12. Namics.
Pros.
● Nearly no red builds in your CI environment
● No bad code ever in your git history
○ That doesn't mean, that your app can’t fail. But when it
fails, at least the code base respects your formatting
guidelines
● Consistent code from the very beginning
● Dev’s will love and thank you
○ once they got used to quality assurance

13. Namics.
More links.
● https://github.com/namics/eslint-config-namics
○ General default eslint configs for different environments
● https://github.com/namics/frontend-defaults
○ General default configs regarding a11y, documentation
skeletons, editorconfig, git config, …

14. Caring for unwritten code
is like caring for the
unborn children.

15. Danke. Namics.
© NAMICS AG 2017
christian.stuff@namics.com
Thanks. Namics.