Object oriented PHP can be a struggle. It’s complicated, difficult, abstract, obtuse. You fight. You end up with a headache. You wish there was an easier way to learn object oriented PHP.
Ever since releasing Mastering Object Oriented PHP in December, PHP developers have had an easy and straightforward way to learn how to write better object oriented PHP. It is possible to write better object oriented PHP; Mastering Object Oriented PHP can help!
Like many people, I upgraded my iPhone to iOS 6 this afternoon. The update for me wasn’t all that exciting, being that I’m on the Death Star network, but it was still worthwhile to upgrade for the Do Not Disturb features.
Shortly after updating, it seems that the wifi connectivity stopped working for me, as well as for lots of other people all over the world. Many people got a screen, similar to what they see when they log in on a wireless network that requires payment or agreement to certain terms and conditions. It appears that whatever URL the iPhone utilizes to determine whether or not connection to the outside world is established was returning a 404 error – not what the iPhone expected, and thus resulting in the display of the Log In screen.
Every pilot works hard to maintain good records of their flight time. Besides being expensive to obtain, the FAA requires that flight time of a certain nature be logged and available for inspection, should it ever be required or questioned. The pertinent regulation gives a description of what information must be logged, but leaves the method up to the individual pilot.
Being a bit of a technologist, I wanted a system for logging flight data that would give me maximum flexibility for manipulating the statistics. And so, my own version of an online flight log was born. I built it using Playdoh, Mozilla’s Django-Plus framework. The application is a very simple CRUD application, but it’s not the input of data that’s interesting; it’s the way it’s displayed.
Back in September, Socorro received a security bug relating to the method we were using for processing inputs for the duration of certain reports. The vulnerability included a proof of concept, with an alert box popping up on production when the link was followed.
By now, most if not all of us have seen the graphic images from UC Davis, where students were pepper sprayed at point blank range by two officers of the campus police force. These images have become more and more commonplace in our society, which is quite sad. The news seems more and more consistently filled with stories of police actions that cross the boundaries of what we might consider acceptable, and the reality is that technology has made it easier to catch these officers “in the act.” But what is terribly heinous is not the actions themselves (though they are); it is the systematic setting of internal policies that allow these activities to take place – and often, go unpunished.
A few months ago, I had the privilege of serving on a jury. The case was simple: a single misdemeanor charge of disorderly conduct. The facts were equally simple: the defendant, after walking out of a bar, was struck by another man who had just left a different bar. Bouncers from the second bar immediately forced the assailant into the parking lot, and made sure that the defendant was alright. After a few minutes, he proceeded to the parking lot to get his car; the assailant again assaulted him. The defendant this time defended himself; he easily overpowered the assailant and by the time the police arrived, had the altercation well in hand.
In the past few days, the alarm has been sounded in the technology community for us to help defeat the Stop Online Piracy Act (SOPA). This legislation, while well-intentioned, is crafted in such a way that it would give private companies the power to shut down other private companies, and require the government and Internet Service Providers (ISPs) to initiate a system for DNS blocking and domain seizure. The law’s vague language and powerful provisions combine to create a law that has the power to shut down sites like Facebook, Twitter and YouTube – or more realistically, the next generation of Facebook, Twitter and YouTube. This isn’t hyperbole, it’s real.
A number of technology companies are banding together to defeat this legislation. Mozilla is one of those companies. Yesterday, the House Judiciary Committee held a hearing on SOPA, which I had the privilege of attending along with James Socol and Alex Fowler. Following the hearing, James and I paid visits to several members of the Judiciary Committee, meeting with a number of staffers and talking about Mozilla’s (and our personal) opposition to this bill. It was a great experience in hands-on involvement in the government, and I’m proud of our efforts.