1. Hacking 101
Christian Heilmann | http://wait-till-i.com | http://scriptingenabled.org
Delhi, India, University Hack Day, January 2009

2. नम#$
Namaste

3. I’m Chris, hacker
and geek.

4. I am today here to introduce
you to what hacking means
to us.

5. To me it means:
“Altering a system to do what
you want it to do using what
is at your disposal.”

6. It also means having a lot of
fun trying to make things do
what they weren’t made for.

7. It is unrestrained innovation.

8. So welcome, innovators!

9. We want you to show us what
can be built using the systems
we (and others) offer...

10. ...that makes a difference in
your lives and make the
things you care about easier
to achieve.

11. Find something that always
annoyed you with systems
you use...

12. ...and build a workaround.

13. You’ll be amazed about the
impact this can have.

14. To reach hackvana you need
three things:

15. Access, Data and an Interface.

16. Access is granted to you via
feeds, web services and SDKs.

17. Feeds are data in a
predictable format, for
example RSS.

18. http://www.guardian.co.uk/travel/restaurants

19. http://www.guardian.co.uk/travel/restaurants/rss

20. Web services are quite
similar, only they allow you
to filter down the data you
want.

21. http://
answers.yahooapis.com/
AnswersService/V1/
questionSearch?
query=delhi+puppies
&region=in&lang=en&
appid=yahoodemo

23. ... lots more...

24. http://developer.yahoo.com/answers/V1/questionSearch.html

25. They also allow you to get the
data in other formats to
easily re-use it.

26. The idea of hacking is to use
this data, mix it up with other
ideas and other data to
provide a better service for
the end user.

27. This is dead easy these days!

28. There’s Yahoo Pipes for
mixing, filtering and
matching.

29. http://pipes.yahoo.com

30. Or if you like SQL-style data
conversion there’s YQL:

31. http://developer.yahoo.com/yql/console/

32. Both of these systems allow
you to reach data from Yahoo
and other services and pre-
filter it for use in your own
hacks.

33. Data however is not enough.

34. Building *working* web
interfaces is a specialist skill.

35. I’ve been developing for the
web for 12 years and it still is a
mystery to me why some
things just don’t work.

36. The technologies are easy
enough:
HTML for structure
CSS for presentation
JavaScript for behaviour

37. Where it gets truly annoying is
the unknowns.

38. You have no idea about the
user’s setup, ability or rights
to change their technical
environment.

39. And then there are the
browsers and all their
wonderful bugs and quirks.

40. This is why it is a good start to
use libraries or frameworks.

41. Here are our helpers:
YUI
BluePrint
http://developer.yahoo.com/yui/ http://mobile.yahoo.com/developers

42. Using these, you can quickly
build interfaces that work on
the web and mobiles.

43. What about reach?

44. The newest way of access that
systems and companies allow
you these days is opening up
their address books.

45. http://developer.yahoo.com/social/socialdir/
http://code.google.com/apis/opensocial/
http://developers.facebook.com/connect.php

46. Instead of building it and
waiting till people come, build
where the people are.

47. http://developer.yahoo.com/yap/

48. And build with what they use
already.

49. http://developer.yahoo.com/search/boss/

50. How about
some hack
examples?

51. I use SlideShare – a lot.

52. http://www.slideshare.net/cheilmann/slideshows

53. One cool thing is
that SlideShare
automatically
creates
transcripts of
your slides:

54. So I’ve used this to create a
version that is easily
accessible for blind people or
those who don’t have Flash.

55. http://icant.co.uk/easy-slideshare/?slides=http://
www.slideshare.net/cheilmann/playing-with-the-web-
presentation

56. Using YQL, it was also easy to
write a JavaScript wrapper
that allows you to show the
transcripts with your slides.

57. http://www.wait-till-i.com/2009/01/11/adding-transcripts-to-
presentations-embedded-from-slideshare-using-yql/

58. I use Twitter – a lot.

59. I got all this emails from
Twitter telling me about
people following me.

60. What I didn’t get was it telling
me when people left me.

61. Or what I was telling the
world before they left me.

62. So I dug into the API a bit and
built TweetEffect.com

63. http://tweeteffect.com/?user=codepo8

65. I put it up, and started testing
edge cases.

66. One of them was Guy
Kawasaki, whom I knew has a
lot of followers and updates.

67. One of them was Guy
Kawasaki, whom I knew has a
lot of followers and updates.

68. And that started a landslide of
visitors, comments and ideas
for it.

69. Tim O'Reilly
Guy Kawasaki
Ryan Carson

70. And without knowing it, I
became a startup to watch!

71. What about reach?
That was me, time for you to
show what you can do!

72. Innovation is not a matter of
skill or being in the right job
position.

73. It is a matter of wanting to
change what we have and be
ready to play.

74. We do this to help you see
your potential.

75. And we do this to see if we do
a good job in explaining our
offers to the developer world.

76. The web is yours, go out and
play!

77. THANKS!
Access happens on several
channels.
http://www.flickr.com/photos/nez/378349478/