Travailler dans le présent - Chris Heilmann - Paris Web 2008

1,963 views

Published on

Dans cette présentation, Chris Heilmann nous parlera des problèmes liés à l'adoption de standards du web récents, et décrira des façons de contourner ces difficultés. Un exemple simple est le manque de prise en charge native de l'audio et de la vidéo, et les problèmes des implémentations actuelles.

La session illustrera concrètement comment régler des problèmes a priori sans solution en les attaquant sous un autre angle. Il s'agit essentiellement de trouver une façon pragmatique de vendre, implémenter et utiliser les standards plutôt que d'attendre que le marché adopte des technologies dont l'utilisation devrait être d'une évidence complète.

Présentation originale : http://www.slideshare.net/cheilmann/working-in-the-now-presentation/

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,963
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Travailler dans le présent - Chris Heilmann - Paris Web 2008

  1. 1. Working in the now Christian Heilmann, Paris Web, Paris, 2008 http://scriptingenabled.org | http://wait-till-i.com | http://twitter.com/codepo8 http://chrisheilmann.s3.amazonaws.com/working-in-the-now.pdf
  2. 2. ParisWeb2007: La grève
  3. 3. However, it had positive results, too.
  4. 4. http://www.flickr.com/photos/mimi5/2038988511/ http://flickr.com/photos/patolucas/2858777485/
  5. 5. I am also sorry that my French hasn’t improved much.
  6. 6. The web doesn’t help there.
  7. 7. Enough of these shenanigans.
  8. 8. Right now we are not working at peak efficiency.
  9. 9. And that is *bleep*ing dangerous.
  10. 10. The market is collapsing.
  11. 11. Everybody is cutting cost.
  12. 12. We’re all going to die!
  13. 13. Culture was the seed of proliferation But it has gotten melded into an inharmonic whole Consciousness has plagued us and we can not shake it :Though we think we're in control: Questions that besiege us in life Are testament of our helplessness There's no vestige of a beginning, No prospect of an end When we all disintegrate it will all happen again Time is so rock solid in the minds of the hordes but they can't :Explain why it should slip away: History and future are the comforts of Our curiosity but here we are :Rooted in the present day: We have no control We do not understand If you came to conquer you'll be king for a day But you too will deteriorate You have no control and quickly fade away You are not in And believe these words you hear When you think your path is clear command!
  14. 14. So yeah, we might lose our jobs.
  15. 15. But even more importantly...
  16. 16. People that promise fast solutions that punish users will get our contracts.
  17. 17. This happened after the first .com crash. (“I remember when this was all fields”)
  18. 18. And lead to a massive market of massive systems...
  19. 19. ...that cost a massive amount of money...
  20. 20. ... and need a massive amount of training...
  21. 21. ...and create suboptimal results.
  22. 22. So, given that we are the good guys with the master plan.
  23. 23. What can we do?
  24. 24. Use what we have
  25. 25. Nobody cares about our technologies.
  26. 26. They do care about the systems we build though.
  27. 27. Our focus should be on collecting information about the success of our products...
  28. 28. ...built with the “best practices” we promote...
  29. 29. ... explained in human (and monetary) terms.
  30. 30. I remember two great examples.
  31. 31. In 2003, Mike Davidson saved ESPN.com 2TB traffic a day by switching to CSS: http://www.mikeindustries.com/blog/archive/ 2003/06/espn-interview (Thanks to James Craig for this link)
  32. 32. At @media 2005 Douglas Bowman showed the redesign of several sites from tables to CSS.
  33. 33. Explaining the amount of traffic saved by switching to a CSS based layout.
  34. 34. He could have shown the numbers.
  35. 35. Instead he showed upper management how many CDs could be filled with the information they saved each month.
  36. 36. http://stopdesign.com/present/2004/sydney/beauty/?no=47
  37. 37. What is 329 terabytes - 465000 CDs
  38. 38. These were all sites that were built from scratch.
  39. 39. That is something that happens less and less.
  40. 40. Let’s try to work with CMS vendors to create cleaner, leaner and meaner sites.
  41. 41. Preferably open source ones.
  42. 42. How awesome would it be to have customers ask for some open source CMS...
  43. 43. ...because so many cool sites have been built with it?
  44. 44. We need more easy to grasp explanations built on best practices.
  45. 45. I’ve created one yesterday:
  46. 46. http://www.shouldiusetablesforlayout.com
  47. 47. Which brings me to a second, very important point.
  48. 48. Use what has already been done for you.
  49. 49. Right now, we are all thinking about saving time and money.
  50. 50. The easiest way to do this is to re-use and recycle.
  51. 51. If you know where to look, you can build an impressive web product using only third party code.
  52. 52. Code that has been tested for you with users, on different browsers and platforms and released for free.
  53. 53. Why don’t we do that?
  54. 54. Because we want to do it ourselves!
  55. 55. Every *beep*ing time, over and over again.
  56. 56. I don’t know where this insecurity or lack of trust comes from.
  57. 57. But if I learnt one thing in my years as a developer...
  58. 58. ...then it is that working together brings much better results.
  59. 59. Big words, but what is there that can be used that saves us money?
  60. 60. Exhibit A: Design Patterns
  61. 61. On the Yahoo Developer Network you can find solutions to tasks that users need to fulfill on web sites.
  62. 62. These are based on research with real users and are live and cross-referenced on Yahoo! sites.
  63. 63. All of them explained in detail and licensed Creative Commons.
  64. 64. http://developer.yahoo.com/ypatterns
  65. 65. This can be a base of your own interface and information architecture.
  66. 66. They even come with stencils!
  67. 67. http://developer.yahoo.com/ypatterns/wireframes/
  68. 68. Exhibit B: CSS Frameworks
  69. 69. Basing your design and layout on an existing CSS framework means you can build them very fast.
  70. 70. It also means they work across different browsers and will work for browsers to come.
  71. 71. In terms of maintenance all you need to do is to update one CSS file.
  72. 72. http://developer.yahoo.com/yui/grids/builder/
  73. 73. There are many others out there: YAML, BluePrint, 960
  74. 74. Pick what suits you best.
  75. 75. Exhibit C: Performance Tools
  76. 76. Exceptional Performance Tips: http://developer.yahoo.com/performance/ http://www.stevesouders.com/ YSlow: http://developer.yahoo.com/yslow/ Hammerhead: http://stevesouders.com/hammerhead/
  77. 77. And of course smushit.com
  78. 78. Exhibit D: Complex Page Widgets
  79. 79. What if HTML is not rich enough for your clients?
  80. 80. Almost all *free* and *big* JavaScript libraries come with widgets that work and are proven in the market.
  81. 81. http://ui.jquery.com/ http://developer.yahoo.com/yui/ http://ui.jquery.com
  82. 82. http://ui.jquery.com/ http://ui.jquery.com
  83. 83. Exhibit E: Specialist Search
  84. 84. What if a client asks you to build a specialist search?
  85. 85. You could buy databases and build an interface and get servers to host and index the search...
  86. 86. Or you could use BOSS.
  87. 87. http://developer.yahoo.com/search/boss/
  88. 88. http://icant.co.uk/sandbox/unsafe.html
  89. 89. How about some success stories and ideas?
  90. 90. Antonia Hyde of United Response needed to build and accessible video player.
  91. 91. She had several offers from agencies – all of them very pricey.
  92. 92. So she complained about it at a conference and asked where are good, cheap developers?
  93. 93. That was me.
  94. 94. Using a free API...
  95. 95. Using a free API. http://code.google.com/apis/youtube/
  96. 96. ...and some hours of work...
  97. 97. ...I built Easy YouTube.
  98. 98. Screenshot of Easy YouTube http://icant.co.uk/easy-youtube/?http:// www.youtube.com/watch?v=vkdZmi85gxk
  99. 99. This inspired others to play with the API.
  100. 100. http://www.nihilogic.dk/labs/youtubeannotations/
  101. 101. And again others to build a company on it.
  102. 102. http://www.tubecaption.com/watch?v=jpCPvHJ6p90&vcId=137
  103. 103. And we used the learnings to make our systems better for everyone.
  104. 104. Another friend of mine works for a University.
  105. 105. His problem is that all videos of theirs need conversion and captioning.
  106. 106. On a large scale – and they have no people or servers.
  107. 107. So what can be done?
  108. 108. http://aws.amazon.com/s3/
  109. 109. http://developer.amazonwebservices.com/ connect/entry.jspa?externalID=691
  110. 110. What about captioning?
  111. 111. http://castingwords.com/
  112. 112. CastingWords must be one heck of a big company to have this turnaround time, right?
  113. 113. No, but they are clever!
  114. 114. https://www.mturk.com/mturk/welcome
  115. 115. We can be as clever.
  116. 116. So don’t waste your time listening to people who talk theoretically about the cloud and the future. LeWeb?
  117. 117. But instead use it now and look what is out there before building it yourself.
  118. 118. If we show people that we work smooth and save money.
  119. 119. We can get through this crisis *and* change things for the better.
  120. 120. THANKS! Christian Heilmann http://scriptingenabled.org | http://wait-till-i.com twitter/flickr: codepo8

×