What if everything you knew aboutCode Quality is wrong?

Erwin van der KooghPrincipal Consultant

evanderkoogh

“What would it take to get this out to customers?”

COO of a $30B company

Let’s rewind 6 months..

“What will TV & media consumption look like 5 years from now?”

Same COO

Image © Gunnar Bothner-By

Image © Thomassin Mickaël

The Need for Speed

Image © Pagani. Used without permission

Languages:Hours doing TDD:

Hours spend pairing:Code Reviews:

Highest # of indents:

5+0009

# of tests: 0# of CI builds: 0

You no know how to code?!

“What would it take to get this out to customers?”

COO of a $30B company

Image © ViaCom. Used without permission

Image © CBS Studios Inc. Used without permission

One does not simply

Put a prototype in production

What we thought we build..

Image © https://www.flickr.com/photos/jldugger/

What we actually build

Huh?

Friction Driven Development

Huh?

Our pain?

Everything changed

Our pain?

All the time..

‘Immutable’ Microservices

Huh?

Image © https://www.flickr.com/photos/scott_horvath/

Microservices all the way

down..

Smooth Dependencies

Huh?

Dependencies are evil

You don’t import, but adopt dependencies

Take Aways

Microservices

• Do one thing well • (And that is still not one thing) • Pretty doesn’t matter when it is done • A Module (Group of services) has it own DB • A new version of a service is a new service

Dependencies

• Just don’t do it • Limit your exposure. • Most dependencies are implicit • Complexity is not in the components, but

the interactions