Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
FRONTEND AUTOMATION BRING IT TO THE NEXT LEVEL jsDay 2017
Slide 2
Slide 2 text
MATTEO RONCHI @CEF62 - GITHUB/CEF62 SENIOR SOFTWARE ENGINEER AT WORKWAVE PROUD MEMBER OF FEVR
Slide 3
Slide 3 text
A LITTLE HISTORY
Slide 4
Slide 4 text
EVERYTHING STARTED TO CHANGE AROUND 2010
Slide 5
Slide 5 text
2013: FRONTEND-OPS DEFINED BY Alex Sexton
Slide 6
Slide 6 text
In a team, everyone should have a role and fulfill a specific purpose -- anonymous
Slide 7
Slide 7 text
MODERN FRONTEND DEVELOPMENT AIN'T ANY DIFFERENT
Slide 8
Slide 8 text
WE ASK FRONTEND DEVELOPERS TO FULFILL MULTIPLE ROLES THAT REQUIRE FUNDAMENTALLY DIFFERENT SKILL SETS
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
FRONTED DEVELOPMENT IS HARD
Slide 11
Slide 11 text
2015: TRANSPILE ALL THE THINGS! 2016: JAVASCRIPT FATIGUE 2017: TAKING BACK CONTROL! (HOPEFULLY...) ☔
Slide 12
Slide 12 text
THE PROBLEM WE FACE
Slide 13
Slide 13 text
ALWAYS EVOLVING STANDARDS
Slide 14
Slide 14 text
ALWAYS EVOLVING STACK OF TOOLS
Slide 15
Slide 15 text
TOO MANY OPTIONS
Slide 16
Slide 16 text
TOO MANY UNSTABLE OPTIONS
Slide 17
Slide 17 text
WHAT YOU CAN DO
Slide 18
Slide 18 text
GROW INTERNAL EXPERTISE
Slide 19
Slide 19 text
KNOWLEDGE BRINGS UNDERSTANDING AND BETTER CHOICES, WHICH LEADS TO FEWER RISKS AND MORE MAINTAINABLE PROJECTS
Slide 20
Slide 20 text
CREATE A CURATED LIST OF SKILLED INDIVIDUALS TO FOLLOW
Slide 21
Slide 21 text
DON'T PANIC! YOU WILL BREAK THINGS MOST OF THE TIME
Slide 22
Slide 22 text
RESERVE A MINIMUM TIME EVERY WEEK TO TAKE CARE OF YOUR PROJECT
Slide 23
Slide 23 text
AVOID BOILERPLATES AND GENERATORS, PREFER SMALL TOOLS TRY TO UNDERSTAND HOW THEY WORK INSTEAD OF BLINDLY USING THEM
Slide 24
Slide 24 text
DO YOU TEST YOUR CODE? YOU SHOULD ALSO TEST YOUR PROJECT'S AUTOMATION
Slide 25
Slide 25 text
ORGANIZE YOUR AUTOMATION AND DECOUPLE IT FROM THE PROJECT
Slide 26
Slide 26 text
USE NPM SCRIPTS, YOUR PROJECT ALREADY HAS THEM ENABLED USE PLAIN NODE MODULES FOR YOUR AUTOMATION WORKFLOWS
Slide 27
Slide 27 text
MOVE YOUR AUTOMATION TO A SEPARATE REPOSITORY
Slide 28
Slide 28 text
DEMO RUN-IT DEMO SCRIPTS
Slide 29
Slide 29 text
AT THE BARE MINIMUM TRY TO ISOLATE GENERIC PROCESSES AND AUTOMATION YOU WILL BE SURPRISED BY HOW MUCH CODE CAN BE REUSED ACROSS PROJECTS
Slide 30
Slide 30 text
YOUR AUTOMATION IS NEVER FINISHED
Slide 31
Slide 31 text
YOUR PROJECT'S AUTOMATION NEEDS TO BE CARED FOR AND WELL GROOMED YOUR EFFORT WILL BE REPAID TENFOLD
Slide 32
Slide 32 text
DEVELOPER EXPERIENCE MATTERS
Slide 33
Slide 33 text
DOCUMENT YOUR SCRIPTS AND THEIR PURPOSE A CONCISE DESCRIPTION IS OFTEN MORE THAN ENOUGH.
Slide 34
Slide 34 text
YOUR AUTOMATION HAS TO WORK BUT DOESN'T NEED TO BE UGLY OR FRUSTRATING. YOU KNOW BETTER! ALWAYS DOGFOOD YOUR OWN TOOLS!
Slide 35
Slide 35 text
Thanks @cef62 https://joind.in/talk/eba12