List Engineering Skills
0 likes890 views
The document instructs teams to list their engineering skills to ensure they only build projects using technologies they are already proficient in. It recommends teams focus on a domain where they have strong skills, as attempting to learn new technologies in a 6-month period could lead to poor performance. Teams are asked to submit a spreadsheet listing founders' names and skill levels in various technologies and domains to assess their strengths and weaknesses.
![Technology
Domain
Founder 1
Name
Founder 2
Name
Founder N
Name
Web Good Beginner Beginner
Android App Great Good Beginner
iOS App
Awesome. See:
[URL]
Great Beginner
[Other Relevant
Domain]
… … …](https://image.slidesharecdn.com/tt13-listengineeringskills-161220224250/85/List-Engineering-Skills-16-320.jpg)
List Engineering Skills
- 2. List Engineering Skills Vishnu Gopal
- 3. List your teams’ Engineering Skills
- 4. Why?
- 5. Because: you should only build using what you already know.
- 6. Why?
- 7. Because in 6 months, there is not enough time to learn something new.
- 8. Example: if your team is not skilled at Android development, don’t attempt an app.
- 9. Example: if your team has never built a web app, do not attempt a complex web app.
- 10. From our past experience, teams that break this rule spend a lot of time learning the technology, and less time building …
- 11. … Leading to poor performance in the batch.
- 12. Build using what you already know.
- 13. So first, list what you know.
- 14. Format to list:
- 16. Technology Domain Founder 1 Name Founder 2 Name Founder N Name Web Good Beginner Beginner Android App Great Good Beginner iOS App Awesome. See: [URL] Great Beginner [Other Relevant Domain] … … …
- 17. Also write down your insight in your timeline entry or as part of your submission.
- 18. Insight = new learning, action items or other todo tasks. All because you performed this task.
- 19. Insight pointers: if your team is weak in all areas, how will you proceed?
- 20. Insight pointers: if your team is strong in one area and weak in another, which technology domain will you focus on?
- 21. Insight pointers: does your technology domain influence your business domain? How?
- 22. Don’t forget to check the Rubric for pointers.