Learn to Code: SXSX 2012
1 like3,224 views
The document discusses learning to code and develop software, emphasizing that it's not as difficult as it seems. It provides resources for learning Python/Django, Ruby on Rails, and HTML/CSS, encouraging individuals to seek help and collaborate on open-source projects. The authors also share a high-level overview of a user request handling process in an application.
Learn to Code: SXSX 2012
- 1. Learn to Code and Make the Software You Want Nate Westheimer Vinicius Vacanti SXSW March 11, 2012
- 2. Nate Westheimer Vin Vacanti Picturelife, Co-Founder Yipit, Co-Founder @innonate @vacanti http://innonate.com http://vacanti.me
- 4. The Big Secret It’s not that hard
- 5. What Does it Take? “The Sweat Lodge”
- 6. The High-Level User Request: “http://yourdomain.com/actions?details=number_two” Server: “Yo app! I got this request. Check it...” Your App: “Sweet! Going to do some magic. Here’s the result.”
- 7. Don’t Worry About • Security • Scaling Issues • Writing Beautiful Code • Maintainability of Code
- 8. Learning Python/Django http://tech.yipit.com
- 9. Learning Ruby on Rails http://railstutorial.org/ http://railscasts.com/
- 11. Need Help?
- 12. Help Yourself
- 13. Still Need Help?
- 14. Just Ask
- 15. And Share
- 17. What Did We Build?
- 18. What Did We Build?
Editor's Notes
- #2: \n
- #3: \n
- #4: - It’s not about being smart, it’s not about having studied computer science, it’s not about being good at math. There’s only one prerequisite: You have to want something to be built.\n
- #5: - For both of us, it was about building something we wanted to exist\n
- #6: - For both of us, it was about building something we wanted to exist\n
- #7: - For both of us, it was about building something we wanted to exist\n
- #8: - What if you want to switch databases? No!\n
- #9: \n
- #10: - What did Nate use?\n
- #11: - Twitter Bootstrap\n- Chrome “Inspect Element”\n
- #12: \n
- #13: \n
- #14: \n
- #15: - What did Nate use?\n
- #16: - What did Nate use?\n
- #17: - Great way to see how pro’s structure their code\n
- #18: - What did Nate use?\n
- #19: - What did Nate use?\n