Greater Wisconsin Software Symposium - Feb 29 - Mar 2, 2008 - No Fluff Just Stuff

Richard Monson-Haefel

Greater Wisconsin Software Symposium

Milwaukee · Feb 29 - Mar 2, 2008

You are viewing details from a past event
Richard Monson-Haefel

VP of Developer Relations, Curl Inc.

Richard Monson-Haefel is the author of 97 Things Every Software Architect Should know (O'Reilly), Enterprise JavaBeans (O'Reilly), Java Message Service (O'Reilly), J2EE Web Services (Addison-Wesley), and one of the world's leading experts and book authors on enterprise computing. He was the lead architect of OpenEJB, an open source EJB container used in Apache Geronimo, a member of the JCP Executive Committee, member of JCP EJB expert groups, and an industry analyst for Burton Group researching enterprise computing, open source, and Rich Internet Application (RIA) development. Today, Richard is an independent software developer. You can learn more about Richard at his web site http://www.monson-haefel.com

Presentations

10 Things Every Software Architect Should Know

An effective software architect understands that every application is different and requires unique choices regarding programming language, middleware, integration, data access, user interface design, etc. Richard Monson-Haefel has distilled knowledge from his own experience and from personal interviews with the World's best software architects to define 10 principles every software architect should know in order to be effective.

Developing Rich Internet Applications

With literally hundreds of RIA products (e.g., Adobe Flash, Nexaweb, Backbase) and open source Ajax projects (e.g. Dojo, GWT, Prototype) to choose from. Picking the right RIA technology for the job requires months of research. Richard Monson-Haefel has been researching and writing about RIA alternatives for two years and has already done the research so you don't have to.

Understanding Open Source Licensing

What does GPL, LGPL, MIT, Apache licenses, copy left, and dual licensing mean? Richard Monson-Haefel explains both the legal and technical implications of the major open source licenses in plain English. He explains when and how you can use open source in the enterprise and in the development of software products and how to protect your organization from abusing open source licensing.