A presentation at We Are Developers World Congress 2021 by Christopher Miller
Our Standards And Why We Use Them
Why Can I talk about this (please note, the email address will no longer be relevant to me - visit the site for up to date info
• Docker • Sass • Terraform • MySQL • AWS • Redis • PHP • HTML5 • Nginx • CSS3 • Laravel • Javascript • Inertia • Webpack • React
STANDARDS HELP - THEY ENABLE DEVELOPERS TO WORK TOGETHER BETTER - SI MPLIFIES CODE REVIEW - KEEPS CODE CONSISTENT ACROSS PROJECTS
• Linter • ECS • PHPStan • Enlightn • Tests Everything we do is thought in terms of the “hit by a bus” scenario If a developer were not available tomorrow, could someone else pick up their work?
Linter NOT JUST MAKING IT PRETTY
Bringing In All The Packages We Need “require dev”: { “jumptwentyfour/php coding standards”: “^0.0.1”, “jumptwentyfour/project analysers”: “^0.0.2”, “php parallel lint/php console highlighter”: “^0.5.0”, “php parallel lint/php parallel lint”: “^1.3”, },
Standards are often misunderstood, and treated as a bad thing. At Jump 24 (my employer at the time) We specialise in Standards Driven and Test Driven Development. This shows the standards in place, and why we use them.
Here’s what was said about this presentation on social media.
for free. You
can too.