Following the release of the phpspec SpecBDD tool, Konstantin Kudryashov has posted this new article talking about SUSes ("Subject Under Specification") and how they relate to the functionality phpspec offers.

First of all, phpspec2 is not a testing framework. It's a SpecBDD tool. It means, testing is not our primary aim. Tool's job is to enforce and make SpecBDD in project flawless and phpspec2 uses all available methods to do that - state of the artformatters, class and method generators and lot of othe fancy buzzwords :) Today, i want to explain you the heart of phpspec2 - SUS, collaborators and prophets.

He starts off defining specifications as a list of behaviors about how an object should behave and the abilities that come with them (like "getTitle"). He shows assertions, like "shouldReturn", and how you can use Collaborators to evaluate the interfaces between objects.

In this new post to reddit.com the question is posed, "is it better to be an expert or all-arounder in web development?"

Is it better to be an Expert in a framework like Zend (a certified Zend Developer) or know a little bit about everything. [...] In sum, it's just taking too much time for me to master Drupal, Magento, and other popular CMS/Frameworks. So I'm wondering if I should just specialize is one framework/CMS.

Most of the comments follow along the same idea - it's good to be an "all-arounder" and know several different technologies, but it's also good to be an expert (or as close as you can) in one or more technologies. As one comment puts it:

In my experience, it's best to have a specialty, but not have a too narrow focus. There's a lot going into a web site - programming, design, usability, marketing, economy, etc. Understanding a number of those fields makes it easier to work with other people.