Unconference Interop

Watch it live

From Wiki

Most web developers perform testing during development and in QA. They might even perform capacity testing. But websites are living things, always changing. Managing change for production websites is like swapping engine parts in the pit stop during the Indy 500. Sure, the developers tested their component during development and in QA. They might even run a capacity test on the compiled application. But websites, like race cars, are living multi-component systems when deployed in the real world. How do we manage web health mid track without losing the race?


[edit] Experts

John Overton, Director of Strategic Partnerships, Coradiant