►
From YouTube: Arsenal Of Democracy: What Open Source Can Learn From the Motor City - Shane Lawrence, Shopify
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Arsenal Of Democracy: What Open Source Can Learn From the Motor City - Shane Lawrence, Shopify
Speakers: Shane Lawrence
Most of us will spend most of the conference learning what's new in the cloud, focusing on developments from the last six to twelve months and discovering what our colleagues are working on in the future. In this talk, we'll break from that paradigm to ground ourselves by taking a look at Detroit's history and the lessons we can learn from its dominant industry. Shane will describe parallels between open source software and manufacturing, explain how lessons learned by automakers in the last century can benefit software development today, and point out potential pitfalls made by industrialists that we should seek to avoid.
A
Learn
a
little
bit
more
about
this
place
and
I
actually
find
Detroit
really
interesting.
It's
always
been
a
place
of
contrasts,
huge
opportunities,
mixed
with
severe
tension,
and
so
I
hope
that
we
can
learn
from
its
history.
It's
got
this
repeating
Underdog
Story,
going
for
it
and
I
I
know
that
we
can
find
some
ways
to
apply
this
to
open
source
and
Tech
in
general.
There's
some
obvious
differences
between
Tech
and
manufacturing.
A
Of
course,
when
I
want
to
scale
something
up,
I
just
keep
control
scale
it,
but
manufacturers
need
to
go,
buy
land
and
hire
people,
and
things
like
that.
So
it's
understandable
that
the
Auto
industry
can't
move
quite
as
quickly
as
Tech
can,
but
that's
not
always
terrible.
Not
all
of
the
rapid
change
in
Tech
is
good
or
even
really
consistent.
A
For
instance,
a
few
years
ago,
I
heard
that
everybody
needs
kubernetes
and
now
I
I
read
on
Twitter
that
nobody
needs
kubernetes,
so
open
source
has
so
many
admirable
qualities,
but
we
should
also
look
for
lessons
from
Big
Tech
and
the
reason
that
I
think
this
is
so
important
for
us
in
open
source
as
well,
is
that
it's
still
dominated
by
a
handful
of
players
that
make
get
viable
and
as
they
go
so
I'll
so
go
we
all
before
I
get
too
far
into
this.
This
is
me.
A
The
tiny
feet
dangling
from
the
carrier
belonged
to
my
kid
he's
two
and
a
half
months
old
and
I.
Just
came
back
from
two
glorious
months
of
leave
where,
like
the
most
complicated
thing,
I
did.
The
entire
time
was
change,
diapers,
so
I'm
kind
of
jumping
right
back
into
the
frying
pan
and
seeing
how
this
goes
with,
like
kubecon
being
my
first
time,
seeing
outside
people
and
doing
work
stuff
in
forever.
A
A
Here's
a
rough
agenda,
the
intro,
that's
what
we
did.
First,
the
agenda
is
what
we're
doing
now.
There's
some
history,
that's
what
happened
before,
but
we'll
be
doing
it
soon.
There
are
lessons,
that's
what
I
hope
you'll
do
later
and
I'll
be
doing
it
less
later,
and
then
the
conclusion
where
we
repeat
what
we
already
did
and
we'll
be
doing
that
last
so
to
get
right
into
it.
This
isn't
comprehensive.
A
If
I
could
give
this
the
detail
that
it
really
deserves,
then
I
would
have
just
like
solved
peace
in
the
Middle
East
before
lunchtime,
but
hopefully
we
can
get
something
out
of
this.
So
instead
I
give
you
a
truncated,
Abridged
approximate
it
and
probably
mostly
wrong
history
of
Detroit.
Our
story
started
with
the
British
and
the
French
fighting
as
they
were
want
to
do
over
places
where
other
people
had
already
lived
for
Millennia.
The
French
noticed
that
there
was
a
Waterway
here
straight
and
forgiving
my
accent.
A
They
creatively
called
it
la
detrua,
which
means
the
straight.
The
British
took
Montreal,
the
French
gave
up
Detroit
and
America,
took
it
in
the
revolution
and
so
I'll
State
without
evidence
that,
as
the
story
goes
in
1812,
Chief
Tecumseh
marched
his
troops
in
circles,
past
Fort,
Detroit
and
Hall
thought
that
there
were
way
more
people
there
than
there
actually
were
got
really
scared
and
surrendered
the
British
kept
it
for
a
while,
but
they
abandoned
it.
A
After
some
ship
sunk
in
a
lake
nearby
and
in
between
all
of
these
wars
among
various
teamonger
governments
themselves,
supported
by
a
Byzantine
Carousel
of
changing
alliances
with
indigenous
peoples,
folks
continue
to
settle
near
the
fort
and
the
town
was
born.
So,
after
that
there
was
a
fire,
a
vote,
a
road
and
waves
of
immigration
that
brought
mostly
white
settlers
from
Europe
and
mostly
black
books
from
the
American
South.
A
As
we
get
into
the
20th
century,
we
get
into
the
industry
that
defined
Detroit.
As
far
as
I
can
tell
modern.
Historians
can
describe
the
mass
murder
of
millions
in
a
cold
clinical
way,
but
if
you
suggests
that
an
individual
truly
changed
the
course
of
history,
they
get
really
emotional.
So
the
so-called
big
man
theories
are
not
in
Vogue
and
it's
fair
to
say
that
the
automobile
was
going
to
be
really
big.
A
It
was
probably
going
to
be
big
in
the
United
States
and
it
was
probably
going
to
happen
here,
but
it
happened
exactly
the
way
that
it
did
happen,
mostly
because
of
Henry
Ford.
Unfortunately,
many
of
the
most
iconic
companies
in
automobile
history
were
led
by
people
whose
economic
success
gave
them
false.
Credence
to
sort
of
repugnant
ethics
and
Henry
Ford
was
an
Unapologetic
anti-semite.
A
It
gets
worse.
Volkswagen
was
started
by
actual
Nazis
and,
of
course,
this
isn't
limited
to
the
Auto
industry.
But
there
is
a
tendency
to
mistake.
Economic
success
for
the
sort
of
like
globally
Superior
intellect
and
to
assume
that
success
in
one
domain
is
going
to
imply
expertise
in
all
domains.
This
is
especially
dangerous
when
it's
combined
with
anti-social,
behavior
and
in
group
bias,
so
keep
an
eye
on
your
founders.
I
am
pleased
to
say
that,
thankfully,
this
is
not
a
problem
in
our
age
and
there
is
peace
in
our
time.
A
Moving
on
we
get
into
just
before
the
20th
century.
Henry
Ford
established
a
car
company
here
in
Detroit.
Does
anybody
know
what
that
company
was
called
I
I
thought
it
was
Ford?
It's
not
so
in
1898,
Henry
Ford
founded
the
Detroit
Motor
Company.
He
made
two
amazing
cars
like
not
not
two
models.
He
made
two
cars
and
promptly
went
out
of
business,
so
in
1901,
Oldsmobile
picks
up
the
slack.
A
Henry
Ford
comes
back
founds.
The
Ford
Motor
Company
in
1904
and
GM
gets
started
in
1908..
So
in
this
way,
Detroit
at
the
turn
of
the
20th
century
was
kind
of
like
an
incubator
for
card
companies,
and
we
see
a
similar
scene
that
played
out
at
the
21st
century
in
Silicon
Valley
in
a
very
different
industry
in
1908
Ford
releases,
the
famous
Model
T.
That's
what
we
see
over
here
and
in
1915
13
of
the
most
popular
car
brands
were
based
in
Detroit.
A
So
you,
you
really
see
the
benefits
of
that
specialization
in
the
early
20th
century
happening
here
and
I.
Think
there's
a
lot
of
parallels
that
we
can
look
at
for
what
happened
100
years
later
in
California
by
the
1920s.
There
was
a
boom
time.
There
was
also
prohibition
and
resourceful
detroiters.
Take
advantage
of
the
proximity
to
Canada
we're
just
across
the
border
was
conveniently
located
a
massive
Distillery
complex
in
1926.
A
This
newfound
wealth
and
the
the
burgeoning
industry
in
the
United
States
had
become
the
largest
industry
in
the
United
States,
and
this
had
some
knock-on
effects
because
whatever
you
need
to
build,
the
cars
is
also
going
to
benefit
from
this
enormous
growth
in
the
Auto
industry.
So
anyone
making
rubber
anyone
making
steel
providers
of
coal
all
of
those
things,
shipping
and
Logistics
they
all
found
that
Detroit's
Auto
industry
was
a
boon
and
in
1927
the
Ford
River
Rouge
Plant
opened
in
Dearborn.
A
It
created
almost
a
hundred
thousand
jobs
in
the
region,
which
is
huge
today,
but
even
bigger
in
1927.,
and
that's
not
all
working
at
the
one
plant
that
includes
Parts
suppliers
and
things
like
that.
But
it's
just
an
enormous
amount
of
opportunity
created
when
that
one
plant
opened
and
dozens
and
dozens
of
plants
are
opening.
Every
year
more
people
were
buying
cars,
even
people
with
earlier
models
of
cars
that
were
still
working
were
just
buying
new
cars
because
they
wanted
a
new
one.
A
They
had
improvements
in
the
industrial
methods
that
were
making
them
more
reliable.
They
were
making
them
safer
and
we've
got
the
model
A
here
it
didn't
even
require
a
hand
crank
to
start.
You
could
just
press
a
button
and
that
thing
would
get
going,
which
sounds
like
a
really
big
Improvement
to
me.
This
also,
though,
led
to
two
troubling
trends
that
I
think
we
see
occurring
today.
So
one
is
an
indecipherable
sequence
of
model
names
and
the
other
is
an
ever
increasing
vehicle
size.
A
Now
in
the
30s,
although
Detroit
was
affected
by
the
depression
along
with
the
rest
of
the
country
and
much
of
the
world,
employment
in
the
industry
continued
to
grow,
albeit
moderately,
throughout
the
30s
and
by
1940.
This
increase
and
migration,
especially
from
the
American
South,
made
Ford
one
of
the
largest
employers
of
people
of
color
in
the
entire
country.
A
In
1942,
though
America
joined
the
war,
they
stopped
all
civilian
production
and
switched
to
military
production,
so
Detroit
was
building
jeeps
and
tanks
and
bombers
instead
of
automobiles,
as
men
joined,
the
military
women
made
up
the
labor
shortfall
and
joined
the
assembly
line
in
record
numbers
like
in
this
photo
from
the
Willow
Run
plant.
Here
it
should
be
pointed
out
that
they
started
working
for
lower
wages
than
the
people
that
they
were
directly
replacing
and
were
asked
to
leave.
When
the
men
came
back,
there's
a
long
way
to
go.
A
It's
now
1945
the
war
ends
and
we
move
back
to
car
production,
and
this
is
not
even
quite
at
the
peak.
Things
are
still
moving
in
a
positive
direction
really
rapidly,
but
one
of
the
the
very
first
of
the
second
and
third
order
effects
that
would
eventually
lead
to
Detroit's
decline,
started
in
1945,
and
that
was
the
Advent
of
suburbanization.
A
So
we
see
in
the
1950s,
the
population
hits
1.85
million
people
and
that's
just
the
the
city
proper
that
doesn't
include
the
outlying
areas,
the
suburbs
other
towns
around
Detroit
and
just
in
the
city
itself,
there
are
almost
300
000
manufacturing
jobs
in
the
city.
Throughout
the
decade,
Detroit
becomes
one
of
the
wealthiest
cities
in
the
world,
and
the
family
car
becomes
a
quintessential
part
of
the
middle
class
white,
suburban
American
Dream.
A
As
we
get
into
the
60s
with
a
large
and
diverse
population,
Detroit
continued
to
have
a
significant
cultural
influence
throughout
the
60s
Motown
changed
popular
music.
It
found
success
across
racial
lines
and
throughout
that
decade
they
had
120
top
20
singles
just
from
Motown
from
artists
like
The
Supremes,
The,
Temptations,
Marvin,
Gaye,
Stevie
Wonder.
But
this
kind
of
betrays
a
lot
of
significant
internal
struggles.
A
Plants
continue
to
move
to
the
suburbs
and
they
brought
the
jobs
with
them.
Detroit
one
of
the
most
diverse
cities
in
the
country
at
the
same
time
had
become
one
of
the
most
segregated,
including
in
the
U.S
South.
Social
assistance
programs
and
affordable
housing
were
withheld
by
local
politicians,
even
when
offered
by
the
federal
government-
and
mostly
this
was
pandering
to
Suburban
populations,
but
pitting
them
against
each
other
sort
of
limited.
The
poor
into
crowded
slums
and
even
middle
class.
A
This
led
to
a
lot
of
tension
when
you
have
people
not
living
amongst
each
other
people.
Thinking
of
each
other
as
sort
of
a
different
entity,
tensions
increased
in
1967,
the
12th
Street
riots
became
one
of
the
worst
riots
in
American
history,
1700
stores
were
looted,
1400
buildings
were
burned
and
43
people
were
killed,
the
National
Guard
and
the
US
Army
were
brought
in.
They
used
tanks
and
machine
guns
to
put
down
the
protests.
The
City's
population
began
its
long
decline
as
we
get
into
the
70s
Japan's
economy
was
booming.
A
And
then
the
1973
oil
crisis
hit
that's
a
totally
different
story,
but
what
it
led
to
was
massive
gas
shortages
and
people
couldn't
get
gasoline
and
when
they
could,
it
was
very
expensive.
This
sort
of
kicked
off
a
positive
trend
here
towards
more
efficient
vehicles,
but
American
Vehicles
were
already
very
heavy.
They
consumed
more
fuel
and
it
took
time
for
the
Detroit
automakers
to
sort
of
adapt
to
this.
At
the
same
time,
the
Japanese
cars
were
already
very
efficient.
A
A
When
we
get
into
the
80s
and
90s
there's
a
shrinking
tax
base.
White
flight
continues.
The
suburbs
are
mostly
maintaining
their
population
at
the
same
level,
but
the
City's
population
is
declining
really
rapidly,
and
the
city
government
is
having
a
hard
time.
Keeping
up
job
losses
are
increasing
as
more
and
more
plants
are
moving
out
to
Suburban
areas
or
closing
all
together
and
as
we
see
that
we
see
more
poverty
and
more
crime
in
the
inner
city.
A
One
thing
that
started
as
just
a
mischievous
tradition
in
the
1930s
was
this
idea
called
Devil's
Night,
where
the
day
before
Halloween
people
would
commit
mischief,
and
it
was
mostly
graffiti
and
minor
acts
vandalism,
but
by
the
80s
and
90s.
This
was
sort
of
a
Tinder
Box
just
waiting
to
explode.
These
turned
into
huge
acts
of
absolutely
malicious
violence.
There
was
rampant
crime
and
in
1984,
for
instance,
in
a
single
night
devil's
night
over
800
buildings
were
burned.
These
arsons
continued.
A
A
in
2008.
The
mayor
was
forced
to
resign
and
he
later
went
to
prison
on
federal
charges
relating
to
corruption
and
by
2010,
the
city
of
700,
000,
now
half
or
less
than
half
of
its
previous
size
has
80
000
vacant
homes
in
2013.
It's
the
largest
U.S
city
to
ever
declare
bankruptcy
and
in
2016,
Detroit's
population
decline,
caused
it
to
fail
to
make
the
list
of
the
20
largest
U.S
cities
for
the
first
time
since
before
the
Civil
War
in
1850
was
the
last
time
that
it
wasn't
in
the
top
20.
A
professor
John
McDonald
from
the
University
of
Illinois
sort
of
analyzed
this
in
an
academic
paper
around
that
time
and
concluded
that
Detroit
suffered
more
than
similar
industrial
cities.
For
three
main
reasons.
One
is
that
the
economy
was
dominated
by
a
single
industry
to
the
political
structure,
encouraged
Urban,
Decay
and
three.
The
competition
for
labor
and
capital
combined
with
racial
animosity
led
a
division
among
the
population.
Now,
obviously,
there's
there's
no
single
paper
that
can
show
all
of
the
comprehensive
reasons
that
all
of
this
was
happening.
A
A
Seeing
some
tech
companies
starting
to
build
Offices
here,
a
number
have
a
presence,
downtown
downtown
Detroit,
as
I'm
sure
you've,
probably
noticed
over
the
last
few
days,
does
not
look
like
the
sort
of
War
Zone
you
might
have
seen
on
TV
and
in
pictures
from
the
90s
or
early
2000s,
and
a
big
part
of
this
is
thousands
of
abandoned
buildings
that
were
Haven
for
Crime
arson
and
other
activity
were
torn
down
and
now
we're
seeing
some
Urban
neighborhoods
are
becoming.
Finally
less
than
segregated
and
city
services
are
improving.
A
So
now
that
we're
caught
up.
What
do
we
learn
from
that?
Where
do
we
go
from
here?
The
city
that
built
itself
up
from
the
Underground
Railroad
in
the
1800s?
That
was
a
production
Power
House,
employing
women
during
the
war
that
brought
people
of
color
into
the
middle
class?
It
became
notorious
for
redlining
for
white
flight,
for
racist
police
for
indiscriminate
violence,
so
I
think.
A
So,
employee,
marginalized
groups
and
increasing
pay
during
boom
times
sort
of
created
this
new
middle
class
for
Detroit's
products.
It
wasn't
just
the
right
thing
to
do.
It
also
made
them
Rich
paying
Fair
wages
is,
was
sort
of
a
quintessential
part
of
Henry
Ford's
proposal
that
I
think
we
can
learn
quite
a
bit
from
and
when
they
employed
mass
production,
it
reduced
the
barriers
to
entry
for
joining
the
labor
force.
He
didn't
need
to
come
from
a
family
of
skilled
Tradesmen.
A
In
order
to
be
able
to
build
a
car,
you
could
show
up
and
be
ready
to
work
and
earn
a
decent
wage.
Doing
that
this,
in
my
opinion,
sort
of
parallels,
the
priesthood
of
computing
that
was
seen
in
sort
of
the
50s
and
60s
you
had
like
large
universities,
defense
organizations
and
a
small
number
of
computer
makers
that
controlled
all
of
the
Computing
equipment
in
the
world,
and
if
you
wanted
to
work
with
them,
you
had
to
work
for
them.
A
When
we
saw
the
Advent
of
the
personal
computer,
it
reduced
those
barriers
and
so
by
the
80s,
it
was
I,
guess
a
little
bit
better.
All
you
had
to
do
was
drop
out
from
Berkeley
or
MIT,
and
you
could
work
on
these
sorts
of
things
in
the
valley
and
it's
improved
even
more
since
then.
Now
we
have
open
source,
and
this
can
be
an
incredible
Force
for
democratization
of
computing.
The
barriers
to
entry
that
used
to
exist
don't
have
to
be
there
to
join
open
source
projects.
Of
course,
education
can
still
be
enormously
valuable.
A
A
Another
thing,
I
think
we
can
learn
from
the
story
of
Detroit
is
in
Supply
Chain
management.
We
saw
the
rise
of
Japanese,
automakers
were
arrivaled
to
Detroit's,
and
one
of
their
advantages
was
something
called
the
Toyota
production
system,
and
parts
of
this
were
imitated
to
varying
degrees
by
automakers
in
the
United
States.
A
They
got
rid
of
warehouses,
and
instead
they
were
just
going
to
produce
enough
parts
for
the
line
to
consume
them,
and
so
they
had
to
find
a
way
to
track
what
was
being
built
and
when
and
they
introduced
the
kanban
system-
and
this
is
actually
I-
think
much
more
valuable
in
software
than
we
might
realize.
Not
because
we
need
to
make
sure
that
we
aren't
storing
too
much
bits,
I
guess,
I,
don't
know,
we
don't
really
need
warehouses
for
that.
A
But
what
we
can
do
with
this
is
identify
what's
going
into
the
supply
chain
and
of
course
it
is
still
a
problem
for
manufacturers
of
physical
Goods
who
are
going
to
keep
track
of
things
and
make
sure
that
authentic
materials
and
authentic
parts
are
going
into
their
supplies.
But
it's
not
as
much
of
a
concern
from
a
security
perspective
for
them,
because
in
order
to
make
fake
Parts
you
need
to
buy
land,
build
a
factory
hire
workers
make
the
faulty
part
and
then
somehow
sneak
it
into
the
supply
system.
A
So
that's
less
of
a
problem
for
them.
For
us,
somebody
needs
to
sit
down
in
their
bedroom
and
log
into
GitHub,
so
I
think
we
should
emulate
the
kanban
system
for
a
slightly
different
reason,
that
is
to
identify
what
parts
are
being
produced
or
what
components
of
software
are
being
produced
and
where
and
make
sure
that
we're
only
putting
safe,
secure
software
into
our
end
products.
A
I
I
think
that
people
think
that
the
s-bomb
is
going
to
be
a
miracle
cure
for
Supply
chains,
and
it's
not
just
like
the
kanban
system
and
its
imitators.
Don't
prevent
mistakes
in
manufacturing.
Identifying
the
components
of
a
supply
chain
doesn't
guarantee
your
security,
but
you
need
to
make
sure
that
it's
up
to
date,
it's
integrated
with
your
deployer
release
pipeline
so
that
you
can
see
what
you're
actually
producing
and
where
it's
all
coming
from.
A
Also
the
components
of
a
specific
build
are
immutable,
but
what
we
know
about
these
components
changes
over
time
as
new
information
becomes
available,
vulnerability
information
needs
to
be
tracked
dynamically,
even
though
the
s-bomb
or
the
component
list
is
a
static
snapshot
in
time.
So
in
manufacturing
you
might
find
severe
defects
after
the
fact
that
threaten
the
safety
of
a
vehicle
and
will
lead
to
a
recall.
A
In
software
we
often
find
that
a
component
has
a
bug
affecting
security
or
maybe
reliability,
and
we
need
to
identify
which
run
times
are,
are
affected
by
this
component,
which
ones
contain
that
component.
And
to
do
this
we
can
aggregate
the
information
from
an
s-bomb
into
a
queryable
dependency
graph.
A
Another
word
from
the
Toyota
system
here
and
I
think
this
is
judoka
I'm,
probably
pronouncing
that
wrong
and
I
feel
weird
departing
completely
from
Detroit's
terminology
to
talk
about
Detroit,
but
all
of
the
domestic
automakers
sort
of
emulate
the
same
thing,
but
they
just
didn't
wrap
it
up
in,
like
one
cool
word,
that
I
can
use
on
a
slide.
So
this
is
where
you
might
have,
if
you're,
for
instance,
putting
interior
components
into
a
car,
you
might
have
a
chromatic
sensor.
A
The
key
takeaway
is
that
you
need
to
enshrine
a
process
where
a
fault
in
one
of
those
components
guarantees
that
it
won't
end
up
in
your
end,
product
and
I
think
a
lot
of
times.
We
don't
do
that
right
now,
either
through
insufficient
detection
of
the
fault
or
it's
detected.
It
throws
a
warning
somewhere,
it's
going
to
be
in
your
build
system
logs,
but
the
artifact
at
the
end
still
gets
produced
and
it
might
be
accidentally
used
in
production
in
the
future
to
detect
problems
as
early
as
possible.
A
You
can
use
static
analysis
tools,
things
like
semgrap.
There
are
lots
of
common
linters
that
you
can
use,
and
at
Shopify
we've
created
a
tool
called
Cube
audit.
We
can
use
that
to
scan,
Kate's
manifests
and
identify
any
that
aren't
following
best
practices,
and
the
real
takeaway
here,
of
course,
is
the
action
that
needs
to
be
taken.
After
all
of
this
is
done,
which
is
alert,
someone
stop
it
from
going
into
production.
A
Now,
standardized
builds
have
been
part
of
manufacturing
for
over
100
years
on
an
assembly
line.
Every
single
machine
is
a
documented
part
of
an
industrial
process.
Manual
steps
are
defined
in
detail
according
to
a
work
construction.
You
have
supervisors
and
you
have
automated
systems
that
ensure
each
step
is
completed
according
to
the
specified
process,
but
standardized
builds
following
an
exact
predefined
process
have
not
been
common
in
tech,
for
whatever
reason
we're
finally
making
some
progress
here
with
things
like
in
Toto
and
the
Sig
store
project
that
are
really
good.
A
The
salsa
framework
is
sort
of
pushing
people
to
start
using
these
things,
and
I
really
hope
that
more
people
will
pay
attention
to
this.
I
hope
that
we're
able
to
make
more
progress
on
this
as
we
move
forward,
we
saw
in
the
late
1980s
that
the
prevalence
of
onboard
computers
led
to
the
need
for
onboard
diagnostic
standards,
and
we
can
see
here
a
scanner
for
OBD,
I,
I,
think
that
might
be
OBD2.
A
This
kind
of
system
can
tell
you
about
problems
with
your
exhaust,
your
timing,
your
fuel
injection
system,
misfiring
and
others,
and
for
Urgent
problems.
It
triggers
the
check
engine
light
so
that
you
know
to
either
take
a
look
at
it
or
go,
find
a
mechanic
who
can
look
at
this
for
you
and
identify
what
the
underlying
cause
of
the
problem
is.
In
this
case,
the
user
is
the
driver,
they
see
it.
They
know
something's,
wrong
and
I'm
sure
they
will
diligently
stop
the
car
immediately
and
have
it
towed
to
the
nearest
mechanic.
A
We
can
use
standardized
metrics
and
things
like
Prometheus,
open,
Telemetry
to
gather
information
about
error
rates,
latency
and
leading
indicators
of
problems.
If
we
miss
those,
then
we
can
see
in
the
logs.
If
we
have
structured
logging,
we
can
compare
different
applications,
output
or
even
the
same
application
over
different
instances,
output
and
see
what
they're
doing
identify
problems
sooner
and
then
we
can
use
real-time
monitoring
alerting
to
ensure
that
when
something
does
go
wrong,
we
flip
on
that
check
engine
light.
A
We
saw
in
the
history
that
Outsourcing
was
a
major
problem
for
Detroit
automakers.
It
contributed
pretty
significantly
to
the
decline.
It's
common
in
manufacturing,
it's
common
in
I.T
and
in
some
corners
of
our
industry.
I
think
most
of
us
probably
haven't
been
affected
yet
in
our
roles,
but
will
it
come
for
us?
A
And
if
so,
what
can
we
do
so
I
think
one
of
the
most
important
things
we
can
do
here
is:
let's
not
assume
that
we're
more
valuable
just
because
of
the
country
or
region
that
we
live
in,
even
when
we
have
specialized
hubs
that
seem
to
create
enormous
value.
Those
can
change
their
fortunes
pretty
quickly
so
find
your
Niche
be
flexible
and
take
inventory
often
you
need
to
know
what
your
competition
is
doing
and
where
they
have
more
strength
than
you
do.
A
One
of
the
leading
factors
in
Detroit's
decline
was
that
there
was
an
enormous
proportion
of
its
industry,
filling
the
exact
same
role
in
the
market.
It
wasn't
just
building
cars,
it
was
building
big
heavy
cars
is
building
cars
that
used
a
lot
of
fuel.
It
was
building
similar
cars,
and
so
so,
when
that
Paradigm
was
disrupted,
it
spelled
enormous
disaster
for
the
city.
A
The
Detroit
automakers
were
really
completely
taken
aback
when
Americans
started,
buying
Japanese
cars
on
mass.
They
understood
already
that
there
was
a
niche
market
for
certain
German
manufacturers.
They
understood
why
people
were
buying
Italian
cars,
but
they
were
totally
surprised
that
people
were
starting
to
buy
Toyota
all
of
a
sudden
and
we
need
to
keep
up
with
the
times.
But
let's
also
be
careful.
A
Some
changes
are
just
obscene
as
anyone
who's
compared
to
62
Fastback
with
today's
monstrous
Mustang
can
truly
attest
to
so
Detroit
created
opportunities
for
marginalized
groups,
it
elevated
the
working
class,
it
pioneered
the
most
important
techniques
for
standardizing
production
that
we
know
of
today
and
had
successfully
imported
a
lot
of
additional
methods
from
other
manufacturers.
It's
enormous
production
capacity
earned
at
the
moniker
arsenal
of
democracy
during
the
second
world
war,
for
its
outsized
contribution
of
armaments
and
equipment,
but
the
economy
was
over
dependent
on
the
Auto
industry.
A
The
population
became
segregated
by
race
and
class
and
a
series
of
leaders
pitted
residents
against
each
other
for
political
gain,
sometimes
corruption
by
emulating
the
factors
that
brought
Detroit's
success
and
cautiously
avoiding
the
traps
that
it
fell
into
that
led
to
so
much
struggling
for
its
residents
during
its
decline,
open
source
and
Tech
at
large
can
be
more
resilient.
More
successful
and
more
equitable,
open
source,
in
particular,
has
the
power
to
democratize
vast
opportunities
presented
by
technology
in
the
21st
century.