- From: Karl Dubost <karl@la-grange.net>
- Date: Thu, 6 Jun 2013 15:55:53 +0900
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: "Appelquist Daniel (UK)" <Daniel.Appelquist@telefonica.com>, www-tag <www-tag@w3.org>
Le 6 juin 2013 à 09:40, Marcos Caceres a écrit : > it's quite sad that many in the dev community are still not seeing us as representing them here at the w3c :( because you don't. :) It is simple as that. No offense, that doesn't remove your competences, passion or qualities. Also you can't say "Web developers" and just be satisfied. For example in the last Web agency I was working just 3 years ago as a technical director, there were: * people doing content editing in HTML templates. * people doing front-end development (CSS/HTML only) partly for integrating Photoshop mockups into a real Web site. Some using templating systems part of Ruby On Rails, PHP, etc frameworks. * people doing front-end dev (JS) * people developing backend with Web frameworks. * Artistic Directors using Photoshop most of the time * UX people (using balsamiq, paper, omnigraffle) to design the interactions * The account manager-bizdev people Some are not directly developing stuff into code, but their profession entirely depends on the capability of the Web platform by allowing some type of interactions or not. For example, many UX people do not realize how much they are dependent of HTTP for user interactions. All the people I have cited above had no idea of what is the Web architecture, nor do they have time to care. Specifically the front-end developer is at the end of the food chain and have to pay the price of our decisions. -- Karl Dubost http://www.la-grange.net/karl/
Received on Thursday, 6 June 2013 06:56:02 UTC