Automatic constraints as a team maturity accelerator for startups

Franccedilois-Guillaume

RIBREAUFGRibreau

Franccedilois-Guillaume

RIBREAUFGRibreau

BringrPerformance oriented

Social Media Management

BringrLeader europeacuteen de

lengagement client en temps reacuteel

(click2chat click2call click2video community )

sold

Bringr

BringrLeader europeacuteen de

lengagement client en temps reacuteel

(click2chat click2call click2video community )

sold

Bringr

Bringr

Developer oriented real-time monitoring and

administration service for Redis

LET ME TELL YOU A STORY

A growing startup

A growing startup

= a lot of newcomers = ever changing directions = need to move fast

[Where How What to follow] to start

- How to start alone a new project - Where are the conventions - What are the best practices - How can I quickly start on a new language - How to setup my dev env - How to deploy in production

Only one quality guard

code reviews

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

A growing startup

A growing startup

= a lot of newcomers = ever changing directions = need to move fast

[Where How What to follow] to start

- How to start alone a new project - Where are the conventions - What are the best practices - How can I quickly start on a new language - How to setup my dev env - How to deploy in production

Only one quality guard

code reviews

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

A growing startup

= a lot of newcomers = ever changing directions = need to move fast

[Where How What to follow] to start

- How to start alone a new project - Where are the conventions - What are the best practices - How can I quickly start on a new language - How to setup my dev env - How to deploy in production

Only one quality guard

code reviews

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

[Where How What to follow] to start

- How to start alone a new project - Where are the conventions - What are the best practices - How can I quickly start on a new language - How to setup my dev env - How to deploy in production

Only one quality guard

code reviews

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

- How to start alone a new project - Where are the conventions - What are the best practices - How can I quickly start on a new language - How to setup my dev env - How to deploy in production

Only one quality guard

code reviews

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

Only one quality guard

code reviews

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

PROBLEM

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

SOLUTION

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

Letrsquos create conventions or how to add a new problem on top of another

httpbitly1iJ27GA

httpbitly1iJ27GA

httpbitly1MmjFln

httpbitly1iJ2BfV

js best practices

java code-style httpbitly1G4rjvN

java code-style httpbitly1G4rjvN

Okay

So whatrsquos the workflow now

read conventions

write codeproduction

ready

memorise conventions

pass the code-review

Hard learning curve amp easy to forgot conventions

while writing code

Humans are faillible

BACK TO SQUARE ONE

Only one quality guard

code reviews

blabla

blabla

(

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

read conventions

write codeproduction

ready

memorise conventions

pass the code-review

Hard learning curve amp easy to forgot conventions

while writing code

Humans are faillible

BACK TO SQUARE ONE

Only one quality guard

code reviews

blabla

blabla

(

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Humans are faillible

BACK TO SQUARE ONE

Only one quality guard

code reviews

blabla

blabla

(

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

BACK TO SQUARE ONE

Only one quality guard

code reviews

blabla

blabla

(

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Only one quality guard

code reviews

blabla

blabla

(

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

(

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Why not add tests tradeoff

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

)

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Even with conventions Itrsquos still hard to detect issues in code-reviews

- code-style - undefined variables - misused functions - wrong types - DRYSoC respect - security - project structure - file naming

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Does conventions mean scalability

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Nope

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

more feedbacks

production

more recruits

more code-reviews

human error

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

more code-reviews

more feedbacks

human error

production

production

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

It does not scale- learning curve is too hard - too hard for newcomers on other projects - conventions grow too fast - technology is moving faster than conventions

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

SOLUTION

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Dont rely on principle rely first on automation

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

AUTOMATE EVERYTHING

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Automate code-style checks

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

jscs

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

jscsrc

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

jscs

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Automate quality-checks with static-analysis

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

eslintrc

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Eslint

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Eslint

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Automate DRY-checks

with static-analysis

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

JSInspect

Match - 2 instances

- domainDateRangeIntervalValueObjectjs3537 + domainMeasurementQueryValueObjectjs205207 if (_isObject(req) || req || _isObject(reqquery)) return new PrettyError(400 Invalid request)

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

LETrsquoS INVENT

A NEW PRINCIPLE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Still

- when amp how to run these checks - how to manage legacy code - how to talk about automated conventions - how and who choose conventions - how to be quickly up to speed with new projectsplatformlanguages

when amp how to run these checks

read conventions

write code production

memorise thempass

code review

before

write code production

pass the code review

CIautomated

checks

continuous checks

after

Letrsquos introduce

check-build (for javascript)

httpbitly109XewR

- when amp how to run these checks - how to manage legacy code - how to talk about automated conventions - how and who choose conventions - how to be quickly up to speed with new projectsplatformlanguages

when amp how to run these checks

read conventions

write code production

memorise thempass

code review

before

write code production

pass the code review

CIautomated

checks

continuous checks

after

Letrsquos introduce

check-build (for javascript)

httpbitly109XewR

when amp how to run these checks

read conventions

write code production

memorise thempass

code review

before

write code production

pass the code review

CIautomated

checks

continuous checks

after

Letrsquos introduce

check-build (for javascript)

httpbitly109XewR

read conventions

write code production

memorise thempass

code review

before

write code production

pass the code review

CIautomated

checks

continuous checks

after

Letrsquos introduce

check-build (for javascript)

httpbitly109XewR

write code production

pass the code review

CIautomated

checks

continuous checks

after

Letrsquos introduce

check-build (for javascript)

httpbitly109XewR

Letrsquos introduce

check-build (for javascript)

httpbitly109XewR

httpbitly109XewR

5SecurityFres

hness

Code styleDRYness

SyntaxGoodPractices

JSInspect

DavidNsp

httpbitly109XewR

how to manage legacy code

PROBLEM

Bringr

monolith

SOLUTION

First donrsquot feed the damn monolith

Bringr

Bringr Strategy

BringrImpact

Bringr

BringrSourcing

Bringr

BringrAlerts

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

PROBLEM

Bringr

monolith

SOLUTION

First donrsquot feed the damn monolith

Bringr

Bringr Strategy

BringrImpact

Bringr

BringrSourcing

Bringr

BringrAlerts

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

Bringr

monolith

SOLUTION

First donrsquot feed the damn monolith

Bringr

Bringr Strategy

BringrImpact

Bringr

BringrSourcing

Bringr

BringrAlerts

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

SOLUTION

First donrsquot feed the damn monolith

Bringr

Bringr Strategy

BringrImpact

Bringr

BringrSourcing

Bringr

BringrAlerts

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

First donrsquot feed the damn monolith

Bringr

Bringr Strategy

BringrImpact

Bringr

BringrSourcing

Bringr

BringrAlerts

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

Bringr

Bringr Strategy

BringrImpact

Bringr

BringrSourcing

Bringr

BringrAlerts

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

Then only automate checks on new code

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

Bringr Strategy Bringr Impact

Bringr Backend

Bringr Sourcing Bringr Account

Bringr Alerts

Filtering

Statistics

Rules EnginePublishing

Statistics Updater

UIUIUI

Indexing

G+

Vimeo

Facebook

Youtube

Wordpres

Twitter

Notifications

only automate new code

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

how to talk about automated conventions

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

PROBLEM

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

Automating everything can sometimes means less readable conventions amp best practices

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

jscsrc

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

SOLUTION

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

Generate readable documentation

from automated tools

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

write code production

pass the code review

CIautomated

checks

continuous checks

before

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

write code production

pass the code review

CI

continuous checks

after

readable convention

automated checks

jscsrcbefore

httpbitly1itmabjafter

jscsrcbefore

httpbitly1itmabjafter

httpbitly1itmabjafter

httpbitly1itmabj

how and who choose conventions

Conventions should be versioned

Debates should be around

Pull-Requests

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Conventions should be versioned

Debates should be around

Pull-Requests

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

Debates should be around

Pull-Requests

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

rdquoFGRibreau

ldquoDONrsquoT CREATE CONVENTIONS YOU CANrsquoT ENFORCE

how to be quickly up to speed with new projectsplatformlanguages

CI

check-build

centralize conventions

keep settings

DRY

Still

You still need to explain the WHY

We record internal talks about why we do what we do

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

CI

check-build

centralize conventions

keep settings

DRY

Still

You still need to explain the WHY

We record internal talks about why we do what we do

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

centralize conventions

keep settings

DRY

Still

You still need to explain the WHY

We record internal talks about why we do what we do

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

Still

You still need to explain the WHY

We record internal talks about why we do what we do

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

You still need to explain the WHY

We record internal talks about why we do what we do

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

We record internal talks about why we do what we do

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

One last thing

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

These automated principles were about code

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

How to spread wider principles (eg application architecture)

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

stories2

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

FGRibreau

constants filesenvironme

nt variables

distributed

Simplicity Genericity

Knowing every running environments

One configuration to rule them all

CONFIGURATION

rdquoFGRibreau

ldquoEVERY CONSTANT NUMBER BOOLEAN OR STRING SHOULD BE CONFIGURABLE

How can we be sure developers will follow this principle

Build base libraries Ease the learning curve Constrain by API design

microserviceAPI

documentation

API schema

API validation

swaggerjson-schemahapijson-api

(Pre-configured in a bootstrap project)

Everything we just saw makes a common base

- leads the developer mindset while coding - brings developers quickly up to speed - flatten issues to cross-language concerns - being able to capitalize on amp standardize issues with an adapted tooling is a huge win

What about non-code principles Eg github repository names

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

Build base libraries Ease the learning curve Constrain by API design

microserviceAPI

documentation

API schema

API validation

swaggerjson-schemahapijson-api

(Pre-configured in a bootstrap project)

Everything we just saw makes a common base

- leads the developer mindset while coding - brings developers quickly up to speed - flatten issues to cross-language concerns - being able to capitalize on amp standardize issues with an adapted tooling is a huge win

What about non-code principles Eg github repository names

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

microserviceAPI

documentation

API schema

API validation

swaggerjson-schemahapijson-api

(Pre-configured in a bootstrap project)

Everything we just saw makes a common base

- leads the developer mindset while coding - brings developers quickly up to speed - flatten issues to cross-language concerns - being able to capitalize on amp standardize issues with an adapted tooling is a huge win

What about non-code principles Eg github repository names

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

swaggerjson-schemahapijson-api

(Pre-configured in a bootstrap project)

Everything we just saw makes a common base

- leads the developer mindset while coding - brings developers quickly up to speed - flatten issues to cross-language concerns - being able to capitalize on amp standardize issues with an adapted tooling is a huge win

What about non-code principles Eg github repository names

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

Everything we just saw makes a common base

- leads the developer mindset while coding - brings developers quickly up to speed - flatten issues to cross-language concerns - being able to capitalize on amp standardize issues with an adapted tooling is a huge win

What about non-code principles Eg github repository names

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

What about non-code principles Eg github repository names

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

A cron checks every days repository names If a developer makes a mistake he will be notified

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

PRINCIPLES

CONVENTIONS

AUTOMATION

CONSTRAINTS

CODE

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you

FGRibreau

QuestionsJoin us iAdvize

Donrsquot forget to take some stickers

Thank you