HackSC: The how and why of hacking at a hackathon

Transcript

1. HACK ON! ! by pamela fox ! @pamelafox @khanacademy
2. USC 3D Animation Linguistics Computer Science
3. COMPUTER SCIENCE + LINGUISTICS
4. COMPUTER SCIENCE + ANIMATION
5. COMPUTER SCIENCE + GAMES
6. SIDE PROJECTS…
7. “DEVELOPER ADVOCATE”
9. 20% TIME
10. Japan Australia Singapore France Brazil Philippines
11. THE HACKING YEAR
15. http://life.khanacademy.org/
16. http://life.khanacademy.org/
17. WHY HACK?
18. WIN PRIZES
19. WIN PRIZES??
20. WIN PRIZES
21. BUILD SOMETHING
22. BUT WHAT?
23. Something BIG! SOMETHING BIG!
24. NO.
25. But big in its own way. SOMETHING SMALL! Source: http://www.flickr.com/photos/ringai/3975402556/sizes/m/in/photostream/
26. HOW?
27. BRAINSTORM
28. BRAINSTORM PICK 1 IDEA
29. BRAINSTORM PICK 1 IDEA PICK 1 FEATURE
30. BRAINSTORM PICK 1 IDEA PICK 1 FEATURE FAKE THE REST
31. ONCE YOU’VE “AGREED” ON THE IDEA… PROTOTYPE DELEGATE & HACK CRAFT YOUR PITCH commit often!
32. PROTOTYPING
33. PAPER PROTOTYPING
34. WIREFRAMES mybalsamiq.com/signup
35. HACKING
36. COMMIT EARLY, COMMIT OFTEN https://help.github.com/articles/create-a-repo/
37. PICK YOUR STACK tinyurl.com/pickyourstack
38. THE FRONTEND
39. THE BACKEND Language + Framework + DB + Host Flask/Django Play / JSP Zend / Drupal Python Java PHP MySQL MongoDB BigTable CouchDB Azure GAE Heroku JavaScript Node / Express
40. BACKEND-LESS FRONTEND
41. PITCHING
42. ALWAYS BE READY TO PITCH. https://github.com/mimming/pitch-like-a-hacker/blob/master/index.html PICK 1-2 PEOPLE TO JUST WORK ON THE PITCH, AN HOUR BEFORE. DON’T ASSUME ANYTHING WILL WORK.
43. https://github.com/mimming/pitch-like-a-hacker/blob/master/index.html BE ENGAGING: MAKE IT INTERACTIVE OR TELL A STORY. PITCH SCRIPT 1. Say your group name 2. State the problem you solved 3. A one sentence description of your solution 4. Demo the stuff that works, dance around the pictures. 5. Talk about the technologies you used in descending order of best prizes
44. PROTOTYPE DELEGATE & HACK CRAFT YOUR PITCH commit often! CELEBRATE!
45. DON’T FORGET
46. BUILD UP YOUR RESUME
47. IF WE’RE HIRING YOU TO CODE, WE WANT TO SEE THAT YOU CAN CODE. Don’t show me this: Pamela Fox! ! USC 2002-2006, B.S. in Computer Science! Courses taken: Algorithms, Databases, Data structures, Web development, Brain Theory, Computer graphics! ! Awarded Merit Research Scholarship
48. IF WE’RE HIRING YOU TO CODE, WE WANT TO SEE THAT YOU CAN CODE. Show me this: Pamela Fox! ! USC 2002-2006, B.S. in Computer Science! GPA: 3.8! ! Projects: * SimilarBooks: A visualization of books related to a user-entered book, using the Amazon Similarity API, Python, and a BFS approach.! * PhotoMunchrs: Based on NumberMunchers, with photos pulled from the Flickr API. Provides a Python REST API built on App Engine to report game statistics and provide munch scores.
49. SHOW US YOUR CODE! Your name! ! USC 2011-2015, B.S. in Computer Science! ! Projects: * AwesomeHack: An app that does X and Y. Built on the A and B technologies. Developed during HackSC 2014 and continued after. Code available at github.com/yourname/awesomehack!
50. LEARN TO WORK WITH PEOPLE
51. CODING? powtac / Flickr
52. CODING! (IN INDUSTRY/OSS) http://www.slideshare.net/wuzziwug/engineering-culture * Understanding existing code * Planning “your” code * Writing consistent code * Testing “your” code * Improving “your” code * Releasing “your” code * Monitoring “your” code * Learning from bad code
53. MEET NEW PEOPLE
54. FRIENDS ARE GREAT (SO ARE CONNECTIONS)
55. HACK ON!