The biggest complaint people have about object-oriented design is where they put all the “glue code” that ties together a bunch of objects and makes them work well. For many, this place is the controller, but as I’ve covered before, most of this logic belongs in the model. In fact, the model should be where all business logic resides. And yet, it can still seem difficult to figure out precisely how to manage all of these behaviors in one place and still follow the best practices of object-oriented design and development.
But there is a way to accomplish this that won’t make you crazy. It’s accomplished by making use of “services” – bits of code that act as the “glue code” for all the different objects that have to operate.
Tuesday, May 5th, 2015 @ 8:00 am | Comments (0) | Categories: Uncategorized, Best Practices, Object-Oriented Development, PHP
At SunshinePHP in January, Elizabeth Naramore gave a talk on how GitHub uses GitHub internally for projects that may or may not involve code. For example, all requests for sponsorship are turned into issues, which are tracked, tagged and labeled.
After this talk, I decided to create repositories for the purpose of tracking bugs in my books. The idea was that I would have a place to track the issues, and that readers would be able to file their issues with the books in a place that most of us are familiar with using and interacting already. No writer is perfect, and no book is published without bugs, so it seemed like a win for everybody.
Wednesday, August 20th, 2014 @ 12:44 pm | Comment (1) | Categories: Uncategorized
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!
Friday, February 15th, 2013 @ 12:40 pm | Comment (3) | Categories: Uncategorized
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.
Wednesday, September 19th, 2012 @ 7:58 pm | Comment (2) | Categories: Uncategorized
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.
Thursday, August 16th, 2012 @ 7:00 am |
Comments (0) |
Categories: Uncategorized, Technology
Tags: pilot, playdoh, private pilot, instrument rating, ifr, logging, flight time logging, training, flight logging, hours, Mozilla, pilot in command, flight, pic, flight training, django
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.
Wednesday, March 7th, 2012 @ 7:00 am | Comment (17) | Categories: Uncategorized
|« Older Entries||Newer Entries »|