Our code base has a lot of code that looks like this: <?php try { $this->doScaryThing(); } catch(Exception $e) { trigger_error("Downgraded: " . get_class($e) . ":" . $e->getMessage(), E_USER_WARNING); } Or sometimes trigger_error is used as a way to log other thigns. This makes it rather difficult to test. Thankfully PHPUnit 8.4 has the expectWarning method, that allows us to check this: <?php public function testItTriggersWarning(): void { $object = new Danger(); $this->expectWarning(); $object->doWarningThing(); } This does mean that the execution stops after the warning is triggered, so we can’t assert anything after that.

Our code base is a lot like a camp site, and we can learn a thing or two from the boy scouts.

Most code bases have far too much comments, while only a few are really usefull.

PHP is already strictly typed, in the same way that JavaScript is. Not through the language itself, but with the help of tooling. JavaScript achieves this through tools like Typescript. (I use typescript as an example, as that is what i normally use.) Typescript adds a lot of new syntax to tha language, which allows for type checking. The transpiler then simply won’t transpile if there are type errors( depending on your configuration).

The tools a modern PHP developer needs to strive.

Using static analysis to find bugs, and it only takes a few seconds.

Using static analysis to find bugs, and it only takes a few seconds.

Using static analysis to find bugs, and it only takes a few seconds.

Using static analysis to find bugs, and it only takes a few seconds.