Hopefully, you have one of those friends who has your back, who will step in and stop you from making a really, really stupid mistake. Because we all are fallible and whether it be in a moment of rage, or just because we are in a rush, we will make mistakes.
This is why I have PHP Lint added as a pre-commit hook on my PHP Project repos. It only takes a minute to set it up and will have you a ton of time, and headache in the future.
First, you need to make sure you have PHP Lint installed on your system. If you are a PHP developer, then the chances are you have it.
Next go to you PHP project .git directory and add the following code to the file .git/hooks/pre-commit
And that should be it. Now every time you do a commit on some PHP code, your git workflow will send each file through the PHP Linter to check for errors. See the example below
Most editors will show you when you make an error, but we are rushing and don't notice that we forgot to add a semi-colon.
We add the file and attempt to do a commit but because of the hook, Git will refuse to commit the files, and we can sleep easier at night knowing we can't accidentally send broken code to our repo.
One thing to note, this git hook will only parse the files you are committing and not the entire project. Meaning if you have a co-working was not doing linting, and you pull in their changes but don't touch the file, your commit will not catch it.
I've been using Vim for years, and I have built up a lot of muscle memory. I also have a few Vim plugins I feel like I can not live without, which also have their key bindings. From time to time, I will play with another editor but only if it offers Vim bindings in some form or fashion, typically it comes in the way of a plugin. Usually, these are lacking a great deal, and it's not long before I am back in native Vim.
One exception to this rule has been PHPStorm. The Ideavim plugin was very complete. That, coupled with a ton of built-in features and a few other plugins like Relative Line Numbers and AceJump I found myself able to get the PHPStorm IDE very close to my native Vim.
This is mainly due to Ideavim's approach which mimics the .vimrc file. Ideavim has the .ideavimrc file which allows you to map custom mappings just like .vimrc but does have some limitations.
In my .ideavimrc file, you will notice several mappings that take advantage of an :action command. The 'action' is a command gives you access to any command within PHPStorm, including commands added by other plugins. With this, I can mimic several commands from my regular .vimrc file that use plugins such as the mappings I have for Fugitive.
It's not a seamless replacement for native Vim, there are a few things that annoy me, and I will switch back to native Vim for development from time to time, but Ideavim gets PHPStorm closer than any other tool and makes working in PHPStorm relatively easy.
When you heard that phrase in the 80's, you knew things were about to get funky. However, in the coding world, dealing with dates and time can be a real pain. I did a presentation for our Laravel User Group about a package that I enjoy called Carbon which makes working with dates and times a ton easier.
If you know me, you know I am a sucker for a good framework. Doesn't matter the language I am using, I will typically look for the hottest framework on the platform when I start a project.
In my primary development world of PHP, that framework had been cakePHP for a very long time. I had tried several others, but none of them stuck with me like cake did, that was up until a few years ago when a friend with our San Diego PHP User Group started pushing another framework on me called Laravel.
In that time, I've taken the Laravel framework further that I have any other including starting a development group that specializes in the framework. As typical, when I do something I like to submerge myself totally in it, and it wasn't too long before I found myself running a User Group for the Laravel framework.
During that time, I've had the opportunity to speak with a few of the key members of the Laravel community. The following two videos are interviews I did with Taylor Otwell (@taylorotwell) who is the creator of the Laravel Framework. The second video in my interview with Jeffrey Way (@jeffrey_way) who I consider the head educator for Laravel. Enjoyed talking with both these guys. They were super friendly and very, very accommodating.
First up is Taylor Otwell, the creator of Laravel. Great discussion with him.
This is Jeffrey Way's video, we had some major auto problems this night, sorry about that. We were able to mute everything when Jeffrey speaks. Also, the video should start at about the 15-minute mark. Everything before that is just some typical User Group meeting stuff.
User groups, or UG for short, are awesome. People passionate about some sort of speciality who get together to share and learn from each other. I personally belong to several UGs but there is one that gets more of my attention than the others and that is our local PHP UG. There are several reasons for this, I am passionate about PHP but more importantly I am one of the organizers of this group which just goes by SDPHP.
One fun thing to check out with other UGs is to see what they came up with for a logo. This sounds simple but coming up with a good meaningful logo is tough. These are some examples of my favorite logos from various PHP User Groups. This is by no means a complete list and I may find myself adding to it over the next couple months but if you happen to have a PHP UG Logo you like, feel free to reference it in the comment section.
Now in no particular order, ok expect for the first one, here are some of my favorite PHP UG Logos.
Right off the bat I am going to do some shameless self promotion of my group SDPHP. I designed this logo and we've been using it for a couple years now and I am still not tired of it.
Next on my list is the San Francisco PHP UG, SFPHP. It's very creative and you can tell they put some time into this one.
Like SFPHP, Seattle PHP User Group managed to work the PHP ElePHPant into their logo which is not something I was able to do.
UPHPU / MNPHP Utah PHP and Minnesota PHP User Group both use nice circular logos. They look like they would make a great patches.
OCPHP Orange County PHP kind of speaks for itself. Simple and representative of their local.
Just wanted to post a link to a really good article on Tech Companies in San Diego and leveraging talent across the border in Tijuana.
I worked for a group that had a very similar business model, it was a little different as the majority of its clients were also based throughout Mexico. I worked with them in their San Diego office with a group of very talented developers, ops, and office staff from both sides of the border.
We did manufacturing in Mexico, a little deeper than Tijuana, and I have to agree with the article in that one of the biggest advantages was being able to quickly iterate through design and components. There is something to be said about being able to travel to manufacturing, discuss with the different teams involved, and pivot if needed.
I would also travel to Tijuana to meet with my tech team who managed IT systems in our Tijuana offices where customer support and designers worked. As I mentioned, in our San Diego office we had developers, graphic artist, office staff, and operation team members who made the journey across the border every day. All very talented people.
I think Baja California is positioned to become one of the next strong draws of IT talent. The skills sets and IT culture south of the border is growing stronger and stronger as the IT generation there are maturing and finding themselves in the workforce. I am hoping as more Tech companies realize this, they also decide to make San Diego their US home.