Tickets for NorDevCon on Friday the 28th of February 2014 are on sale now! You can buy your ticket by following the link below:
There are 50 Super Early Bird tickets at £50 + fees and 450 Early Bird tickets at £75 + fees. We are offering significant discounts for students and the unemployed. Please email firstname.lastname@example.org for details. There are 80 places for the conference dinner (3 courses, 2 glasses of wine and speakers!) and tickets are £35 + fees. The Virgin Wines reception is free to attend for conference attendees and there are 80 places.
Check out the website for the confirmed speakers, sessions and programme:
Speakers for the remaining slots will be announced over the next few weeks. The call for papers is now closed.
Please find details of further highlights in the second part of Winter Is Coming below.
The Conference DinnerThe conference dinner will be held in the evening following the conference. In this unique experience the speakers remain seated while the conference attendees move round between courses. This is your opportunity to speak to your favourite speakers of the day. Last year the conference dinner was one of the highlights of the conference and sold out! Please make sure you purchase your dinner ticket at the same time as your conference ticket. You can view the menu here.
The Virgin Wines ReceptionVirgin Wines will be hosting a reception at the venue between the end of the conference and the start of the conference dinner. As well as a glass of wine courtesy of Virgin Wines there will also be a bar. Places are limited so please make sure you get your free Virgin Wines reception ticket at the same time as your conference ticket.
The Architecture of UncertaintyRalph Johnson defined architecture as "the decisions that you wish you could get right early in a project, but that you are not necessarily more likely to get them right than any other". Given our inability to tell the future how can we design effectively for it? Much project management thinking is based on the elimination of uncertainty, and advice on software architecture and guidance for future-proofing code often revolves around adding complexity to embrace uncertainty. In most cases, this is exactly the opposite path to the one that should be taken.
The talk looks at how uncertainty, lack of knowledge and options can be used to partition and structure the code in a system.
Applied API designIt's all very well seeing toy examples of API design where only snippets are required, but what does a good API look like in a complete application?
In this live coding session, Jon will be applying his love of all things immutable, separation of concerns and other design goodness to a certain well-known shape-dropping game. We'll explore different approaches - including ones from the audience - as we go along, but end up with a clean model which works equally well when using WPF, a console-based view... or playing by email. Unlike some other sessions where Jon has shown some truly horrible, unreadable, twisted, evil code the aim here is to end up with an example of elegance and beauty. That doesn't mean we can't visit a few evil notions along the way, of course...
Spock: the test framework of choiceJUnit, a derivative of sUnit, was the unit test framework of choice with Java for many years. Then came TestNG and changed the scene: testing was about integration and system test as well as unit testing. With behaviour-driven development (BDD) augmenting test-driven development (TDD) more development of test frameworks became necessary. There are a number of Java frameworks for this but Spock, which is a Groovy-based system, knocks them all for six.
Because Groovy is a dynamic language that works with the Java data model, it is symbiotic with Java. Spock can therefore be used for testing mixed Java and Groovy systems.
In this session we will explore what Spock can do and why it is the Java testing framework of choice.
Actively involved with Python, Groovy, GPars, GroovyFX, SCons, Java, and Gant. Also Gradle. And Python-CSP. Seriously interested in Ceylon, Kotlin, D, Go, Rust.
Russel’s stance on testing: it isn't optional. Spock, py.test, Catch, etc. are your friends.
Originally publisher here.