“Admitting you were wrong and a willingness to change course is great example, and far too rare in today’s hard-liner “Stay-The-Course” world” +1. A breath of fresh air from the W3C.
Via David Wragg, a pointer to a great description of the roles and responsibilities of senior technical staff, written by a former colleague, Mark Kampe. Interestingly, that version was drafted 4 weeks after my tenure began (retroactively) as a Senior Staff Engineer at Sun. I’m surprised I hadn’t seen it until now.
The snippet that David quotes is the one that struck a chord with me too;
When the “Emperor has no clothes”, it is the responsibility of the senior technical staff to stand up and say so. Sales people are driven by short term business. Marketing people work with all manner of vague and ambiguous factors. Executives work with the information that other people have given them. Managers work with the directions they have been given. Engineers are the people who responsible for figuring out how this stuff is all going to work … and if it isn’t going to work they have an obligation to say so.
- Declaritive Ajax components and XML namespaces, referencing a great Dave Johnson post.
- a new ZK Google Maps components, which is used declaratively
Any move of the pendulum in this direction is a-ok by me. But to be clear, I am glad it’s a pendulum … meaning that there’ll always be a place for script (the bleeding edge), but we need to consolidate common practice periodically. This also gives us the opportunity to support the functionality natively in the browser.