It's been 10 years since Roy Fielding first defined REST in his dissertation on Architectural Styles and the Design of Network-based Software Architectures. Since then, REST is often held as the standard for usable, well-designed, easy-to-integrate APIs.
At the Cloudstock hackathon December 6th, 2010, Brian Mulloy presented "Teach a Dog to REST," asking the question: where are all the elegant REST APIs we'd all hoped to see? While many claim REST has arrived, many APIs in the wild exhibit arbitrary, productivity-killing deviations from true REST.
In this presentation, Brian starts with a typical poorly-designed API and iterates it into a well-behaved RESTful API. Check out the presentation for rules and advice on how to do REST right, including handling complex variations, pagination and API versioning.
The current state of the Web platform makes working with, and maintaining lots of HTML and CSS a painful task. Even modestly-sized applications can quickly end up with tens of thousands of lines of HTML and CSS. And dozens of developers may need to work with the UI code on a daily basis.
Without an HTML/CSS application architecture, things can quickly get out of hand. This talk will look at the design of the SUIT framework, and the use of tooling to support and test HTML/CSS development.
These days it's easy to get started building a Single Page Application (SPA). Dozens of frameworks are clamouring to pitch their trivial "hello world" and "todo list" examples. But the moment you step outside the predefined path and begin actually crafting something for a real business, you face an explosion of choices.
This talk is about experiences of building large SPAs and maintaining them over time. In part, I'll demonstrate pros and cons of various technology choices, such as TypeScript, Grunt, and AMD module optimisers. In part, I'll demonstrate some Knockout.js-specific techniques, such as the new and powerful "components" feature that improves maintenance, testability, and runtime performance.
Since Kent Beck wrote the book on TDD in 2002 a lot of words have been dedicated to the subject. But many of them propogated misunderstandings of Kent's original rules so that TDD practice bears little resemblance to Kent's original ideas. Key misunderstandings around what do I test, what is a unit test, and what is the 'public interface' have led to test suites that are brittle, hard to read, and do not support easy refactoring. In this talk we re-discover Kent's original proposition, discover where key misunderstandings occured and look at a better approach to TDD that supports sofware development instead of impeding it. Be prepared from some sacred cows to be slaughtered and fewer but better tests to be written,