For more than 35 years I have asked myself, what is the right way to program? I've learned about goto-less programming, top-down programming, object oriented programming, the Common Object Model, Java Beans, MBeans, Enterprise Java Beans, Plain Old Java Objects, and XML binding. But regardless of the approach, the software is always too rigid, the software stack is too deep, and the requirements always change in ways that require too much work.
In 2002 I had the privilege of working for, and being mentored by, Norman Kashdan. By that time he had already spent 18 years developing a world view that he calls Rolonics. I believed then that there was something very right about Rolonics and have myself spent the last 5 years developing a software engineering practice around it. Finally I have come to understand [some of] its value: with a Rolonic approch to software engineering we can create highly configurable, fluid software systems that can change on-the-fly to meet ever changing requirements.
