Prove Your Code Works: How to Communicate Quality

Prove Your Code Works: How to Communicate Quality

Professionalism has two core features, expertise and guarantees. This talk delves into the topic of observability and how professional software developers can guarantee their software works and communicate this to others. It covers the checks to make, the metrics to collect and the documentation to write so developers can prove code works.

99a446aac48cfaf36593646d5565a830?s=128

Rob Waller

June 03, 2020
Tweet

Transcript

  1. 2.

    W: rbrt.wllr.info | T: @RobDWaller Hello! Rob Waller, Aylesbury UK

    Roles: Developer, Manager, Architect. Languages: PHP, JavaScript, Rust. Work: ReallySimpleJWT, csp_generator. Home: 1x , 2x
  2. 9.
  3. 36.

    W: rbrt.wllr.info | T: @RobDWaller Useful Tools & Links Mutation

    Tests Infection PHP: https://infection.github.io/guide/ Stryker: https://stryker-mutator.io/ Mess Detection PHPMD: https://phpmd.org/ ESLint: https://eslint.org/docs/rules/complexity Lines of Code PHPLOC: https://packagist.org/packages/phploc/phploc CRAP Index PHPUnit: https://phpunit.readthedocs.io/en/9.1/code- coverage-analysis.html Semantic Versioning https://semver.org/ Code Validity PHPStan: https://phpstan.org/ Psalm: https://psalm.dev/ TypeScript: https://www.typescriptlang.org/ Code Coverage CodeCov: https://codecov.io/ Coveralls: https://coveralls.io/