I am a self-taught toolmaker by profession; having developed a variety of computer based tools since 1958. My work with computers has always been highly oriented towards creating value for the users in the short and long term. I have measured my research results by their utility, not their academic acceptance. The focus is on comprehension, abstraction, design, and quality; the goal being to get it right the first time. ("Any method that prevents the programmer writing code, is a good method"). My most successful projects have been projects where the same people were system architects, designers, coders, trainers of users, system operators, trouble-shooters, maintainers, and salesmen.
My first major project, Autokon, resulted in a highly successful CAD/CAM product that went into production in 1963 and was used by shipyards all over the world for more than 30 years. It is worth noting that this project could probably not have happened today. The current fashion is to let end users dominate research projects. The nebulous Autokon project could not have survived a head on competition with real and urgent shipyard investment needs. Or it would have failed if academic research were permitted to dominate; there were many interesting problems that could have diverted the project from its strictly utilitarian goals. The project achieved a delicate balance between these two forces; the developers focused sharply on the needs of the users, but they took the users' concrete requirements as symptoms of a general classes of problems that needed general solutions.
trygver at ifi dot uio dot no
(+47) 22 49 57 27
Trygve Reenskaug is professor emeritus of informatics at the University of Oslo. He has 50 years experience in software engineering research and the development of industrial strength software products. He has extensive teaching and speaking experience including keynotes, talks and tutorials. His firsts include:
The goal of his current research is to create a new programming paradigm for readable and reviewable code that reflects the end users' mental models. The result is the DCI paradigm where the code is seen in three perspectives: The Data perspective for system state, the Context perspective for the runtime networks of communicating objects, and the Interaction perspective for the system's behavior. The research method is experimental. The BabyIDE Interactive Development Environment is a proof-of-concept implementation illustrating the power and applicability of DCI.
(Last updated by Trygve 2009.11.30)