The document outlines essential principles for technology development in early-stage startups, focusing on choosing the right tech stacks and best practices for efficiency and performance. It emphasizes factors such as code reusability, support for multiple languages, learning curves, productivity, community support, testability, debuggability, and documentation quality. Additionally, it highlights potential pitfalls in understanding requirements and performance concerns, using PayPal's experience as a cautionary tale.

1. Technology Development in
Early Stage Startup
By Yodi

2. I’m a
Programmer

3. What is HOT today?

4. techstacks.io

5. Frontend, Backend, Mobile, Data-
Engineering

6. stackoverflow.com

7. stackoverflow.com

8. stackoverflow.com

9. stackoverflow.com

10. stackoverflow.com

11. stackoverflow.com

12. stackoverflow.com

13. It is important for businesses to adhere to the
best practices and choose the right platforms
to get the job well done.

14. Principle
• DRY: how DRY is the the technology? is there support
for code-reuse and partials?
• i18n: is there support for translations and multiple
languages?
• Hot reload: are changes visible immediately or is there
a compile/deploy cycle?

15. Principle
• Performance: how long does it take to render in the
browser and server?
• Ramp-up time: how is the learning curve?
• Ramped-up productivity: once you've ramped-up,
how fast can you build things?

16. Principle
• Server/client support: can support both client-side
and server-side?
• Community: is there an active community using this
project? Can you google issues?
• Library agnostic: are there dependencies on other
libraries?

17. Principle
• Server/client support: can support both client-side
and server-side?
• Community: is there an active community using this
project? Can you google issues?
• Library agnostic: are there dependencies on other
libraries?

18. Principle
• Testable: how hard is it to write unit and integration
tests?
• Debuggable: is it possible to step through the code
while it's running to track down errors?
• Editor support: is there an editor with auto-complete,
syntax highlighting, error checking, etc?

19. Principle
• Maturity: is this a relatively stable project or still
experimenting and churning?
• Documentation: how is the documentation?
• Code documentation: do the software
encourage/require documentation/comments?

20. Principle
• Maturity: is this a relatively stable project or still
experimenting and churning?
• Documentation: how is the documentation?
• Code documentation: do the software
encourage/require documentation/comments?

21. In Summary?

22. Fast, Easy and Documented

23. StackBehind

27. Kargo Stack

29. Technology Development

30. Planning
(Asana, Trello)
Development
(Github, IDE)
Deployment
(EC2,
PlayStore)
Testing
(Selenium)
Ticketing
(Trello, Jira)

31. Pitfall

32. • Don’t understand the requirement
• Too worried about performance
• Following the hype

33. After they merged with X.com, the new CEO wanted to
switch to Windows—even after PayPal cofounder Max
Levchin showed that their software scaled only 1% as
well on Windows as Unix. Fortunately for PayPal they
switched CEOs instead.
PAYPAL

34. Thank you