GOTO Berlin is a vendor independent international software development conference with more that 60 top speaker and 400 attendees. The conference cover topics such as Java, Open Source, Agile, Architecture, Design, Web, Cloud, New Languages and Processes.

Richard P. Gabriel, IBM Research

Richard P. Gabriel

Biography: Richard P. Gabriel

Dr Richard P. “Dick” Gabriel is a leader in the Lisp/OOP community, known for his book “Innovation Happens Elsewhere”, his essay “Lisp: Good News, Bad News, How to Win Big”, and the "Gabriel” Lisp benchmarks that became a standard way of benchmarking Lisp implementations. Dr Gabriel is also the recipient of the recipient of Association for Computing Machinery's 1998 Fellows Award, and the 2004 Allen Newell Award.

With a Ph.D. in Computer Science from Stanford University in 1981, and an MFA in Poetry from Warren Wilson College in 1998, Dr Gabriel was described in the Alan Newell Award as stretching “the imagination of computer scientists with ideas and innovations from other fields” and he combines these into presentations to technology audiences that he describes as being “audacious set-piece guerilla performances”.

Dick has been a researcher at Stanford University, company president and Chief Technical Officer at Lucid, Inc., vice president of development at ParcPlace-Digitalk, a management consultant for several startups and Sun Microsystems, and Consulting Professor of Computer Science at Stanford University.

Presentation: I Throw Itching Powder at Tulips

Track: Beyond Agile / Time: Friday 15:50 - 16:40 / Location: Paris

I don't write software like any of you. Software development methodologies are nonsense. Literally. Here is my manifesto:

* Nature over Individuals and Interactions over Processes and Tools
* Insights over Working Software over Comprehensive Documentation
* Problem Engagement over Customer Collaboration over Contract Negotiation
* Grappling with Mystery over Responding to Change over Following a Plan

My guiding principles:

* Create opportunities for change
* Continuous engagement with software
* Code and scientists must work together
* Build projects around mysteries
* Stare at the problem staring at you
* Puzzling software is the primary measure of progress
* Surprising development
* Contentious attention to insight and diversion
* Simplicity is beside the point
* Self-organizing scientific method
* Continuous revolution

I write software to make machines do what they cannot do. I work from no requirements nor specifications. My only collaborators are human knowledge as it exists today (at a distance) and the code I am working with (which constantly stares blankly back at me). For standard programmers, design and coding are, at most, puzzles; for me design and coding are mysteries, at least.

In this talk I'll tell you about the software I am working on and why no software engineering process has anything to do with it.