Walking with Developers      ILI, 30/October 2012Track A - Rethinking Technology           Session A102        Stephanie T...
How to turn developers from this -
To this…
What you DON’T need -• A technical background• An ability to write code• A knowledge of every possible technology that  co...
What you DO need -• An ability to clearly describe what you want  something to DO
Start with a workflow• Think through & describe the steps of how  something should work
Then draw up your requirements• Make a list of what you need the technology  to do• Note any specific standards the techno...
Let everyone do what they do best• You know best what you want to be able to do  with a tool• Let the developer(s) sort ou...
Talk The Same Language• Be very clear about what you both mean.
Be Flexible• You don’t have to understand all the technical  details, you just need to be able to understand  how somethin...
The Hardest Things Of All• It’s your call in the eternal time versus  perfection battle• Let the developers get on with it...
And don’t forget…• Development teams need regular supplies of  kittens, coffee, cake & beer                   Thankyou!
Image Credits• Slide 2 - http://www.flickr.com/people/infomofo/• Slide 4 – http://www.flickr.com/people/gamerchick02/• Sli...
Upcoming SlideShare
Loading in...5
×

S taylor ILI 2012 Presentation

1,247

Published on

'Walking with Developers' a short presentation on working with developers in the library & information sector.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,247
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "S taylor ILI 2012 Presentation"

  1. 1. Walking with Developers ILI, 30/October 2012Track A - Rethinking Technology Session A102 Stephanie Taylor Critical Eye Communications criticalstepht@gmail.com
  2. 2. How to turn developers from this -
  3. 3. To this…
  4. 4. What you DON’T need -• A technical background• An ability to write code• A knowledge of every possible technology that could be used
  5. 5. What you DO need -• An ability to clearly describe what you want something to DO
  6. 6. Start with a workflow• Think through & describe the steps of how something should work
  7. 7. Then draw up your requirements• Make a list of what you need the technology to do• Note any specific standards the technology will need• Note any systems or other technologies the new technology needs to interact with• Any other important things it needs to do
  8. 8. Let everyone do what they do best• You know best what you want to be able to do with a tool• Let the developer(s) sort out exactly how this is done – that is not your problem
  9. 9. Talk The Same Language• Be very clear about what you both mean.
  10. 10. Be Flexible• You don’t have to understand all the technical details, you just need to be able to understand how something might impact on your workflows to make a decision.• Keep talking- it’s about teamwork.
  11. 11. The Hardest Things Of All• It’s your call in the eternal time versus perfection battle• Let the developers get on with it – trust their expertise
  12. 12. And don’t forget…• Development teams need regular supplies of kittens, coffee, cake & beer Thankyou!
  13. 13. Image Credits• Slide 2 - http://www.flickr.com/people/infomofo/• Slide 4 – http://www.flickr.com/people/gamerchick02/• Slides 5, 6, 8, 9, 10 & 11 – http://www.flickr.com/people/laurie_pink/• Slide 12 - http://www.flickr.com/people/tragically_dork/• All images used, with thanks, under CC BY-NC-SA 2.0 http://creativecommons.org/licenses/by-nc- sa/2.0/deed.en
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×