Ruby on Rails or PHP? MySQL or MongoDB? Java or C#? Heroku or Amazon? Will this scale? Will it perform? With so many options, it's hard to make decisions about which technology to use to build and deploy your next web idea or application, difficult to convince others and risky to trust someone else to make these decisions for you. In this course you will learn how to approach this problem, discover the essential vocabulary of technology stacks and learn which questions to ask. This class is equally suited for both a technical and a non-technical audience and will focus on the decision-making process using some real world examples of modern technology start-ups. http://choosingtechnology.eventbrite.com/

1. CHOOSING Technology Tuesday July 5th @dblockdotorg #gachoosingtech @ gnrlassembly Daniel Doubrovkine - http://code.dblock.org-dblock@dblock.org

2. Building SOFTWARE unlike building _________________

3. Problem domain

4. what is IT going to do? Who is going to use it and how? What stories will it tell?

5. Choosing technology TRADITIONAL APPROACHES

6. stack a stack that works a stack that worked

7. STACK: Ruby on Rails Backbone.js Rails +60 gems Ruby MongoDB Heroku + addons AWS (S3, Cloudfront)

8. STACK: LAMP Zend Django PHP Python Apache MySQL Linux Rackspace

9. Stack: J2ee JAF JTA JM IDL JTS JSP JS RMI XML JMS JDBC JNDI EJBs Java JVM Windows

10. What do stacks do? Help You Focus on The Domain Classify Problems Offer Generic Solutions Provide Consistent Experience Map Software Evolution Reuse Skills

11. Data storageeasy choice

12. Business logicimpossible choice

13. SCALABILITY Effort to Provide Service with More ________ Users Traffic Data Calculations Unit of Scale

14. complexity Number of Moving Parts Time to Rebuild from Scratch Developer Bus Factor

15. COST People + Time + $ for ________ Minimum Viable Product Hosting and Storage Features and Bugs Operations

16. Choosing technology doesn’t have to be boringLESS TRADITIONAL APPROACHES

17. Developer happiness Developers Are Happy with ______ Their Own Choices Cutting Edge Technology

18. Bullet proof logic It Worked For Me Before It Didn’t Work for Me Before It Sounds Exciting ______ Uses It

19. Choosing technology doesn’t have to be a science Personal approach

20. Pragmatic Try It … Iterate … Keep It … Toss It Easy to Learn Frustration-less Quick to Leverage Vibrant Community Elegant Solutions

21. Did YOU make a good choice? Good Technology Choices Help Developers Focus on the Problem Domain

22. IS it time to reset? Reset Early, Several Times Rational Thinking Kills Companies Incremental Rewrites Take Forever Think “Startup”

23. QUESTIONS? name: Daniel Doubrovkine(aka. dB.) company: http://art.sy twitter:@dblockdotorg blog:http://code.dblock.orglink to slides here email:dblock@dblock.org