Qcon london2012 recap

1,033 views

Published on

my quick recap of 3 talks @ QCon London

Published in: Technology, Business
1 Comment
1 Like
Statistics
Notes
  • Thx. Cool thoughts about 'documenting trade offs'.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,033
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide
  • Click toaddnotesPeter Gfader recapQconLondon 2012
  • Click toaddnotesPeter Gfader recapQconLondon 2012
  • Itisalways a trade offKompromisse
  • Was sind die Vor und Nachteile von colocated und verteilt?
  • Knowthetradeoffs!
  • Many weeks went into thisThis is not allowed to shareEvery time Silverlight comes out we confirm
  • Advise: influence decision made by the team
  • Silverbullet: solve a problemwith 1 shot. Promisetoimprove a business
  • having same architectureforeverysystemisgood?genericarchitecturemeansnothing
  • Qcon london2012 recap

    1. 1. #qconLondon 2012 Recap
    2. 2. What?• qconlondon.com• 2 days: tutorials• 3 days: conference• Recordings online @ infoq.com In the next 6 months• London!
    3. 3. What?• 1200 devs• „VIP“s o Martin Fowler o Greg Young o Dan North o Rebecca Parsons o Rich Hickey o Jim Webber o Zach Holman o Ade Oshineye
    4. 4. 3 days full onhttp://gfader.tumblr.com/Recap of best talks
    5. 5. The bad news
    6. 6. There are no best practices
    7. 7. „There are no best practices“Dan North
    8. 8. What is your context?
    9. 9. Trade offs!You get somethingYou loose something
    10. 10. SampleTeams co-located or distributed
    11. 11. SampleDevelopment WPF or Windows Forms
    12. 12. SampleDevelopment automated or manual build
    13. 13. Trade offs!It is always a trade off Know the trade offs
    14. 14. „Trade Off Game“
    15. 15. Trade offs!Know the tradeoffs
    16. 16. Trade offs!Know the tradeoffs Decision
    17. 17. You cant take an informed decision without knowing the tradeoffs
    18. 18. What should we do?
    19. 19. #1 Know the tradeoffsSeek advicePlay the „Trade off game“
    20. 20. #2 Document Trade offsAnd Decision!
    21. 21. Document Trade offsEveryone involvedTransparencyShare decisionShare responsibility
    22. 22. No „silver bullet“
    23. 23. „Scrum is not a Silver bullet“ http://www.controlchaos.com/message-from-ken/
    24. 24. Silver bullets?Scrum, Silverlight, .NET, WinRT,WCF, Scala, Java, Kanban, Cloud,ContinuousDelivery, HTML5, SOA,WPF, Lean, SharePoint, SOAP,Collaboration, Automation,SixSigma, WinForms, RUP,JavaScript, …
    25. 25. Be aware!People seek for Silver Bullets!
    26. 26. Be aware!Someone talking about a silver bullet?
    27. 27. Be aware!Someone selling a silver bullet? It might be a vendor
    28. 28. #1 Know the Trade offs  Play the Trade off game
    29. 29. #1 Know the Trade offs  Play the Trade off game#2 Document Decisions (incl. Trade Offs)
    30. 30. #1 Know the Trade offs  Play the Trade off game#2 Document Decisions (incl. Trade Offs)#3 There are no Werewolves Silver Bullets
    31. 31. Thank you!!http:// gfader.tumblr.com/http:// blog.gfader.com/
    32. 32. SampleArchitecture monolith or single components
    33. 33. SampleTechnologies Silverlight or HTML+JS
    34. 34. SampleDevelopment style automated or manual testing
    35. 35. SampleTeams small teams or big team
    36. 36. SampleDevelopment style No branching or branch by feature
    37. 37. SampleArchitecture company wide standard or each project different

    ×