Thirty years after its publication, Donald Norman's seminal book "The Design of Everyday Things", which examined how the tiny usability touches in everyday items matter so much, remains relevant and important. In fact, Don just this year wrote that the technology industry badly needs to re-focus on the true meaning of Human Centered Design, observing that despite his decades of advocacy, the same kinds of design flaws continually recur.

We are just a handful of years short of the centenary of the publication of Modern Architecture pioneer Le Corbusier's maxim "A house is a machine to live in", yet our architecture remains stubbornly steam powered.

My position is that we ought step back and critically reexamine the shape and detail of our workplaces and homes, and in particular how we interact with the computer software that is coming to pervade our workplaces, vehicles and even bodies. The great labour saving devices of the 20th century freed us from much physical drudgery, but significant cognitive burden remains. I will examine, in the abstract and concrete, how much cognitive load is imposed on us by our environment; it has been written that a modern human makes approximately 30,000 choices every day.

For example, why are our light switches placed for the convenience of builders, not inhabitants. Why do so many of our labour-saving appliances require us to spend so much time monitoring and pampering them. Wouldn't it be great if your various "intelligent agents" could work thing out among themselves without involving us. How often do you stumble about in the dark fumbling for a light switch. Wouldn't you prefer to discover the failed refrigerator or flooded storeroom before the contents are ruined?

Join me for an imagination of how Living In The Future could truly be better.

Functional programmers are lovers of simplicity and order. Developing for the Web has become nothing like either of these. The number of tools and libraries you need to learn seems to multiply without end, and getting them to work together can be a nightmare.

What if there was a language and environment that had no external dependencies, required no complex packaging tools, runs in the web browser, and oh yes, it's purely Functional.

The Elm Architecture (consisting of the Elm functional language, and a way of applying it to web development) aims to allow fast iterative development of beautiful web apps in a functional language. Hundreds of easy-to-install libraries give you

Most elm tutorials stop at the "hello world" level and sweep the complexity of large applications under the carpet. This presentation goes beyond the bare essentials to show you how my team builds real world applications in Elm that incorporate non-elm javascript libraries while still retaining as much of possible of the simplicity, type-safety and ease of refactoring that Elm brings.

Ports are Elm's mechanism for interaction with the non-functional, loosely typed Javascript runtime. I'll show you practical ways to interact with tools such as Amazon Cognito and the Leaflet mapping engine from within your Elm application, keeping the non-functional glue code to the barest minimum.

The Internet of Things is undeniably here. In the last year we have heard tell of of security cameras, dishwashers and even ovens roaming the internet unsupervised. As a consultant and writer about the Internet of Things, I have worked to bring my experience from 20 years in manufacturing and internet security to the IoT world. This presentation will cover the tools and techniques I use to build secure, reliable and rapidly updatable IoT devices. The techniques covered are applicable to both the simplest embedded devices with no general-purpose OS, and more powerful devices running Linux or Windows.

The Internet of Things (IoT) is really about the ubiquity of data, the possibility of humans extending their awareness and reach globally, or further.
IoT frees us from the tedium of physically monitoring or maintaining remote systems, but to be effective we must be able to rely on data being accessible but comprehensible.

This presentation covers three main areas of an IoT big data strategy

• The Air Gap - options (from obvious to inventive) for connecting wireless devices to the internet
• Tributaries - designing a scalable architecture for amalgamating IoT data flows into your data lake. Covers recommended API and message-bus architectures.
• Management and visualisation - how to characterise and address IoT devices in ways that scale to continental populations. I will show some examples of large scale installations to which I've contributed and how to cope with information overload.

The Internet of Things is undeniably here. In the last year we have heard tell of of security cameras, dishwashers and even ovens roaming the internet unsupervised.

As a consultant and writer about the Internet of Things, I have worked to bring my experience from 20 years in manufacturing and internet security to the IoT world. This presentation will cover the tools and techniques I use to build secure, reliable and rapidly updatable IoT devices.

The techniques covered are applicable to both the simplest embedded devices with no general-purpose OS, and more powerful devices running Linux or Windows.