There’s a lot going around right now about Facades. Laravel introduced the concept, or at least the term, to the PHP community in their framework. Given the popularity of the term, it’s worthwhile to define what a Facade is, and what a Facade is not.
The definition of a Facade
Any web developer writing PHP applications is eventually going to have to store user passwords. Most developers have at least learned that storing a password in plain-text isn’t secure, but for many of us, we still use insecure methods.
The problem is, that if our web application is ever hacked, insecure password hashing algorithms will make it simple, easy and quick for attackers to break our passwords.
At SunshinePHP two weeks ago, lots of people asked me about my object oriented PHP classes and future training opportunities. With that in mind, I wanted to share that I am offering two new training opportunities early next month.
Object oriented PHP is really hard for a lot of people. These classes are designed to break apart these complex concepts into simple, easy-to-understand bits. Each six hour class will include you actually working on code, helping to cement these concepts for future use.
This summer, several PHP developers (myself included) will be embarking on a 16-city speaking tour called The Crafting Code Tour. This multi-state, multi-country event is designed to bring great outside speakers to user groups around the United States and Canada. Today, I’m pleased to announce the dates for The Crafting Code Tour!
We’ll be visiting the following locations on the following dates:
When a discussion thread on the PHP user group leader’s list started up about the cost and potential for outside speakers, most people generally agreed that user groups have a hard time wrangling outsiders to come and speak. The cost of travel is prohibitive, and small user groups often have trouble getting the funds necessary to bring in someone from far away. The internet surely brings us closer together, but there’s still no substitute for the in-person speaker who can share knowledge and experiences, plus a beer or two.
This challenge of bringing in outside speakers prompted an idea. What if, instead of organizing one speaker for one user group, we could organize a tour of speakers to travel to multiple user groups? What if, instead of expecting the user group to pay the expenses, we sought the help of those who care the most for the community? What if, instead of one speaker bearing the burden of travel, we distribute it to many speakers, each having a small role to play in the overall event?
My last day at Mozilla was yesterday. I will surely miss it.
Most jobs I’ve had experienced only a two week resignation period, during which I wrapped up my projects and usually had some tension with those left behind. I was always moving on to something better (and I am in this case, too, but “better” is different in this sense), and they knew it. When the Vice President of Engineering thinks those who don’t live in the office are not dedicated enough to the company, most people wish to move on. And they resent the lucky few who do.
But Mozilla is different. Between the six week notice period (to finish up my goals) and the fact that I actually LOVE Mozilla, leaving was more like a slow, painful death than a quick, jubilant exit.