I attended #LeadDevLondon this year, it was a nice and different conference. Generally, I have attended more language-specific conferences. There were basically no language-specific talks at all during the conf, as everything was a bit more general about building and working well with technology teams. Given that these days a large part of what I do is manage teams of devs, it was good to hear other folks talk through some of the challenges and solutions they have gone through during their journey.
My swag bag full of stickers
For my very favorite slide see the section with my tweets below ;) Otherwise, enjoy some favorite slides with little to no context ;) You can generally find the full presentation slides on the talks page and the full videos of the #LeadDevLondon talks on youtube.
@alicegoldfuss explaining containers
@alicegoldfuss explaining what else ops does ;)
@alexhillphd going over the art of code reviews, this talk had my favorite slide of the conf
@cmccarrick how to scale yourself and make important decisions
@tara_ojo on how to help Jr’s with good 1:1s
@nmeans lessons learn from 3 mile island
@dbussink shows how distributed his team is
@dbussink explains how to make that an advantage
@WebDevBev on how to run awesome internships
@jqiu25 the journey to safe ways to edit production data
I guess I really liked what @ramtop had to say about legacy code
One thing I noticed and really came away with from the talks is that every piece of advice and best practice really fits into part of a companies growth curve. Even the most agreed on advice can’t and shouldn’t apply the same to a single person startup and a company of thousands of people and hundreds of engineers. This made me crave a talk that opposed to saying how some team approaches a challenge and the ways it works for them, but how a best practice or process changes and adapts to different growth stages of a company…
As a single talk, an example let’s consider continuous delivery of the growth of a team. While the end best practices involve style checkers, peer code review, automated test suites, deployment to one or more staging, and feature flag or percentage based releases to production, before/after metric analysis on the impact of deploys… It would not be possible to start there nor would it be sensible to set up all that complexity when just getting started… I feel like the flow would naturally look something more like this.
I think it would be great to see detailed talks on tech org structures, testing, monitoring, alerting, etc..
Some of the tweets I shared during the conf.
Great to see some old friends at #LeadDevLondon and introduce them to Theo... @mariagutierrez got a nice hug... pic.twitter.com/bUIjOUrdff
— Dan Mayer (@danmayer) June 27, 2018
My favorite slide from #LeadDevLondon so far.. Also, why our team tries to have linters as part of our CI build... Have higher level PR discussions... pic.twitter.com/9gandnj3Q5
— Dan Mayer (@danmayer) June 27, 2018
Thanks #LeadDevLondon after the conf, Theo got to see the analytical engine and difference engine at the London Science Museum... Which is fun since I am reading him a book about Ada Lovelace and Charles Babbage. pic.twitter.com/sK6VxRnhaQ
— Dan Mayer (@danmayer) June 28, 2018
Seriously, thanks to all the sponsors and friends handing out stickers. I love collecting stickers at conferences to come back and cover my climbing wall. I am building a large collage covering the entire climbing wall in layers of stickers. After returning from a conference I always have a huge collection of stickers to use, which is great. In this case, I basically was able to make an entire tile of my climbing wall a #leaddevlondon tile full of stickers I picked up during the trip.
If you don’t know what to do with all the stickers you have collected at various conferences, feel free to send them my way ;)