A Startup Story - Geekcamp Presentation
0 likes495 views
This document summarizes the development timeline and approach of Gameplan, a startup building a sports tournament platform. It describes key milestones from April to September including the first public demo, free preview launch, and beta launches. It then discusses the company's working philosophy of top-down development, just-in-time building, and feedback loops. Pair programming is used when possible. The document emphasizes common sense over buzzwords and having user traction, profits, and happiness over great code alone. It advocates testing assumptions through failure and success and provides tips on dry testing a product and not taking advice too literally.
A Startup Story - Geekcamp Presentation
- 1. A Startup Story Arun Thampi @iamclovin Co-Founder of Gameplan http://gameplanapp.com
- 2. The Gameplan Story So Far • April 1 - Begin Work Code LOC: 5210 • June 1 - First Public Demo at Echelon 2010 Test LOC: 12500 • July 5 - Free Public Preview goes live Code-To-Test Ratio: 1:2.4 • July 17 - Tournaments private beta goes live • July 28 - Tournaments public beta goes live • Sept 1 - Paid Plans Launched
- 3. Disclaimer • Need not apply to a startup building the next Google, Facebook, Twitter or Wego. • But then again it’s not supposed to. • If you follow advice wholesale without thinking about what it means to you, you are doing it wrong.
- 4. Buzzword Soup Pair Programming TDD Scalability Agile BDD NoSQL Scrum
- 5. BULLSHIT
- 6. The Only Acronym You Need Common Sense Driven Development
- 7. Your Startup’s Aim No Yes Great Code Traction Great Test Coverage Happy Users Prettiest Website Profit An architecture to challenge Happy Investors / Owners Google
- 8. Gameplan’s Working Philosophy • Top-Down Approach • Think in terms of URLs, links, forms and flow • JIT Building • Feedback Loops • Pair Programming (whenever we can)
- 9. Start Off with a Feature (We use Cucumber) Feedback Loop The View URLs, Links and Forms Controller Test Controller Code Model Test Model Code
- 10. Pair Programming • A piece of the puzzle • Getting Stuck • Riding through bad days (the World Cup wasn’t too helpful) • Distractions • We are pragmatic about it • Nine-to-Six working hours to avoid burnout
- 11. The Startup Story Getting Traction, Users, Profits and Hustling Product & Engineering
- 12. STARTUP == ASSUMPTIONS
- 13. Make Assumption Test Assumption Failure Success Modify Assumption & Great! Repeat
- 14. var value_of_idea; value_of_idea == 0; // => true
- 15. JFDI
- 16. Dry Testing is dead simple • Create Landing Page • Google Ads • Hacker News • Forums • Twitter
- 17. Don’t take advice too seriously • Including mine • Use as a starting point and make your own path • Nobody can teach you to live your life • Nobody can teach you to run your startup
- 18. Thank You