Slides from 0-60 in startup technology fro

1. 0-60 in Startup Tech Monday June 6th Daniel Doubrovkine @dblockdotorg http://code.dblock.org dblock@dblock.org

2. Startup Founders Job: Dream It Carter

3. You (ME) Technical Co-Founder Head / VP of Engineering Lead Developer Job: Build This

4. WEEK ZERO: Day One What will you do? “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. -Me”

5. DAY ONE: CODE NAME Create an Identity Version 0.1 Job: Build This “Gravity”

6. Day Two: A Place to DOCUMENT Hosted by a 3rd Party Free or Cheap Private Share Backup Data http://stackoverflow.com/questions/143321/best-hosted-wiki-solution-for-private-wikis

7. Day THREE: A Place FOR PROCESS Create Tasks Assign Tasks Start Tasks Complete Tasks + Basecamp + Redmine

8. Process Grow this way >>>>>>>>> #FAIL

9. Day 4 and 5: ACQUIRE Knowledge Domain Driven Design Taxonomy Specs People

10. DAY 5: DDD/SME/KB

11. Concluding Week Zero Scheduled exciting meetings with other startups Created a place to write information, a team wiki Created a KB and a way to create new knowledge Created a place to manage and track work. … I feel like we forgot something important …

12. Concluding Week Zero

13. Week 1, Day 1: A Plan Story: “Users can sign-up for beta” ETA: EOW Breakdown: ?

14. Week 1, Day 1: A Place to Put Code + TFS + Mercurial (HG)

15. Week 1, Day 1: Peer Code Reviews Peer review of every check-in Shared knowledge Shared responsibility It’s common to push back

16. Week 1, Day 1: Your First Commit Getting Started

17. Week 1, Day 2: a Friendly Visit Bring Pastries Tell Your Story Be Impressed Ask “Why?” at Least 3 Times Owe One

18. Week 1, Day 3: Pick a Technology Your and Your Team’s Experience Other People’s Experience The Cutting Edge Learn Something New

19. Week 1, Day 3: Choose a Stack

20. Week 1, Day 4: Implement “Users can Sign-Up” Test-Driven Development Unit Tests Integration Tests System Tests Regression Tests Acceptance Tests

23. Week 1, Day 5: Demo Day Team Wiki, KB, PM Demo! Demo! Demo! Story: “Users can sign-up for beta” Developers know how to get started. Developers can commit code with a peer code review. Every time a developer checks in code, continuous integration runs tests and e-mails results to the team. Every time continuous integration executed tests successfully, a developer can push the code to a staging environment.

24. How fast are we going? TGV

25. A 2 and a 3 Week Sprint Stories are user-facing, always Under-promise, over-deliver Focus on making developers happy Don’t build technical debt Best management is one that nobody notices

26. Hiring People make all the difference. There’re excellent developers who are a bad cultural fit. There’re bad developers who are an excellent cultural fit. Hiring via open-source.

27. How fast is 60 days? http://www.youtube.com/watch?v=kDd9vlnqRuo&feature=related E-Mail: dblock@dblock.org Tech Blog: http://code.dblock.org < Slides Here http://iwny.co < Recorded Sessions Twitter: @dblockdotorg