It has only been a year, but I’m making a return to the world of freelancing.
For those of you that don’t know, I’ve been working for CleverCherry for the last year (well, a year as of yesterday). It has been a wonderful year and a wonderful experience. I’ve made some friends along the way and I’ve thoroughly enjoyed being a part of their team. I handed my notice in some two months ago and my final day of employment will be the 3rd November, followed by a week of me relaxing, and then it’s back into it again.
The reason for my decision to return to the world of freelancing is that in all honesty, I miss it. After four years of being my own boss it’s hard to get used to situations where I don’t have the say, and for those that know me, I have a problem with that most the time as it is. On top of that, I miss the sort of work I did when I was in London. Don’t get me wrong, I’ve worked on some really interesting things while with CleverCherry, but I’ve always been a fan of functionality driven applications.
As of the 13th of November I will be available for freelance projects and contracts alike. I’m also, as always, open to employment should an opportunity turn up on my desk that I absolutely cannot turn down. If you’re looking for a freelance developer to build your app, or a contractor to bolster your team, get in touch over at Ollie’s Lab.
On a side note, this hopefully means that I’ll have time to actually write articles and work on some of my open source projects!!!
It has been while (almost two years) since I wrote an article here and I’ve decided to make my triumphant return with an article I never managed to get around to writing.
As the title may suggest, this article is about streamlining validation with Laravel. While the final aim is to explain and present you with a quick and simple abstracted validator that requires minimal code in the actual implementation stage, before we get there I will need to cover the usual methods of validation which are default validation, form request validation and model validation. So let’s start.
So about a week or so ago I found myself started a few projects, some for clients and some personal. While I doing this I noticed that I was copying and pasting a lot of basic classes and configurations that I use in almost everyone of my projects, so I decided to create myself a toolkit to use with my projects. My choice was an annoying composer configuration connecting to private repositories, or just making it a public repository with a package on packagist, so naturally I went with the second option. You can find the package here, and the repository here.
As I stated above, the idea behind this was to provide myself with a simple toolkit for us in my projects, to save myself duplicating code and having the modify multiple files if I fix a bug or make improvements. That being said, it’s available for others to use should they wish for a basic toolkit, or would like a basis to build their own. With that in mind, I’ve decided to write this article with some further information regarding it.
For those of you that frequent the Laravel irc channel on freenode, you may have been witness to a recurring conversation surrounding Laravel routing, namely, using http methods other than POST & GET, and the use of Route::controller() & Route::resource(). Well this article plans to cover those bases as well as some added fun regarding Laravel routes, that may help.
User authentication is a huge part of web applications, with it being necessary in the majority of cases, on top of which, it’s usually the first part of any system that a developer will approach, or at least it should be. Laravel is a powerful, easy to use framework that provides you with the basic tools to create a simple ACL to suit your needs.
I am aware that there are many packages for Laravel that offer this functionality, but I find them often to be more complicated than necessary. In this article I will detail how to create a simple yet highly customisable ACL using the basic tools that Laravel ships with.