• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
2011 04-20 0-60 in startup technology
 

2011 04-20 0-60 in startup technology

on

  • 639 views

Slides from 0-60 in startup technology fro

Slides from 0-60 in startup technology fro

Statistics

Views

Total Views
639
Views on SlideShare
639
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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 2011 04-20 0-60 in startup technology Presentation Transcript

  • 0-60 in Startup Tech
    Monday June 6th
    Daniel Doubrovkine
    @dblockdotorg
    http://code.dblock.org
    dblock@dblock.org
  • Startup Founders
    Job: Dream It
    Carter
  • You (ME)
    Technical Co-Founder
    Head / VP of Engineering
    Lead Developer
    Job: Build This
  • 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”
  • DAY ONE: CODE NAME
    Create an Identity
    Version 0.1
    Job: Build This
    “Gravity”
  • 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
  • Day THREE: A Place FOR PROCESS
    Create Tasks
    Assign Tasks
    Start Tasks
    Complete Tasks
    + Basecamp
    + Redmine
  • Process
    Grow this way >>>>>>>>>
    #FAIL
  • Day 4 and 5: ACQUIRE Knowledge
    Domain Driven Design
    Taxonomy
    Specs
    People
  • DAY 5: DDD/SME/KB
  • 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 …
  • Concluding Week Zero
  • Week 1, Day 1: A Plan
    Story: “Users can sign-up for beta”
    ETA: EOW
    Breakdown: ?
  • Week 1, Day 1: A Place to Put Code
    + TFS
    + Mercurial (HG)
  • Week 1, Day 1: Peer Code Reviews
    Peer review of every check-in
    Shared knowledge
    Shared responsibility
    It’s common to push back
  • Week 1, Day 1: Your First Commit
    Getting Started
  • Week 1, Day 2: a Friendly Visit
    Bring Pastries
    Tell Your Story
    Be Impressed
    Ask “Why?” at Least 3 Times
    Owe One
  • Week 1, Day 3: Pick a Technology
    Your and Your Team’s Experience
    Other People’s Experience
    The Cutting Edge
    Learn Something New
  • Week 1, Day 3: Choose a Stack
  • Week 1, Day 4: Implement “Users can Sign-Up”
    Test-Driven Development
    Unit Tests
    Integration Tests
    System Tests
    Regression Tests
    Acceptance Tests
  • Week 1, Day 4: Continuous Integration
    Build and run tests with every check-in
    E-mail the team.
    • Hudson / Jenkins
    • TeamCity
  • Week 1, Day 4: Continuous Deployment
    Dev
    Staging
    Production
    Demo
  • 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.
  • How fast are we going?
    TGV
  • 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
  • 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.
  • 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