This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Multiparadigm Programming in Industry: A Discussion with Neal Ford and Brian Goetz
September/October 2010 (vol. 27 no. 5)
pp. 61-64
Dean Wampler, DRW Holdings
Tony Clark, Middlesex University
Neal Ford, ThoughtWorks
Brian Goetz, Oracle
The guest editors discussed the pragmatics of multiparadigm programming with Neal Ford and Brian Goetz. Should the average team adopt MPP? Can it do so successfully? Neal argues that such teams can't afford not to adopt MPP, if they want to stay competitive. However, the risks can be mitigated by careful adoption, based on demonstrable value, with appropriate division of responsibilities among team members, based on their skills. Brian argues that developers often make poor choices, driven more by personal interests than by concern for what is ultimately best for team success. Neal offers some real-world examples of how Thoughtworks has used MPP effectively.
Index Terms:
multiparadigm programming, domain-specific languages, software process, team organization
Citation:
Dean Wampler, Tony Clark, Neal Ford, Brian Goetz, "Multiparadigm Programming in Industry: A Discussion with Neal Ford and Brian Goetz," IEEE Software, vol. 27, no. 5, pp. 61-64, Sept.-Oct. 2010, doi:10.1109/MS.2010.121
Usage of this product signifies your acceptance of the Terms of Use.