Hack 101 at IIT Kanpur
Download as PPTX, PDF•0 likes•1,717 views
This document provides guidance for participants in a hackathon event called HackU. It defines hacking as constructively altering a system to do what you want using available resources. HackU is described as 24 hours of non-stop coding and innovation where participants are encouraged to build something they will personally use, show what can be built with available systems, and present their work at the end. Tips are provided such as focusing on one innovative idea, using available APIs, code libraries and development tools from Yahoo and others, and preparing a backup demo in case of technical issues.
Hack 101 at IIT Kanpur
- 2. What is a hack?
- 3. “Hacking” is a constructive term. “Cracking” is destructive
- 5. “Altering a system to do what you want it to do, using what is at your disposal”
- 8. 24 hours of un-interrupted, unrestrained coding and innovation
- 9. Hack
- 10. Eat
- 11. Get Help
- 12. Recharge
- 13. Have Fun
- 15. Present
- 16. Win
- 17. Where do I start?
- 18. A good hack starts with an idea…
- 20. Build something you will use yourself
- 22. Show us what can be built using the systems we (and others) offer.
- 25. To build a typical web hack you need data, access and an interface
- 26. Yahoo! has opened up its data
- 27. Search (BOSS), Flickr, Geo, Social, Mail, Messenger …
- 28. And so have others
- 29. Programmable web lists 9810 APIs in their API directory Twitter, Facebook, Google, …
- 30. To access these you can use YQL
- 31. YQL is a SQL-Like Language that lets you …
- 32. … filter, combine, tweak data across hundreds of Web Services. http://developer.yahoo.com/yql/console
- 33. Data however is not enough.
- 34. You also need working interfaces
- 35. Technologies are easy: HTML, CSS, JavaScript
- 36. Making it work on all browsers and OS is tricky
- 37. YUI
- 40. Do not show us slides about your hack
- 41. Instead show us what you have done
- 43. Have a plan-B
- 44. Have a Plan B • Record screencast • Do not depend on the internet • Keep your stuff ready in the browser • Rehearse the demo with atleast one crew member before hand
- 45. And once you are done
- 46. And once you are done • Keep your hack live for others to see • Show other hackers what you have done • Publish your code in Github • Let us know and we can help you to take it even further!
- 48. Don’t limit yourself to your favorite toys
- 49. A good hack doesn’t need to be a big thinghttp://www.flickr.com/photos/capricorndragon/4000384412/
- 50. Don’t look for features. Concentrate on one thing Don’t look to solve everything
- 51. You only have 24 hours
- 52. Find things that already work And put them together
- 53. Innovation has no limits
- 54. Go Hack !!! Have Fun
- 56. Hack Resources • http://developer.yahoo.com • http://developer.yahoo.com/yql/console • http://github.com/yahoo • http://hackyourworld.org/ • http://github.com/codepo8/hackday-toolbox/ • http://talks.php.net/show/hacku/
Editor's Notes
- #2: Introduce Crew on Stage
- #3: How does this word resonate with you?
- #4: Often misrepresented in the media
- #6: Jargon File
- #8: So what is a hacker?
- #9: Hack U - Bring the concept from our internal Hack Days and Open Hack days to Universities
- #22: Find something that always annoyed you with systems you use... ...and build a workaround.
- #23: Random Hacks of Kindness
- #25: Everything that yahoo does for developers is located. With documentations, code examples
- #26: Everything that yahoo does for developers is located. With documentations, code examples
- #53: Record screencastDo not depend on internetKeep your stuff ready in browser
- #55: Tell us about your progress
- #58: Be ready to play with new technologies
- #59: Hacks need not be complex. It need not be the next big thing. You don’t need to have a product out in 24 hours.
- #60: Don’t try to solve everything in your hack..
- #61: You have only 24 hours.
- #62: Mashup or Shutup.