Feb
11
2006
Find citations on Bloglines or Technorati. View blog reactions
By category: Current Events, Design, Engineering, Front End Engineering, Tools, Web Services.
Marc Hedlund writes on the O’Reilly Radar blog about “Web Development 2.0“. In his experience, “many startups and companies seem to be developing a new set of software development practices”:
Software isn’t written for Web 2.0 companies the way it was during the bubble, nor is it written the way traditional, shipped software was. New ideas about Web applications seem to necessitate new ways of making those applications.
He reports on 7 characteristics:
- The shadow app
- Sampling and testing
- Build on your own API
- Ship timestamps, not versions
- Developers - and users - do the quality assurance
- Developers - and executives - do the support
- The eternal beta
He’s got a paragraph or two under each of those bullets, so I encourage you to head over and take a read. I’m a big fan of #3, and have been doing #2, #4, and $5 for years. What about you? Any to add to the list?
Subscribe to this blog.
Wally February 12th, 2006 - 11:16 am
I agree with the #3, building atop your API. You’re testing 2 birds with a single stone by developing a single interface for your web app and external partners and those mash-up nerds. Is #1 similar to this point?
Eternal beta means you can’t charge for the service, right? It doesn’t mean you can’t make $$$ indirectly via ads.
I’m not so hot on #4 which can promote erratic practices in processes. I’d rather build a framework, featuring a CMS, rather than push a build that could potentially break (Murphy’s a bitch); you never know and there’s too much at stake.
Just my 2 cents. Thanks Nate for the link.
Martin Hernandez May 11th, 2006 - 9:50 pm
Internet Explorer Eolas changes and the Flash plugin
Filed under: flash javascript usability quicktime flashobject@ 2:30 pm
Microsoft recently announced (again) that they will be changing the way Internet Explorer handles plugins (more info here).
So how does all of this affect you being a web developer?
Basically, the functionality changes work like this:
When using an applet, object, or embed tag to insert a plugin into an HTML document, that plugin will not allow user interaction until the user clicks on it. Microsoft calls this process “Activating an ActiveX Control’s Interface.“
In the case of the Flash plugin, it means that your Flash movies will not work until a user ‘activates’ it first by clicking on it. The details are still a bit fuzzy, and I can’t find a developer preview of IE 6 or IE 7 that include this new functionality to test this new functionality (If you find one, please let me know) (see below). This is a slight improvement over the previous ‘fix’ which was a small dialog prompt for each ActiveX control on a page. Now you just have to click on each control to activate it (if you want to interact with it).
Microsoft says “We believe over the next six months, most customers will be running copies of Internet Explorer with this behavior.” The changes will be rolled into IE 6 through security updates to Windows, and included in IE 7.
http://www.instantenet.com.ar
Marc Hedlund May 20th, 2006 - 9:56 am
Thanks for the link, Nate. You might also like the follow-up to the original piece. I think there’s a lot more to say about this topic — I’m hoping we’ll get more stories from the people who would know.
austin texas personal injury lawyer June 26th, 2006 - 2:24 pm
great entry