Title Slide

Our Standards And Why We Use Them

Who Am I? Why Am I Here?

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

Why Do We Need Standards?

What Is Our Stack

• Docker • Sass • Terraform • MySQL • AWS • Redis • PHP • HTML5 • Nginx • CSS3 • Laravel • Javascript • Inertia • Webpack • React

Key Takeaway

STANDARDS HELP - THEY ENABLE DEVELOPERS TO WORK TOGETHER BETTER - SI MPLIFIES CODE REVIEW - KEEPS CODE CONSISTENT ACROSS PROJECTS

PHP - The Standards We Apply

PHP Standards Are Our Centrepiece

• 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

Linter NOT JUST MAKING IT PRETTY

A Bad Code Example

Our Code Fails To Execute

Bringing In Some Packages

Now We Can See Whats Wrong

Our Code Fixed

Our Code Executes

Use Our Standards Packages

Bring Everything In

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”, },

And The Scripts For Composer

PHPStan Neon File

ECS.php

Publish Enlightn

Configure Enlightn

So What Are We Using Here

Why Linting?

Why Ecs?

What Standards Do We Apply?

Why PHPStan

Why Enlightn?

This Is Only A Part Of Our Standards