Evfsv4hynyqqx6xmr0p2
Meet up

LDNUG October 2015

Thursday, 15th October at CodeNode, London

This meetup was organised by LDNUG: London .NET User Group in October 2015

Overview

Join London .Net User Group for this meetup to learn from the experts and their experiences. Talks by Pete Smith and Pete Mounce.

Pete Smith: "The myth of the qualified developer"

There's a lot to master in any job, but software engineering takes this to a whole new level. A good developer has to enjoy learning, and of course we usually do this by making mistakes. But what level of knowledge divides a master from a mere competent beginner? How do we know when we've learned enough to do our job properly and consider ourselves fully qualified? In this talk I'll help you to answer these questions by sharing the stories of my own greatest mistakes, and reveal how a lot of them ended up becoming my greatest opportunities. We'll explore what it means to fail (sometimes specatacularly) and most importantly, how to make the most of it. And remember - whether you think you know too much, or too little - you're wrong!

Pete Smith

Pete Smith is a software consultant and speaker based in London with almost 10 years of experience making web applications with ASP.net, specialising in API design and JavaScript browser-based applications. He is the author of Superscribe - an open source routing framework - and HTTP query library Linq to Querystring among others. Just recently he's embarked on a journey learning JVM and Scala.

Pete Mounce: How do you know your code is working RIGHT NOW?

You write your tests and you ship your code, but many teams stop there - "our tests are green, it's in production, let's get onto the next ticket!". But then alarms go off. "But our tests were green! It can't be OUR code... Can it?" Sure it can. Production is a sensitive complicated place. There are loads of variables. Load balancing, numerous servers, different servers, network outages, transient slow downs for no apparent reason, databases with more than a hundred things in them, data that shouldn't be possible, third party dependencies (you know, those things you mocked out)... Oh, and customers - they do really strange things too. When it goes wrong, it costs money per minute. It's a high-stress, high-pressure environment, and continuous delivery can make it worse. I'm going to talk about some of the things you can do to tame the chaos that continuous delivery can enable • make your applications tell you whether they’re working or not • alerts demystified - they're just test automation that runs all the time in production • configuration management - it's just build scripts for servers not code • how to kill environment drift with infrastructure as code

Peter Mounce

I have worked in developer teams, an operations team, and been a generalist shipping software for JUST EAT since 2010 (with a few years doing that elsewhere first). I've lived through cultural and technological change and played a role in effecting it. I had a pivotal role in migrating our platform from a datacentre to the AWS cloud - consequently, we now do tens of deployments a week compared to a tens a year. I've automated systems, tests, servers, and in some cases myself. I've touched many parts of the platform and delude myself that I do an OK job at that.

Thanks to our sponsors

Who's coming?

Attending Members