How to Write Better Code Automatically

An overview of tools and processes that help you write better code for WordPress or any other PHP application.

Presented at WordCamp Rīga 2017 (November 25).

Transcript

1. How to Write Better 
 Code Automatically Kaspars Dambis WordCamp Rīga, November 2017
3. https://kaspars.net
4. https://youtube.com/kasparsdambis
5. Photo: Maurizio Pesce, https://flic.kr/p/emnk9K
6. Use AI to Help You Write Better Code Computers
7. Use Computers to… Check code for errors Check code formatting and style Test if 1+1=2
8. Use Computers to… Is this supported in PHP 5.3 and PHP 7.2? Does it work with WordPress 5.0 and Jetpack 5.0? Does the JS & CSS work in IE 8? Does it impact the page load time?
9. But How?
10. Start Small!
11. Use a Good Text Editor Atom PHPStorm SublimeText
12. Use a Good Text Editor Atom
13. Use Version Control
14. –User Support Request “All images are broken in the latest version of the plugin! Fix it ASAP!111” Use Version Control
15. Use Version Control
16. Use Version Control
17. Use Version Control Everyone uses Git WordPress uses Subversion (SVN) for plugins and themes
18. Use Git Hooks Runs scripts and checks before every commit! Commit only working code BONUS
19. Use Git Hooks BONUS .git/hooks/pre-commit
20. Use Git Hooks BONUS $ git commit -m "Fix user not found" PHP Parse error: syntax error, unexpected '}', expecting ';' in modules/custom-post-types- taxonomies/module.php on line 27 Errors parsing modules/custom-post-types- taxonomies/module.php
21. Use a Package Manager Composer for PHP dependencies npm for project dependencies
22. Use Node Package Manager
23. Use Node Package Manager $ git clone https://github.com/kas...org.git $ npm install
24. Use GitHub
25. Use GitHub A remote backup for your code Invites contributions Supports Continuous Integration
26. Use GitHub with Travis CI
28. Use Code Linters
29. Use Code Linters https://github.com/squizlabs/PHP_CodeSniffer
30. Use Code Linters http://jshint.com
31. Use Code Linters Also available in the “Cloud”
32. Use Code Linters
33. Use Coding Standards Silicon Valley TV Series
34. Use Coding Standards Developers Who Use Spaces Make More Money Than Those Who Use Tabs https://stackoverflow.blog/2017/06/15/developers-use-spaces-make-money-use-tabs/
35. Use Coding Standards • Tabs or spaces for indentation? • Single or double quotes? • Closing PHP tags? • Braces or no braces for one-line conditionals?
36. Use Coding Standards https://make.wordpress.org/core/handbook/best-practices/coding-standards/
37. Use Coding Standards phpcs.xml
38. Use Coding Standards linter-phpcs Atom package
39. Use Coding Standards linter-phpcs Atom package
40. Use EditorConfig
41. Use Automated Testing 1 + 1 = 2
42. phpunit.xml Use Automated Testing
43. A very simple PHPUnit test Use Automated Testing
44. Use Automated Testing
45. Use Automated Testing A very simple QUnit test
46. Use Automated Testing
47. Use a Virtual Environment
48. Use a Virtual Environment
49. Use a Virtual Environment Varying Vagrant Vagrants (VVV) https://varyingvagrantvagrants.org Good for WP core development Can’t run two boxes at the same time
50. Use a Virtual Environment http://docs.chassis.io One WP install per virtual box Quick!
51. Use a Virtual Environment
52. Use a good text editor Use Git for version control and hooks Use a package manager Use GitHub for continuous integration and accepting contributions Use code linters (checkers) Use coding standards Use automated testing Use virtual development environment
53. Only a mock-up wptide.org
54. Kaspars Dambis kaspars.net Lovely robots 
 designed by Freepik http://www.freepik.com