-
“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.
links for 2006-10-30
Leave a reply
Monthly Archives: October 2006
links for 2006-10-28
-
Sam considering WSO2. See my comment.
-
“I mean, let’s face it: strategy is all that guy’s got going for him. He has no limbs and he’s already on fire.”. ROTFL!
links for 2006-10-27
-
“Evil doesn’t come like Darth Vader dressed in black, hissing. Evil comes as a little bird whispering in your ear”. Poignant.
-
I think the co-anchor should have taken that one!
-
Are urban design plans considered a failure because a tornado takes out a business park?
-
Openid support has either been removed, or it’s well hidden.
links for 2006-10-26
-
“We spent a considerable amount of time researching a number of HTML rendering engines for use in Apollo”, “Apollo will be distributed […] with Apollo applications”, “Is Apollo a web browser? No”. Call it what you like, but it’s a browser. Blech.
-
“Working against the web — and treating it just as a back-end to pull data from to fuel proprietary RIA’s — is like marching your armies into a Russian winter: a decision everyone knows is ill-fated, but leaders keep doing over and over again” Nicely s
links for 2006-10-25
-
Eric provides some more info on the upcoming W3C “Web of Services for the Enterprise” workshop. I hope to attend.
-
Wow. What a beautiful, inspiring story about one man’s (Scott Adams) principled design of a (possible) cure to his lost voice.
-
Message to a certain TAG member and WS-Transfer editor; it’s time to pick sides, my friend.
-
Go Ladies!
-
Fibre to Toronto and Montreal, but no Ottawa! Gah!
Responsibilities
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.
links for 2006-10-23
-
“Traffic Web Services are also available through the Traffic REST API.” Erm, so there’s an RSS API *and* a REST API? Does .. not .. compute. REST != XML/HTTP. I’d say scrap the “REST API”. Nice work otherwise though. Keep it coming.
links for 2006-10-22
-
“Ashwin walked us through the SOA Architectural Big rules. I made notes, crossing out the errors and replacing them with the relevant REST principles.” A good read.
links for 2006-10-21
-
Heh, he said “MIME Typen”. I hope I’m not offending anyone by finding that cute 8-)
-
Heh, I love it; SOA as Beta 8-) P.S. Jeff, the VHS version came out 15 years ago, not 5. 5 years ago somebody tried to put video on 8-track 8-)
-
“Can the Web fulfill industry and business requirements?” Pretty much, yah.
-
“Also, there is no logout button. I plan to take care of both problems for new schemes in Mozilla.” God bless you, Rob Sayre.
Declarative Ajax catching on
Just a quick followup on a previous piece, Ajaxian picked up a couple of declarative Javascript stories today;
- 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.