Location: Methods & Tools trackTime: 2007-11-14 14.00Level: Intermediate
|
|
Marcus Widerberg, Blue Plane, SwedenMarcus works primarily with server side development and has filled different roles such as coach, developer, trainer, architect and project manager in several industrial settings.Marcus works as part of the newly formed blue plane team in helping clients improve their development methods and ensuring a good fit between method and organization.He has been speaking about development methods and techniques for several years. Current interests are testability, software quality and group dynamics.Currently, Marcus is working as part of blue plane to improve the development skills of an already agile team.www.blueplane.se
mawi.org
|
|
Readability - Avoiding Picky Professors and Cowboy CodersFor years on end, readability has been - and will be - studied. It is the holy grail of code everywhere - creating code that is very readable means very maintainable: So any developer can go in and fix that bug, add that feature... At the same time, most coders will have to admit to writing alot of horribly unreadable code (yes, you too), that *somehow* makes its way into production and *somehow* ends up at another developers screen: How and why do we end up in that situation? How bad is it - how important is readability? This seminar will have a look at what readability means, how we go about getting readable code and why we oftentimes end up with the non-readable. Recent years have given us tools that make it so easy to improve the readability factor, which we'll highlight. We'll also discuss how ideas from areas like refactoring, domain driven design, literate programming, good old OOP and design patterns (still) can enlighten our manners at the keyboard. Whether you often end up picking at the bits through a magnifying glass or herd the code forward with your lasso, join us to discuss how we can get a more pragmatic approach!
|
