10.Oct.2009 at 13:25 by Ben Longden
Yeah ok. Not bad.
I'm sure you could have picked a more flattering pic though :-D
Tools and Talent
Rowan Merewood (10.Oct.2009)
Talk at PHP North West 2009 (English - UK)
A development environment is a pretty personal choice, but when you’ve got over twenty developers all working on the same codebase, you need to start deciding on some standards. You need to find the options that aid your productivity, rather than restrict you with unnecessary overhead. Plusnet has been running its business on PHP for over a decade now, and over that time we’ve used a mixture of home-grown tools and off-the-shelf solutions. Some of these have stuck, some have had teething troubles, and others just haven’t caught on at all. We’ll look at the choices we’ve made for the tools that support us throughout the development process, including version control, unit testing, debugging, quality metrics, bug tracking and, of course – actually writing code. Alongside the obvious technical merits of choosing a particular tool there are other factors to consider such as licensing, community support, industry standards, performance, security and so on.
However, you can’t just throw all these tools at your developers and hope that bullet-proof code comes out the other end. You need to look at how you can trial your new choice, prove that it works, and then integrate it into your development process – and this needs to happen without just stopping your business at the same time. This might involve creating new processes to take advantage of the tools you’ve chosen, or alternatively you might be migrating from an existing tool to an improved option.
All of this is purely theory without someone to champion the cause, forcing a tool from the top-down is never as effective as having your developers wanting to adopt it themselves. You need some evangelists in your organisation who can play the role of salesman, mentor, and technical expert. We’ll use a few case studies to see the experiences our developers have been through in finding a tool they wanted to use, convincing the rest of us of its value, and then how they went about getting it adopted. Through this we’ll pull together the theory and the practice to give you a solid plan for successfully incorporating a new tool into your development process.
Quicklink: https://joind.in/614
Who are you?
By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.
If the claim is approved you will be able to edit the information for this talk.
Are you sure?
Comments
10.Oct.2009 at 22:38 by Jordan Hatch
Very good talk and some good practices there to know for future reference :)
11.Oct.2009 at 11:23 by Mark Baker
A well presented talk on how to choose and implement new tools in the development cycle with a minimum of disruption or members of the team feeling they're being forced into it, and how to get the best benefit from their use.
The emphasis on the processes involved made it very relevant to managing a development team.
The ghostbusters references made it amusing - though I didn't see Slimer in the list at all.
11.Oct.2009 at 18:13 by Rob Mills
good talk, well presented, with good analysis into best practices we should all follow.
11.Oct.2009 at 18:13 by Elliot Ward
Great illustration of the steps for dropping new tools and working practices into an organisation. And the analogy ramped up the accessibility.
"We got the tools, we got the talent!" - Winston Zeddemore.
11.Oct.2009 at 20:19 by Paul Lemon
Good talk and great to get some insight into another dev team and their working (and drinking) practises.
13.Oct.2009 at 13:44 by Michael Nolan
Nicely delivered and interesting to get an insight into another organisation's approach to deploying new tools.
14.Oct.2009 at 13:39 by Peter Spain
A great talk and an important subject for many I am certain. Well delivered.
10.Oct.2009 at 12:52 by Dave Nattriss
Good reinforcement of stuff we should already know/practise