This is an interesting look at how we use casing in our code. In his blog post Brendt argues that snake case is more readable than camel case. I particularly like this point that he makes:-

Readable code, reduces cognitive load. Less cognitive load means more memory space for humans to think about other things, things like writing business logic.

I’ve always preferred camel case over snake case, but I think that has been for purely aesthetic reasons over how easy they are to read.

A simple little trick in PHP for when you need to make sure that a value doesn’t drop below zero. For example, you might be subtracting a discount from a basket total and not want the amount to be paid to become negative.

Earlier today I got caught out by an interesting little issue when using env() to access environment configurable values on a deployed Laravel app. Despite having read through the documentation I managed to completely miss the caveat on using this function whilst caching the app’s configuration.

Constants are named values that do not change. You’ve probably used them many times to set a value that you want to persist throughout your codebase. In this short post I’m going to look at a couple of ways we can use them to improve our code. We’ll look at how they can be used to reduce bugs and make our code more readable.

A look at automating NPM and Composer when checking out new branches and pulling from a remote Git repository using Git hooks.