PhpSpec is enjoying a growth in popularity lately, probably related to the recent release of 2.0. Lots of people have been playing with it and trying to get to grips with what it can do. Naturally they try to do the same things they would with other testing tools. Soon they find out they can’t. “Oh! This PhpSpec has so many limitations… I can’t do this… I can’t do that…”. Ironically, other people make positive comments about the same “limitations”. So I decided to publish a list of my top ten favourite limitations of PhpSpec, and why I love them so much.
Kacper Gunia, a software engineer for Sensio Labs UK, and Certified Symfony Developer, gave a talk at the London Symfony Meetup on the adverse effect of resource-intensive tasks, leading to an underwhelming user experience, affecting performance and even uptime, and potential loss of revenue. However, there are a variety of strategies to overcome this – one being queueing. In this video, Kacper takes a look at RabbitMQ – what it is, how it works, and how to use it with a Symfony2 application to aid scaling.
Read more →
Feedback on performance matters. It not only maintains quality, refines and hones performance, but it can also improve morale and trust, and build relationships. It can stop minor problems from escalating into major capability issues. It’s something that every people manager or team leader should be doing as standard, and yet it’s so hard to get right.
For some people, giving good feedback is easy. They have no problem telling their team what a fantastic job they have done. They may do this regularly throughout the course of a project, or just at official times during appraisals or probation reviews. Some managers may simply overlook to give feedback at all, particularly where they assume the team member knows how well they are doing. The not-news flash is that people don’t telepathically know they’re doing well or badly. They might assume that any problems would be flagged, but is the assumption that all feedback will be bad, really what you want? Read more →
Paweł Jędrzejewski, creator of Sylius, explains why he adopted full-stack Behaviour-Driven Development (BDD), how it can work for open source projects, improve communication and its applications for customer projects.
Paweł was speaking at the latest London Behat Users meetup, a community event that aims to share best practice and advice for implementing Behat and BDD. For the full list of upcoming events, sign up at http://www.meetup.com/LondonBehatUsers/