Dylan wrote his first web page in 1992 and never looked back. He’s the systems architect at Spotlight, the UK’s leading casting service for professional actors. Dylan works on distributed systems, ReST APIs and microservices, and the challenges involved in introducing scalable architecture in a company where legacy systems generate most of the revenue.
Dylan a frequent speaker at conferences and user groups, where he’s spoken about topics including continuous delivery, Conway’s Law, front-end development, OAuth2, federated authentication and ReST. Dylan lives and works in London, and when he’s not wrangling software he’s into guitars, skiing, diving, beer, Lego, Africa, cats and hats.
Session: Life, Liberty and the Pursuit of APIness : The Secret to Happy Code
We spend our lives working with systems created by other people. From the UI on our phones to the cloud infrastructure that runs so much of the modern internet, these interactions are fundamental to our experience of technology – as engineers, as developers, as users – and user experiences are viral. Great user experiences lead to happy, productive people; bad experiences lead to frustration, inefficiency and misery.
Whether we realise it or not, when we create software, we are creating user experiences. People are going to interact with our code. Maybe those people are end users; maybe they’re the other developers on your team. Maybe they’re the mobile app team who are working with your API, or the engineers who are on call the night something goes wrong. These may be radically different use cases, but there’s one powerful principle that works across all these scenarios and more. In this talk, we’ll draw on ideas and insight from user experience, API design, psychology and education to show how you can incorporate this principle, known as discoverability, into every layer of your application. We’ll look at some real-world systems, and we’ll discuss how discoverability works with different interaction paradigms. Because, whether you’re building databases, class libraries, hypermedia APIs or mobile apps, sooner or later somebody else is going to work with your code – and when they do, wouldn’t it be great if they went away afterwards with a smile on their face?
Audience level: technical, intermediate. Language-agnostic but developer-centric.