|
|
|
<<< Previous speaker
|
next speaker >>>
|
Kevlin Henney, Independent Consultant
Kevlin Henney is an independent consultant and trainer based in Bristol, UK. He has variously developed and delivered training courses, consultancy and software across a number of domains ever since getting involved in professional software development in the late 1980s.
Kevlin's work focuses on software architecture, patterns, development process and programming languages.
He has been a columnist for various magazines and online publications, including The Register, Java Report and C++ Report. With Frank Buschmann and Doug Schmidt, he is coauthor of two volumes in the Pattern-Oriented Software Architecture series, A Pattern Language for Distributed Computing and On Patterns and Pattern Languages.
|
Presentation: "Five Considerations for Software Developers"
Time:
Wednesday 10:30 - 11:20
Location:
Store Sal
Abstract: Those involved in software have a lot to keep in mind as they negotiate the worlds inside and outside of their code and the relationship between them. For those interested in improving the state of their art there are many (many) sources of specific recommendations they can use to sharpen their practice.
This talk takes a step back from the busy, overpopulated and often overwhelming world of such recommendations to focus on five general considerations that can inform more detailed recommendations and specific decisions.
Presentation: "Programmer's Dozen: Thirteen Recommendations for Reviewing, Refactoring and Regaining Control of Code"
Time:
Wednesday 11:30 - 12:20
Location:
Store Sal
Abstract: This talk walks through a 13-point list of recommendations (0 through
12) that can be applied out-of-the-box to reduce code size and complexity, acting as both guidelines for new code and indicators for refactoring.
This short list has no ambition to be all that you needed to know about design (but were afraid to ask), but it does offer an easily memorable and easily practised set of guidelines that offer the greatest immediate return on investment. The recommendations presented are structured as themes and are not necessarily specific to programming language, although concrete examples include matters of class interface and hierarchy design, expression of control flow and logic, and other issues ranging from the apparently minor to the unavoidably major.
|
 |
| |
