My talk at Future of Web Apps Dublin about using building blocks that solve issues instead of writing your own code. Includes lots of geolocation demos.

1. Powerful tools
that you need. (And probably don’t know about)
http://www.flickr.com/photos/wwarby/3016593775/
Chris&an Heilmann, Future of Web Apps ‐ Dublin, Ireland 5/2010

2. As developers we
are our worst
enemies.

3. The reason is that
we are driven to
perfection and
constantly being let
down by products.

4. These frustrations
make us do one
thing over and over
again.

5. Summoning the inner
demon!

6. A lot of our
problems have been
solved numerous
times.

7. Instead of
learning from
each other,
we repeat
the mistakes
of others.

9. If people call CSS3 effects sexy
then they should have some real
sex to see the difference.

10. Instead of
applauding the next
new push of the
envelope I want you
to do one thing.

11. Build some *real*
products and talk
about them!

12. One hot
topic is geo
location or
location
based
services.

13. I wanted to play
with that and create
a solution for me to
build other things
on.

14. http://isithackday.com/hacks/geo/yql-geo-library/

15. YQLGeo now allows
me to solve my Geo
needs in one
JavaScript function.

16. ★ Geographical location from a text
★ Location information from lat/lon
★ Geo locations mentioned at a certain
URL
★ Place from an IP number
★ Finding the user (geolocation API or
IP)
yqlgeo.get(what,callback)
http://github.com/codepo8/YQL-Geo-Library/

17. The main task was
to find all the
services I am using
in there.

18. Yahoo Placemaker
http://developer.yahoo.com/geo/placemaker
Yahoo GeoPlanet
http://developer.yahoo.com/geo/geoplanet/
JSON IP
http://jsonip.appspot.com
IP location tools
http://iplocationtools.com/ip_location_api.php
W3C Geo location
http://dev.w3.org/geo/api/spec-source.html
Flickr.places.findByLatLon
http://www.flickr.com/services/api/
flickr.places.findByLatLon.html

19. The normal cause of
action would be the
same for each of
those.

20. ★ Sign up for a developer key
★ Wait for key
★ Download SDK
★ Enter key
★ Fail to use SDK
★ Curse other developers
★ Write own authentication code
★ Get data in random format
★ Write filtering function
★ Convert to usable format

21. A.k.a. a big friggin
waste of time.

22. Which is why I used
something different
that Yahoo provides
you with.

23. YQL http://developer.yahoo.com/yql/console/

24. YQL http://developer.yahoo.com/yql/console/
select {what} from {where}
where {conditions}

25. YQL is a web
service in itself that
allows me to mix
and match services
stored in “data
tables”.

27. http://isithackday.com/hacks/geo/around-you/

28. http://isithackday.com/geoplanet-explorer/geodrilldown.php

29. A friend of mine
complained that it
is hard to do
research with
search engines.

30. select * from query.multi where queries='
select Title,Description,Url,DisplayUrl
from microsoft.bing.web(20) where query="cat";
select title,clickurl,abstract,dispurl
from search.web(20) where query="cat";
select titleNoFormatting,url,content,visibleUrl
from google.search(20) where q="cat"
'

31. http://icant.co.uk/goohoobi/index.php?research

32. http://vimeo.com/8075850

33. Do not try to build
everything yourself!

34. Use the web
to build for
the web.

35. http://winterolympicsmedals.com

36. http://www.guardian.co.uk/news/datablog/
2010/feb/11/winter-olympics-medals-by-country

39. select * from csv where url="http://
spreadsheets.google.com/pub?
key=tpWDkIZMZleQaREf493v1Jw&output=
csv" and
columns="Year,City,Sport,Discipline,Countr
y,Event, Gender,Type" and Year="1924"

40. http://isithackday.com/csv-to-webservice/

41. Give us your data so
that others can
work with it!

42. http://github.com/yql/yql-tables

43. Building interfaces?
Learn from
research.

44. http://developer.yahoo.com/ypatterns

45. http://developer.yahoo.com/ypatterns/wireframes/

46. Do you really want to fix CSS
layouts?
http://developer.yahoo.com/yui/grids/builder/

47. Build on things that
work and style them
to your needs.

48. http://developer.yahoo.com/yui/

49. http://www.yuiblog.com/blog/2010/02/11/video-heilmann-yql/

50. And last but not
least...

51. Do *not* build your
own login system!

52. You got the data,
you got the building
blocks.

53. All you need is the
right mindset.

54. Christian Heilmann
http://wait-till-i.com Cheers
http://developer-evangelism.com
http://twitter.com/codepo8