9
Optimizing Developer Workflows Ross Kukulinski - @rosskukulinski #BayNode Lightning Talks March 5, 2014

BayNode Optimizing Developer Workflows

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: BayNode Optimizing Developer Workflows

Optimizing Developer Workflows

Ross Kukulinski - @rosskukulinski#BayNode Lightning Talks

March 5, 2014

Page 2: BayNode Optimizing Developer Workflows
Page 3: BayNode Optimizing Developer Workflows

Rapid iteration

Write Tests Write Code Run Tests Test App

Later, Rinse, Repeat.

The faster you can do this, the better.

Page 4: BayNode Optimizing Developer Workflows

Test Driven Development

• You are doing this, right?

• We run unit tests after every change

• We run the test suite as pre-commit hook

Page 5: BayNode Optimizing Developer Workflows

JSHint / Lint / Whatever

• Teams should agree on a style– (Or at least agree to disagree but deal with it)

• Linting can help enforce (and catch ‘dumb’ mistakes)

• We run lint on every file change

Page 6: BayNode Optimizing Developer Workflows

Live Reload

• Chrome extension• Modules for Grunt, Gulp, others• Refresh your browser on change

Page 7: BayNode Optimizing Developer Workflows

Make / Grunt / Gulp / Whatever

Task runners automate developer workflows

They also provide consistency across your team

Pick one (or more) and use them

Page 8: BayNode Optimizing Developer Workflows

• Application Scaffolding• http://yeoman.io/

Page 9: BayNode Optimizing Developer Workflows

DEMO!

• https://github.com/DaftMonk/generator-angular-fullstack