Projects
- Technical Trainer and Mentor: Sencha Ext JS, Touch and Java
- Architect and Team Lead
- Architect
- Enterprise Architect
- EclipseCon 2006 Web Site Architect
- Application Architect
- OOPSLA 2005 Volunteer
- Practice Manager
- OOPSLA 2004 Volunteer
- Java Courseware Development and Delivery”
- Earlier Work

Technical Trainer and Mentor: Sencha Ext JS, Touch and Java
Currently, Mr. Rahder spends most of his time doing training and mentoring in HTML5 development using the Sencha libraries Ext JS, Touch and Ext GWT, as well as training in Java-related technologies: core Java, servlets/JSP and JPA.
Software as a Service Product Architect and Team Lead
Mr. Rahder was sole architect, implemented critical features and guided and supervised the work of the project team for a nationally marketed software-as-a-service Web-based information system. The application provides contact management, job tracking and order tracking for trades-based projects.
The project was agile, using a weekly sprint cycle, daily stand up meetings, and other Scrum techniques. The front-end uses state-of-the art Web technologies, such as AJAX, Ext JS (a rich Javascript front-end library) and Flex (Adobe’s Rich Internet Application front-end library). Some features are also available via iOS and Android applications. Data and servers are fully in the cloud: Data is stored in XML, using Amazon Simple Storage Service and SimpleDB. Web hosting is provided using on-demand Amazon Elastic Cloud Computing servers. Subscriber payments is done using Amazon Flexible Payment Service.
Mr. Rahder was architect and product manager for an inter-state construction company. Historically, the company’s corporate office manually processed about 1,000 pages of paperwork and $600,000 of revenue each day. Manually processing the information was labor-intensive, error prone, and slow—the company’s growth was limited by their ability to process information. The application designed and implemented by Mr. Rahder allows almost all paperwork to be gathered on-line, either centrally or by salesmen in the field. The information is available immediately throughout the company, allowing higher productivity, better cash flow and better controls. In addition, the company now has the ability to handle a larger volume of business, and therefore, is free to expand into new markets.
Mr. Rahder’s simple, innovative design uses Amazon’s Simple Storage Service as the data repository, and Java technologies for the business and presentation layers. Customer addresses are geocoded, and their locations displayed using a Google Maps mashup.
The next generation of the application was extensively re-factored to be sold as a software-as-a-service (see above).
Mr. Rahder worked as an enterprise architect for a large corporation. The corporation is moving from a history of “stovepipe” application development to a service-oriented approach using an enterprise service bus.
The stovepipe applications resulted from the practice of funding and scoping applications along business unit lines, rather than along user use-case lines. In other words, in this organization many key user’s tasks touch on several business units. But because applications are typically developed along business unit lines, these users must use multiple applications to do a task.
This problem could be addressed procedurally—by being careful to broaden the scope of requirments for projects and by taking a broader, enterprise-wide, perspective. However, to allow the flexibility to create appliactions for current, and future unanticipated applications, SOA approaches are being pursued.
EclispeCon 2006 Website Architect
Mr. Rahder designed the Web content management system EclipseCon. The site separates layout from content. Pages are date-driven, allowing pages to be automatically “released” when key dates are reached. Submissions are stored in XML format on a remote server, and are dynamically fetched and rendered.
Application Architect
Mr. Rahder was the lead application architect for a system that allows client applications to electronically file documents. The system includes a Web Services back-end a Web-based user interface.
For more information on the project visit http://www.dor.state.wi.us/ust/retn3.html.
Mr. Rahder was the “Technical Chair” for OOPSLA 2005.
Mr. Rahder was made Practice Manager and Team Lead for a team of Java developers. As Practice Manager Mr. Rahder coordinated the activities of the team with the organization’s Project Management Office. He also supervised and mentored the team in their day-to-day design and programming activities.
Mr. Rahder also created a set of best practices that addressed object-oriented design, development methods, and Java technique. These practices helped developers clarify scope, write code with higher cohesion and lower coupling, and raise the overall quality of their applications.
Mr. Rahder was the “Technical Chair” for OOPSLA 2004. To this end he created a content management application for the OOPSLA Web site.
Java Courseware Development and Delivery
Mr. Rahder developed a Java curriculum for the State of Wisconsin, covering topics from beginning Java to creating model-view-controller Web applications and Struts. See the training page for more information.
Earlier Work
OOPSLA 2003 Volunteer
Mr. Rahder was the “Communications Chair” for OOPSLA 2003. The Communications Chair is responsible for print- and Web-based content and advertising.
Article: “Application Architecture”
The article appears in The July 2000 issue of The Delphi Magazine , and discusses the infra-structure of classes that makes it easier to extend and modify a Delphi program. For the development team the result is dramatically reduced development and maintenance costs. For the end user the result is a more flexible application with features that have consistent behavior.
Article: “Reduce Site Maintenance…”
The article appears in Inside Web Development, and describes an early and startlingly parsimonious implementation of a layout-aware Web server application.
Article: “A Delphi Multicaster”
The article appeared in the January 2000 issue of The Delphi Magazine, and described how to implement a multicaster in Delphi. A multicaster is an implementation of the Observer design pattern.