Search
Programme
Register
About Us
 

Watch the

Videos

 

Book your

Hotel

 

Build your

Schedule

 

Relax

Xtra(ck)

 

Track overview

Tuesday: NoSQL Day

WednesdayThursdayFriday
JavaJavaJava
.Net.Net.Net
Smart phonesSmart phonesSmart phones
ArchitectureCloud & nosqlPatterns
Web developmentWeb developmentSocial media
AgileAgileAgile
CollaborationRealizing business ideasSoftware craftsmanship
Xtra(ck)Xtra(ck)Xtra(ck)

Speaker: Neal Ford

Neal Ford is Software Architect and Meme Wrangler at ThoughtWorks, a global IT consultancy with an exclusive focus on end-to-end software development and delivery. He is also the designer and developer of applications, magazine articles, presentations, and author and/or editor of 6 books spanning a variety of technologies, including the most recent The Productive Programmer. He focuses on designing and building of large-scale enterprise applications.

Website

http://nealford.com

Twitter

http://twitter.com/neal4d

Emergent Design

Track: Agile, friday 11:20 - 12:10

This session describes the current thinking about emergent design, discovering design in code. The hazhard of Big Design Up Front in software is that you don't yet know what you don't know, and design decisions made too early are just speculations without facts. Emergent design techniques allow you to wait until the last responsible moment to make design decisions. This talk covers three areas: emergent design enablers, battling things that make emergent design hard, finding idiomatic patterns, and how to leverage the patterns you find. It includes both proactive (test-driven development) and reactive (refactoring, metrics, visualizations, tests) approaches to discovering design, and discusses the use of custom attributes, DSLs, and other techniques for utilizing them. The goal of this talk is to provide nomenclature, strategies, and techniques for allowing design to emerge from projects as they proceed, keeping you code in sync with the problem domain. This talk shows lots of examples of how to make this concept work in your environment.

Testing the Entire Stack

Track: Java, thursday 14:15 - 15:05

Most talks you see about testing cover one particular tool, and rarely delve into the strategies around when you should use a particular tool for a particular kind of testing. This talk differs because it covers testing the entire stack: unit, integration, functional, behavior-driven, databases, user acceptance, mocking & stubbing, and other topics and strategies. I discuss the merits of "known good state" vs. "nuke & pave" for databases, discuss the differences between ClassicTDDers vs. Mockists and how they approach testing. Throughout, I provide strategies and heuristics to help guide you when making decisions about how, when, and why you are testing some part of your infrastructure.

Øredev founded by: Jayway

Contact us | Archives | telephone: +46 (0)40 - 602 3134 | fax: +46 (0)40 - 127276 | email: info@oredev.org