It has been my ever-faithful companion for the last three years, but now sadly the time has come to part ways with my old MacBook Pro. The only reason I’m selling is that I need longer battery life on occasion. The machine works fine, and I’ve just fitted it with a 500GB HDD (taken from my new MBP; sorry, but I’m keeping my SSD 🙂 ). The outer casing’s finish is worn in one spot; not bad considering this machine has been with me all day every day for the past three years.Be the first to leave a comment »
Are you going to PHPNW09? Are you interested in my two day course on how to organise a team of PHP developers? Do you still want to go, but missed the early bird tickets?
Then keep an eye on your inbox … there’ll be an email from the PHPNW09 organisers in the next day or so including a discount code you can use to buy tickets for my course at a nice reduction.Be the first to leave a comment »
Stuart is running a course in Manchester in October immediately before the PHPNW09 conference on how to setup and organise your PHP developers to ensure things run smoothly for you and your customers, which will include looking at how to get the most out of Trac. Learn more about the course, or sign-up now.
When it’s just you, working on one project at a time, it’s easy enough to keep track of the work you’re doing and the work you still need to do to complete the job. Chances are you can keep it all in your head, or at least keep the discussions with your customer on something like Basecamp in your head. You know that you should be using source control and bug tracking because it is “best practice”, but it just seems like too much of an overhead to bother with when it’s just you. After all, you’re working on the customer’s server, and there’s no-one else editing the code anyway.
Some of the folks reading this blog post might be cringing at that, but I’ve lost count of the number of times I’ve come across professional PHP developers who work in exactly this way. Is it because they don’t know better? Maybe. Is it because it has worked okay for them up to now? For sure.
But eventually, there comes a point where one developer becomes a team of two … or more. Having a team means that you can go after larger projects … but it also means that you have to go after larger projects to pay the team. Larger projects mean more complicated requirements, multiple phased deliveries … and a larger, more demanding (and probably a more complicated) customer holding the pay cheque.
Running a team of PHP developers (like all management activity in all walks of life) comes down to three key things: direction, organisation, and supervision. Only now it isn’t just you and a customer, just a list that you can keep in your head. Now you need to keep track of a larger list, of multiple lists for multiple people to work on that need to be brought together in the end, and if anything slips through the cracks it’s your reputation on the line. Getting the customer to come back for repeat business just got a lot less easy to take for granted.
Trac and Subversion have been part of our community’s toolkit for many years now. Used correctly, you can get yourself and your customers well-organised, and grow your reputation when you grow your team. If you haven’t started using them yet, both are open-source, and well-backed with plenty of information freely available around the blogosphere on how to use them.
Or join me in Manchester in early October, where I’ll show you how they fit into an overall approach to running your team of PHP developers.Be the first to leave a comment »
At work, we have quite a variety of kit that we use for development:
- Cheap and cheerful desktop machines w/ multiple monitors and plenty of RAM, normally with AMD CPUs. These machines mostly run some form of Linux … Ubuntu and Debian are both popular.
- Various laptops, a fair mix of MacBook Pros and other kit running Linux.
- Virtual machines running on the desktops and laptops, used for cross-browser testing.
- Virtual machines running on HP servers and blades, used for system testing, release testing and production.
It gives us a lot of flexibility, allows us to develop and test on standards-compliant environments (but still use Windows for testing IE), and most of the time the developer is the bottleneck not the equipment 🙂 Recently, I’ve added both a netbook and an Atom-based mini-itx machine into the mix, and this blog post is my attempt to recommend that you consider doing the same.
Netbooks are incredibly popular in the wider computer-owning population. Over here in the UK, they come free with many mobile broadband packages, making them cheaper than many low-end laptops. They’re sold in the supermarket and the high street. Their small form factor and relative lightweight makes them appealing to people who would never willingly cart a traditional laptop around. And they run Windows, which most people are familiar with.
After an initial explosion of innovation, the specs have settled around a 1.6GHz Atom processor, 1 GB of RAM and a 10″ 1024×600 resolution screen. That’s not a lot of power, and it isn’t a lot of screen estate. How do your websites look on a netbook? Does your home page or your landing pages make an impact at that size, or is your site’s message partially or completely below the fold? How do the rest of the pages look? If you’re creating an app, does the user have enough of a working area to comfortably do their tasks? Try using Google Reader or Zimbra on a netbook to see examples of what to avoid.
Testing on a netbook is one way you can spot and deal with these problems before your customers do.
Stuart is running a course in Manchester in October immediately before the PHPNW09 conference on how to setup and organise your PHP developers to ensure things run smoothly for you and your customers. Learn more about the course, or sign-up now.Be the first to leave a comment »
On Zend’s DevZone, Remi Woler recently talked about his experiences as a judge for the WinPHP contest organised through the Dutch PHP User Group and the Dutch PHP Conference. One of his closing remarks really stood out for me, where he was expressing his surprise at how few people participated: “I refuse to believe there are only a couple of dozen PHP developers in Europe.”
It’s an odd statement … the world and his dog knows that PHP is immensely popular over here in Europe. Perhaps Remi completely overlooked the Windows factor here?
- I’ve been running a series of polls looking to learn more about the wider PHP community. One of the things that comes out of those polls is that 15% of developers use Windows as a platform, but only 3% are using Windows for their production platform.
- At this year’s PHP UK Conference in London, Microsoft’s Hank Jansen (who heads up their open-source efforts) spoke in the main room. I wasn’t able to attend personally, but by all accounts his talk was not well-attended. Not only aren’t people using Windows, but the curiosity doesn’t seem to be there either.
- Most hosting services (and practically all shared hosting services) are Linux based. If you want to host your site on Windows Server, there are plenty of firms offering this as an option, but many of these services are beyond the budget of many PHP projects.
My personal experience over the years is that many developers work in PHP on Windows because they’re working on laptops … and Linux on laptops continues to be a very hit-and-miss experience sadly. (They should all buy Macs instead 😉 ) About half of the larger corporations I’ve worked with in the UK prefer Windows Server because Linux skills are rare in their organisation, but these corporations were also reluctant to use PHP-based solutions, still wrongly seeing PHP as a hobbyist language compared to .NET or Java.Be the first to leave a comment »
October in Manchester is home to the PHPNW09 conference. Last year’s conference was a great event, and this year’s promises to be even better. And I’m not just saying that because I’m a conference sponsor this year, honest 🙂
Immediately before the conference, I’m running a two day tutorial in the fundamentals of setting up and running a team of PHP developers, covering:
- Keep your promises to your customers using written specifications
- Organise your team using Subversion and Trac
- Control quality using code reviews
- Deliver to your customers using release management and follow-up support arrangements
- Where to go after the course for additional learning
Earlier in the year, before PHP 5.3 was released, I asked the community a series of questions about their attitudes towards moving to PHP 5.3, and had a fantastic response. I’m going to turn all of those answers into a new conference talk that I’m working on.
Now that PHP 5.3 has been around for a few months and we’ve started seeing plenty of blog posts covering all the new features in PHP 5.3, I’m wondering whether or not you have actually moved to PHP 5.3 yet. I’m especially curious to see how this compares to what people said they’d do before it came out 🙂
Please vote on twtpoll to let me know if you have moved to PHP 5.3, and if not, what’s still stopping you. Many thanks in advance!Be the first to leave a comment »