In 1990 Tim Berners-Lee invented the World Wide Web. He developed the first web server, web browser and web page. This web browser, the world’s first, was called WorldWideWeb (all one word to distinguish it from the World Wide Web).
Tim created the WorldWideWeb browser at CERN in Switzerland on his NeXT computer (a product of Steve Job’s company during his years away from Apple). This browser worked as both a viewer and editor of web pages. It only ran of NeXT machines and as a result was only grayscale (a limitation of the computers’).
It’s almost thirty years since Tim gave us the web and the first web browser. A group of developers and designers came together at CERN recently to rebuild Tim’s browser so that we can experience the web as it first was from the comfort of a modern browser. Compared with today’s browsers it is very simplistic, but it is fascinating to see how it all began.
PHP 7.3 was released at the end of last year, but for many of us working with the latest version of PHP is not an option for a while. We are often restricted by the servers that we have to deploy to which can often be a version or two behind.
This means that for many, the new features of PHP 7.3 will remain out of reach for some time. If this describes your situation then this post is for you. We’ll look at four things you can start doing now that will help make it easier to migrate your code to PHP 7.3 when the time finally does arrive.
With the arrival of PHP 7.3 last month came some interesting changes to the existing heredoc and nowdoc syntaxes. However, not everyone I spoke to even new that this syntax existed in PHP, so now seems like a good opportunity to take a look at what they are and how to use them.
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.
A tutorial on getting started with PayPal’s REST API using PHP and MySQL I wrote recently for Evoluted’s Think Tank.