Shipping products in a start-up environment

Presented during a guest lecture for the "Software development in start-ups" course taught as part of the Computer Science MSc curriculum at Radboud University.

More from me about business and technology.

Transcript

1. shipping software in a start-up environment @joelcox joelcox.nl
2. shipping software in a start-up environment @joelcox joelcox.nl
3. shipping products in a start-up environment @joelcox joelcox.nl
4. product vs. software
5. use a product sell a product maintain a product evolve a product
6. what about a start-up?
7. hint: not this photo by al abut
8. constrained by money constrained by time constrained by team
9. constrained by money constrained by time constrained by team enabled by technology?
10. “Uber, the world’s largest taxi company, owns no vehicles. Facebook, the world’s most popular media owner, creates no content. Alibaba, the most valuable retailer, has no inventory. And Airbnb, the world’s largest accommodation provider, owns no real estate.” – Tom Goodwin
11. who are you and why are you telling me this? graduated in 2014 freelance (lead) software engineer works for small start-ups
12. technology
13. not as relevant as you might think…
14. stack based on market
15. stack based on market talent
16. stack based on market talent domain
17. technology + methodology
18. should you do scrum tdd devops ci?
19. it depends…
20. build for tomorrow not next year
21. class AbstractSubscriptionPaymentProviderServiceFa
22. future performance is something for the future
23. development speed over safety destroyallsoftware.com/talks/wat
24. greenfield will soon be brownfield
25. quality allows for agility
26. bureaucracy when needed
27. todo in progress done
28. todo in progress ready for review done needs improvement
29. shared understanding = less documentation
30. team
31. small team, large ambitions
32. t-shapes T
33. t-shapes T generalist specialist
34. “We often have to pass on people who are very strong generalists without expertise, or vice versa. An expert who is too narrow has difficulty collaborating. A generalist who doesn’t go deep enough in a single area ends up on the margins, not really contributing as an individual.” – Valve: Handbook for new Employees
35. software engineers computer scientists
36. software engineers computer scientists
37. software engineers computer scientists
38. hit the ground running
39. html css sass cross-origin resource sharing node.js ember.js ajax json d3.js local storage json-api git icon fonts @font-face npm bower broccoli ember-cli handlebars.js foundation coffeescript a+ promises
40. time
41. m v p
42. minimal viable product
43. minimal viable product ≠ software
44. fast good cheap
45. “The purpose of a self-imposed deadline is to sharpen the edge of your prioritization sword and stake a flag of coordination for the team. […] It’s a voluntary constraint on scope.” – David Heinemeier Hansson
46. add value first don’t start building a login system
47. many (potential?) platforms little time
48. restful api ios app web app 3rd party identity service attachment service timeline service
49. nih-syndrome don’t fall for
50. you are not that special
51. new and shiny stuff don’t fall for
52. innovators early adopters majority laggards
53. stability without stagnation
54. build ship improve
55. #protips
56. tinker!
57. be pragmatic
58. learn to understand business
59. learn to understand business designers
60. learn to understand business designers marketers
61. learn to understand business designers marketers users
62. fin @joelcox joelcox.nl