The document discusses important considerations for choosing a technology stack. It recommends focusing innovation on business solutions rather than the latest technologies. It advises picking platform defaults, familiar technologies, and the best tool for the job rather than personal preferences. The key factors outlined are innovation points, platform defaults, familiar technologies, and pragmatism. An example technology stack is given that uses Rails, Ruby, OpenOffice, and Python.

1. SV.CO
Technology Stack

2. Why is this important?

3. The technology stack is
the foundation of your
engineering work.

4. + it’s very hard to
revise these choices.

5. So choose wisely.

6. Four important
considerations before
you choose.

7. 1: Innovation Points

8. Spend your innovation points
solving business solutions
not on picking the
“latest” and “hottest” technology.

9. Choose Boring
Technology

10. Choose Boring Stable
Technology

11. 2: Pick Platform
Defaults First

12. Pick technology that your
platform provider
endorses

13. React Native
versus
Android Java or iOS Swift

14. 3: Pick Familiar
Technology

15. Do not learn a new
language/framework/tool
for your work at SV.CO

16. This is not an research project.
The focus is always
on building something that
real customers will use.

17. 4: Be Pragmatic

18. Pick the best tool for the job.
In some cases, don’t pick the tool
that you personally like or know.

19. Frontend
(accepts
uploads)
Backend
(offline job
processor)
Tool
(to convert PPTs
to Flash)

20. Frontend
(accepts
uploads: Rails)
Backend
(offline job
processor:
Ruby)
Tool
(to convert PPTs
to Flash:
OpenOffice)

21. Frontend
(accepts
uploads: Rails)
Backend
(offline job
processor:
Ruby)
Tool
(to convert PPTs
to Flash:
OpenOffice)
Glue
(OpenOffice
Connector:
Python)

22. Hacky.
Hacks are OK.

23. Task: submit a
one-pager describing
your technology choices.

24. Describe:
- Programming Langauge(s)
- Frameworks
- Libraries
- Database
- Tools

25. Finis: Questions?