As a longtime reader of InfoQ, QCon has always been on my radar. In its 11th year, I managed to attend QCon London. For those that haven’t heard of QCon, it’s a top-notch software development conference, held all around the world. It’s spread over three days with each day broken into tracks. Each track has a particular focus, such as “Architecting for Failure”, “Containers: State of the Art” or my personal favourite “Security: Lessons Learned From Being Pwned”.

Overall, I found the conference to be of a superbly high quality. The talks were relevant and well delivered, the venue ideal and the food abundant. What follows are my takeaways from day 1.

The Talks

  1. Strategic Code Deletion with Michael Feathers
  2. Using Quality Views To Tackle Tech Debt with Colin Breck of Tesla
  3. Continuously Delivering Security In The Cloud with Casey West
  4. From Microliths To Microsystems with Jonas Bonér
  5. Building a Data Science Capability From Scratch with Victor Hu
  6. Crushing Tech Debt Through Automation at Coinbase with Rob Witloff

Strategic Code Deletion

  • If you don’t already have it, a test coverage metric is a great place to start measuring tech debt
  • Mutation testing is an even better way of measuring true test coverage, but the tooling is pretty lacking
  • If code has very little value, consider removing it
  • Mentions of using Martin Fowler’s “Strangler Application” approach

Using Quality Views To Tackle Tech Debt

I recommend that you checkout Colin’s blog post for the details on Quality Views.

Continuously Delivering Security In The Cloud

  • A moving target is harder to hit so regularly create and destroy containers — this helps to ensure an attacker does not gain persistence
  • Secrets can be rotated using a secrets manager like Hashicorp’s Vault

From Microliths To Microsystems

A summary of the talk can be found on InfoQ.

  • Reactive Design Principles help when developing microservice architectures
  • Separate stateless behaviour from stateful entities in a microservice architecture — this helps with scaling
  • References to Pat Helland’s paper “Data on the Outside versus Data on the Inside”
  • Use Domain Driven Development, but don’t focus on the things (nouns), instead focus on what happens (events)
  • CQRS and Event Sourcing mentioned as a useful techniques

Building a Data Science Capability From Scratch

Although a good talk consisting of first-hand experiences, there wasn’t a key takeaway for me.

Crushing Tech Debt Through Automation at Coinbase

  • We need to move fast to survive, technical debt slows us down
  • Build in automated guardrails to ensure that we can move fast without bringing down production
  • Everyone at Coinbase can deploy a tested master branch to production
  • Focus on building a blameless culture
  • Create archetype projects to speed up creation of new services
  • Do security checks in the build pipeline
  • Hashicorp’s Vault mentioned again here
  • Coinbase uses Docker — no container lasts for more than 30 days

That wraps it up for Day 1. Day 2 can be found here and day 3 will follow shortly.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s