2011 04-20 0-60 in startup technology

723 views

Published on

Slides from 0-60 in startup technology fro

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
723
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Does the site say “we’re in beta, sign-up here”?Can a user enter his e-mail address and is it written into a database?Does the user see an error when he clicks ok without an e-mail address?
  • 2011 04-20 0-60 in startup technology

    1. 1. 0-60 in Startup Tech<br />Monday June 6th<br />Daniel Doubrovkine<br />@dblockdotorg<br />http://code.dblock.org<br />dblock@dblock.org<br />
    2. 2. Startup Founders<br />Job: Dream It<br />Carter<br />
    3. 3. You (ME)<br />Technical Co-Founder<br />Head / VP of Engineering<br />Lead Developer<br />Job: Build This<br />
    4. 4. WEEK ZERO: Day One<br />What will you do?<br />“Dear ___,Saw your excellent presentation at ___. I liked the Q&A and learned a bunch of new things.I have a favor to ask. I’ve joined a NY startup, ___. We’re just starting, and I am hoping to do things ‘right’ from the start. I was wondering whether I could borrow someone’s time at ___ next week (yours or someone who works for you) and maybe bring 1-2 people with me to see how your code and tooling is organized.<br />-Me”<br />
    5. 5. DAY ONE: CODE NAME<br />Create an Identity<br />Version 0.1<br />Job: Build This<br />“Gravity”<br />
    6. 6. Day Two: A Place to DOCUMENT<br />Hosted by a 3rd Party<br />Free or Cheap<br />Private<br />Share<br />Backup Data<br />http://stackoverflow.com/questions/143321/best-hosted-wiki-solution-for-private-wikis<br />
    7. 7. Day THREE: A Place FOR PROCESS<br />Create Tasks<br />Assign Tasks<br />Start Tasks<br />Complete Tasks<br />+ Basecamp<br />+ Redmine<br />
    8. 8. Process<br />Grow this way >>>>>>>>><br />#FAIL<br />
    9. 9. Day 4 and 5: ACQUIRE Knowledge<br />Domain Driven Design<br />Taxonomy<br />Specs<br />People<br />
    10. 10. DAY 5: DDD/SME/KB<br />
    11. 11. Concluding Week Zero<br />Scheduled exciting meetings with other startups<br />Created a place to write information, a team wiki<br />Created a KB and a way to create new knowledge<br />Created a place to manage and track work.<br />… I feel like we forgot something important …<br />
    12. 12. Concluding Week Zero<br />
    13. 13. Week 1, Day 1: A Plan<br />Story: “Users can sign-up for beta”<br />ETA: EOW<br />Breakdown: ?<br />
    14. 14. Week 1, Day 1: A Place to Put Code<br />+ TFS<br />+ Mercurial (HG)<br />
    15. 15. Week 1, Day 1: Peer Code Reviews<br />Peer review of every check-in<br />Shared knowledge<br />Shared responsibility<br />It’s common to push back <br />
    16. 16. Week 1, Day 1: Your First Commit<br />Getting Started<br />
    17. 17. Week 1, Day 2: a Friendly Visit<br />Bring Pastries<br />Tell Your Story<br />Be Impressed<br />Ask “Why?” at Least 3 Times<br />Owe One<br />
    18. 18. Week 1, Day 3: Pick a Technology<br />Your and Your Team’s Experience<br />Other People’s Experience<br />The Cutting Edge<br />Learn Something New<br />
    19. 19. Week 1, Day 3: Choose a Stack<br />
    20. 20. Week 1, Day 4: Implement “Users can Sign-Up”<br />Test-Driven Development<br />Unit Tests<br />Integration Tests<br />System Tests<br />Regression Tests<br />Acceptance Tests<br />
    21. 21. Week 1, Day 4: Continuous Integration<br />Build and run tests with every check-in<br />E-mail the team.<br /><ul><li>Hudson / Jenkins
    22. 22. TeamCity</li></li></ul><li>Week 1, Day 4: Continuous Deployment<br />Dev<br />Staging<br />Production<br />Demo<br />
    23. 23. Week 1, Day 5: Demo Day<br />Team Wiki, KB, PM<br />Demo! Demo! Demo!<br />Story: “Users can sign-up for beta”<br />Developers know how to get started.<br />Developers can commit code with a peer code review.<br />Every time a developer checks in code, continuous integration runs tests and e-mails results to the team.<br />Every time continuous integration executed tests successfully, a developer can push the code to a staging environment.<br />
    24. 24. How fast are we going?<br />TGV<br />
    25. 25. A 2 and a 3 Week Sprint<br />Stories are user-facing, always<br />Under-promise, over-deliver<br />Focus on making developers happy<br />Don’t build technical debt<br />Best management is one that nobody notices<br />
    26. 26. Hiring<br />People make all the difference.<br />There’re excellent developers who are a bad cultural fit.<br />There’re bad developers who are an excellent cultural fit.<br />Hiring via open-source.<br />
    27. 27. How fast is 60 days?<br />http://www.youtube.com/watch?v=kDd9vlnqRuo&feature=related<br />E-Mail: dblock@dblock.org<br />Tech Blog: http://code.dblock.org < Slides Here<br />http://iwny.co < Recorded Sessions<br />Twitter: @dblockdotorg<br />

    ×