All work and no play makes it hard to justify hobbies that look too much like your career.
I value my ability to contribute to the work of others far more than my ability to mandate how they use my contributions.
Applications that used to fit in a few megabytes now consume a gigabyte – or more – to do essentially the same thing. I find this development a bit disturbing.
Determining which methods in your application needed testing used to be easy – test everything exposed by the public API. But once you invite other developers to contribute, you are exposing a whole other set of internal APIs to the team. The behavioral consistency of these methods is just as important as that of the public API, so shouldn’t you be testing them too? I would argue you should, even if this internal API consists of private and protected methods. To make life easier, I’ll give you a couple of tools for testing these limited-visibility functions without forcing everything to be declared “public.”
Please also review my follow-up post, Making Singletons Safe in PHP. There has been a lot of discussion this week regarding the Singleton pattern and whether or not it has a place in modern software development. Mike Schinkel wrote a tutorial about a Singleton factory. I wrote one about using Singletons as a WordPress plugin […]
One of the most widely recognized social media applications in the world today is Facebook. People use it for everything from email to event planning to entertainment. You can manipulate your profile to display every detail of your life or nothing. You can build an online profile to represent yourself in any fashion you want […]