jQueryTO 2013 - Creating a Development Culture
•
1 recomendación•1,686 vistas
From jQueryTO, held in Toronto March 2-3 2013, my talk on creating a stronger developer process and culture within a mixed team
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (16)
Similar a jQueryTO 2013 - Creating a Development Culture
Similar a jQueryTO 2013 - Creating a Development Culture (20)
Más de Monika Piotrowicz
Último
Último (20)
jQueryTO 2013 - Creating a Development Culture
- 1. / Creating a Development Culture
- 2. Monika Piotrowicz Front End Developer, Jet Cooper @monsika 2
- 3. We design and build products for web, mobile and tablet devices 3
- 4. People we work with We’ve had an opportunity to work alongside leading Canadian startups, brands, and organizations 4
- 5. Today What we’re doing today
- 6. Process A process exists to support creativity, not resist it 6
- 7. Disclaimers 1. This is only our approach 2. This is difficult 3. Will never be perfect, just better for now 7
- 8. Good conference, right? But what happens Monday? 8
- 9. Why does this happen? Don’t go stop chasing Waterfalls 9
- 10. Design Development 10
- 11. Discovery Production Design Development 11
- 12. Discovery Production Design Development 12
- 13. != short order cooks We’re problem solvers too, dammit! 13
- 14. Changes We need to keep up with them 14
- 15. 15
- 16. Ideas We need a way to share them 16
- 17. (we didn’t pose for this, I swear) 17
- 18. Designers We want to work with them 18
- 19. Image Credit: Cassie McDaniel 19
- 20. Time for a change Inside and outside of projects 20
- 21. Devs inside projects Changing the way we build together
- 22. A new approach Killing the “stagger” 22
- 23. Discovery Production Design Development 23
- 24. Discovery Production Design Development 24
- 25. 25
- 26. So uh, what now? Two new opportunities 26
- 27. 1. Your new best friend Surprise, it’s the designer! 27
- 28. Levelling the playing field A more collaborative approach to design 28
- 29. 2. Research & Prototype The chance to actually learn about and implement the new things that interest you 29
- 30. Your sandbox The freedom to focus on one problem at a time 30
- 31. Form and function Prototypes can be as bare bones or complex as we want 31
- 32. 32
- 33. 53 33
- 34. Your future self will thank you The earlier an assumption is challenged, the easier it will be to fix 34
- 35. 35
- 36. Drive the design Your code is your chance to create a concept 36
- 37. 37
- 38. Share & iterate Design informs development Development informs design 38
- 39. Design FED Iteration 39
- 40. Devs in the company Organization-wide activities
- 42. Developer meetings Keep up to date with what the other developers have been up to 42
- 43. Recess!!! Self-directed research, prototyping, and internal side projects. Bring lessons back to process 43
- 44. Lessons Learned It’s a lot to implement, but a strong developer culture can bring a lot of benefits
- 45. What we gain 1. We make more informed decisions 2. Time is reduced and quality increases 3. Happy developers, yay! 45
- 46. Ok so what? How can you get the ball rolling for your team?
- 47. Talk to your designers Your ally, because no one wants to design in the dark 47
- 48. Become an Advocate Talk about the benefits of a strong developer team, Don’t just vent, have meaningful discussions 48
- 49. Take the first step Even if it’s on your own time, the results will speak for themselves 49
- 50. Fix the process Let’s create a stronger stance collectively