As developers, we’re always looking for ways to make sure that the code that we deliver to our customers is as error-free as possible. There are lots of ways that we can do this but most developers tend to rely on manual and automated testing.
Manual testing is flawed because we constantly have to redo our tests manually. Automated Tests are more efficient because it’s automatically done which can save us huge amounts of time. The downside is that they require a non-trivial amount of effort from the developers to create them off.
There’s a third option that’s generally overlooked as a way to improve our code’s quality requiring just a little extra effort on our part. That’s using static code analysis. In this article, we’ll discuss what static code analysis is and why we should be using it on every commit.Read More
Laravel 9 was released on 2/8/2022 and in this article, we’ll describe how to update our applications from Laravel 8 to Laravel 9.
If you’re upgrading from a previous version make sure you check out our article on how to upgrade to Laravel 8. You’ll have to upgrade through each version one at a time.Read More
When we’re connecting to remote servers it’s important to make sure our connection is secure but it can be annoying to have to type in our passwords over and over again. Thankfully we have a whole suite of tools that will help us access a remote terminal and move files securely.
In this article, we’ll discuss how to connect to our Unix-based servers using a Secure Shell connection without passwords.Read More
The annoying thing about deleting data from a database is that it’s gone forever. We can’t even look at the data to see if we needed it because it’s gone. If we need the data back, our only solution will be to restore a backup and hope we have the backup just before it was deleted so the loss is minimized.
Thankfully, Laravel provides a built-in feature that allows us to flag database rows as deleted without actually deleting them from the database. This article/video discusses how to use Soft Deletes in Laravel.Read More
One of the hardest parts about shipping code is working on a large feature while other developers are working on the same portions of the code. There are two ways that we can do this.
The first is that we can create a branch in our revision control software and develop the whole feature in the branch over several weeks or months. Every day we’ll want to merge in the changes that others are making so we have our code up to date. The annoying part of this process is that we’re going to get stuck merging in other developers’ changes because they’re unaware of how our changes are affecting the same code. These long-lived branches tend to be hard to merge back into the main branch and are a headache for all involved.
The second method is to develop small changes that take no longer than a day or so to create and are constantly being merged into the main branch. It makes our job much easier. The downside to this is that we then have to hide the new feature from our users until it’s ready to be deployed.
In this article we’ll explain how to use feature toggles to do just that.Read More
Vagrant makes it easy to go from zero to working in a very short time. We can feel free to completely wreck our setup because we can reset it back to a working state. The flip side to this is that while it’s easy to reset our VMs it might be a challenge or time-consuming to recreate our data inside the VMs.
What if there was an easy way to take a snapshot of our current VMs drive state so we could quickly get back to it?
In this article we’ll talk about how to use Vagrant’s snapshot feature to do just this.Read More
subscribe via RSS