Software engineering practices have matured tremendously in recent years, but too often they are applied thoughtlessly and without a true understanding of why or when they might be applicable. Frequently, engineers will debate the "best" or "correct" way to do things without wider reference to the problem at hand. In this talk I will show how a pragmatic approach to quality is required if we are to truly make digital products that matter.
“We launch valuable products,
services and companies that make a
measurable difference to the world.
Whether our iconic game Monument Valley or
innovative technical platform Wayﬁndr, for 10 years
we’ve create products with passion from conception
to launch and beyond.
OF THE YEAR
The ustwo games team conceived and built Monument
Valley in 10 months with continuous user testing with
gamers and non-gamers to achieve a magical and
intuitive puzzle game experience with mass appeal.
We partner with smart clients to launch new
products, services and companies that are of
strategic importance and reliant on innovation.
DO IT “RIGHT”
I am a huge proponent of writing quality code, a view that is shared by many of my
colleagues. Unfortunately, I do encounter those who do not share my enthusiasm.
Their view is often one of “Get It Done,” whereas I take the position of “Get It Done
Right.” - Chris Eargle
5. Your Code Sucks
4. Debts Accrue Interest
3. Repetition Is Dangerous
2. Spaghetti Is Good to Eat, Bad to Read
1. Littering Is Rude
None of these issues
directly concern the
user of the software
IF YOU LEAVE HERE WITH
ONLY ONE MESSAGE, IT
SHOULD BE THIS...