with Richard A. Green Wednesday, October 06th, 2010 @ 6pm Abstract: How does one design a programming language for business processing? Why are today's popular languages (Java, Python, C++, COBOL, …) poorly matched to today's environment? Our tools shape our thinking about solutions. How might our tools be getting in the way of better thinking? A programming language cannot be understood separately from its run-time platform. Nor can it be understood separately from its people. Programmers create their own culture and that, more than anything else, channels the evolution of the language. To demonstrate how these principles apply, Richard reviews Hum, a business programming language designed for today's environment with some extensions for future user interfaces. Hum enables a kind of natural language syntax. It delegates persistence, messaging, fuzzy-arithmetic, and accounting to the run-time Bio: Richard Green is a software architect currently employed by DTE Energy. Previous roles have included enterprise architect, project manager, chief programmer, methodologist, and consultant. He has designed and delivered business systems, statistical analysis tools, and computer aided software engineering (CASE) tools using Java, Smalltalk, C++, C, C#, Pascal, PL-1, COBOL, Visual Basic, ForTran, and Assembler |

