►
From YouTube: [2022-08-23] Next Architecture Workflow
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
C
C
B
B
Andrew
newdigate
d.e.,
infrastructure:,
you
know,
kind
of
vaguely
dynamic
way,,
because
terraform
is
not
designed,.
It's
basically
everything
to
do
with
multiple
regions.,
it's
very
static.
and
ah,
and
they,,
and
they
very
reluctant
to
change
it,.
Because
there's
a
lot
of
issues
about
it.,
so
yeah,.
B
Andrew
newdigate
d.e.,,
infrastructure:
no,,
I
mean
the
the
high
level
abstraction
that
we're
using
is
to
get.
Is
the
get
module.?
That's
the
main
one.,
but
I
don't
know
if
other
ones.
but
yeah,
send
it
to
me
because
I'd
be
interested
in
looking..
But
obviously
the
main
one
is
for
us
is
get
um,,
because
that
is
effectively
a
big,,
careful
module.
C
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
marshall,
cottrell
principal,
strategy
and
operations
(technical):
imported
based
on
like
string
paths,,
and
it
then
it
just
doesn't
like,.
B
C
C
C
C
Marshall,
cottrell
principal,
strategy
and
operations
(technical):
go
over
what
you
put
together.
C
D
Grzegorz
bizon
principal
engineer,,
verify:
I've
been
talking
with
many
engineers
in
the
last
couple
of
weeks
about
what
the
blueprints
are
and
what
we
should
put
into
them,
and
like
from
my
experience,
how
we
are
using
them
mostly
here
at
the
github.
Is
that
a
blueprint
is
this
umbrella
about
epics
and
issues.?.
D
Grzegorz
bizon
principal
engineer,
verify:,
like
the
essential
part
of
that
is,
of
course,,
a
technical
vision,
because,
without
knowing,
like,,
without
describing
the
technical
vision.,
it's
like
impossible
to
itrate,
or
something,,
because
we
don't
know
where
we
are
going,,
but
basically
uh,
blueprint
is
for
me..
It's
a
map
of
how
to
iterate
it's
uh,.
It's
this,,
this,
this,,
this
this
technical
artifact
that
guides
us
throughout
our
iterations.
D
D
D
C
C
C
C
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):
on
the
architecture,
evolution,
workflow
page
as
part
of
that?,
because
I
think
I
think
formalizing,
the
definition
of
blueprint
makes
sense..
But
then
I
think
we
should
use
blueprint
rather
than
architecture,,
evolution,
workflow,
and
in
more
places..
You
know
what
I'm
saying.
D
Grzegorz
bizon
principal
engineer,,
verify:
yeah,.
Perhaps
I
I
think
I
will
think
a
bit
more
about
that
as
I,
as
I
move
forward
with
this
merchandise,
andrew,
such
as
the
trolled
map,,
and
I
think
that
roadmap
is
something
a
little
different,,
because
that
roadmap
tells
you
exactly
what
the
next
point
of
your
journey
is
for
us,
like
the
blocking,.
D
B
Natalia
tepluhina
staff,
frontend
engineer,
plan:,
but
the
classic,
you
know.,
I'm
going
to
build
a
plane,
and
then
there's
a
seven
hundred
and
thirty-seven,
and
that's
a
blueprint,
and
that's.
But
then
your
roadmap
is,
is
that
plus??
You
know
the
seven
hundred
and
forty,
seven,
and
then
the
seven,
five,,
seven,
or
whatever.,
and
that's
your
roadmap,.
And
I
don't
know.
If
that's
what
you
intending
to
say
by
a
map
of
iteration,
because,,
you
know,.
They
both
got
map
in
the
name,,
which
is
the
things
kind
of.
B
D
D
Grzegorz
bizon
principal
engineer,
verify:
and
usually
a
set
of
principles
about
how
we
want
to
move
forward.,
but
we
never
actually
say
exactly
what
the
next
step
is
going
to
be
because
it's
evolutionary
architecture.
after
every
iteration,
you
learn
something
new..
We
want
to
integrate
that
back
in
your
direction
and
adjust
that,
if
needed.
so
in.
In
that
way,
you
will
bring
this
piece
of,.
D
Grzegorz
bizon
principal
engineer,
verify:,
and
that
tells
you
exactly
what
the
next
step
is
going
to
be.,
but
it's
this
artifact.
That
was
with
you
that
you
update
constantly,
and
when
you
don't
really
know
what
the
next
step
should
be,.
You
take
a
look
at
it,
and
it
helps
you
to
decide
how
the
next
operation
should
look
like.
E
D
C
marshall,
cottrell,
principal,
strategy
and
operations
(technical):.
I
think
what
we
want
to
push
people
into
is
documenting
everything
in
the
blueprint
where
you
might
have
documented
implementation
details
in
in
the
issue
and
epic
previously
right.
so
like
we
have
a
tendency
to
like
start
fanning
out
work.
C
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):
as
you
as
you're
working
through
an
initiative,.
You
keep
the
blueprint
up
to
date
with
implementation
details.,
so
it
remains
like
the
source
of
truth.
and
then
your
planning
stuff
is
just
pointing
back
to
to
the
blueprint.
right
like
you're
you're
saying,.
We
plan
to
do.
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
marshall
cottrell
principal,
strategy
and
operations,
(technical):
on
the
marshall
cottrell
principal,
strategy
and
operations,
(technical):
cross
prioritization
framework.,
I'm
working
on
catching
up
with
this
stuff..
So
I'm
working
on
documenting
that
this
week,
I
should
be
done
by
the
next
meeting.
C
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
I'll,
see
I'll,
run
him
down
and
see
if,
if
he
still
wanted
to
do
that.,
if
not,
I'll,
I'll
try
to
take
a
look.
and
then
the
other
thing
I've
been
working
on
is
documenting
what
our
requirements
have
been
for
a
blueprint,,
the
pr.
and
appsite
review
into
a
spreadsheet,.
So
we
can
kind
of.
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):,
I
I
I
I
think,,
like
marshall,
cottrell
principal,
strategy
and
operations
(technical):,
just
having
looked
at
the
actual
pr's.
there's
a
ton
of
documentation
in
like
the
container
registry
migration,
one
that
is
duplicative
of.
What's
in
the
blueprint.
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
marshall
cottrell
principal,
strategy
and
operations
(technical):
jumping
down
to
three..
I
thought
it
was
an
interesting
here,
like
similar
to
justin.
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):
and
it's
ah,.
It's
an
interesting
project,,
because
they're
they're
trying
to
build
it
in
a
way
to
where
it
could
be
productized
and
and
rolled
into
like
the
the
product
in
the
future..
So
I
suggested
to
him
that
it
might
make
sense
to
produce
a
blueprint
for
that
project.
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
wake
up.
marshall,
cottrell
principal,
strategy
and
operations
(technical):.
I
don't
know
if
it
opens
the
door
marshall
cottrell,
principal,
strategy
and
operations
(technical):
too
much
marshall,
cottrell,
principal,
strategy
and
operations.
(Technical):
right,
like
I'm,
trying
to
think
of
like
other
initiatives
like
stuff
that
we
might
do
in
the
handbook,
for
example.
like,.
Would
we
want
that
sort
of
thing
to
be
a
blueprint
that
is
shipped
as
part
of
like
the
get-lab
documentation.
B
B
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
that
that's
what
I
think,
too.
I
just
didn't
want
to
like
from
our
end.
users.
Perspective.
they
don't
care
about
how
we
operate
as
a
company
necessarily
right?.
So
like
the
implementation,
details
of
our
data
platform
or
our
handbook
or
hacky
stack
that
we
use
for
infrastructure,
provisioning.
C
B
Andrew
newdigate
d.e.,,
infrastructure:
why,,
you
know
the
users
don't
have
to
be
the
primary
consumers,
like
another
example.
Would
be,
get
that
dedicated,
and
we
use
some
form
of
blueprints,,
but
we
don't
they
not
intended
for
any
end
users,
basically
only
ourselves
and
our
partners.
C
A
B
Andrew
newdigate
d.e.,
infrastructure:
yeah,
um.,
but
the
the
question
I
have
is
like,.
Do
the
do.
these
docs
have
to
appear
in
the
kit
lab
documentation,,
or
can
they
be
blueprints
in
in
other
places
like
that
are
not
in
the
getlab
kind
of
official
documentation?
does
it??
Does
that
have.?
Is
that
an
assumption?.
B
C
C
B
Andrew
newdigate
d.e.,
infrastructure:
yeah,,
there
might
be
other
places,
with,
say,,
a
team,
that's
doing
a
recruitment
engineering
where
that's
the
case
as
well,,
something
you
know,
data
engineering
to
some
degree
as
well,.
I
mean,
obviously,,
it's
nice
to
have
everything
public,
but
some
subsystem
possible.
C
D
C
D
B
B
Andrew
newdigate
d.e.,
infrastructure:
the
the
issue
kind
of
relies,.
How
much
discussion
there's
been
between
various
people
on
on
the
subject.,
but
there,?
There's
this
kind
of
general
idea
of
of
providing
a
sort
of
self-service
path
for
for
different
organizations
to
kind
of
just
deploy
and
manage
and
run
their
services
much
more
easily
without
having
to
kind
of..
B
Andrew
newdigate
d.e.,
infrastructure:,
we
get
everything
done
through
infrastructure
in
the
way
that
we're
doing
it
at
the
moment
to
kind
of
build
out
an
internal
path.
and
there's
there's
been
some
discussion
around
how
we
could
implement
that.,
but
one
of
the
things
that
I
would
really
like
in
that
is.-
and
this
is
kind
of
building
on
on
what
we're
talking
about
here
to
some
degree,
but
more,.
Maybe
the
service
maturity
model.,
but
I
thought
I'll
just
bring
it
up,
anyway,.
B
Andrew
newdigate
d.e.,
infrastructure:,
and
that
is
that
we
could
say,.
You
know
we
will
let
you
deploy
into
a
staging
environment
without
having
your
observability
set
up.
but
then,.
If
you
want
to
go
into
full
production,
environment,,
there's
going
to
be
more
gates
that
you
need
to
pass
through,
and
like
one
of
those
things
might
be
things
that
we
would
require
from
from
a
blueprint..
So
you
know,
links
across
to
blueprints.,
um,
or
or
even,
you
know,
like.
So
I
think
it's
more
of
the
service
maturity
stuff.
So
like
hard
gateways
like.
B
Andrew
newdigate
d.e.,
infrastructure:,
you
can't
go
to
production
without
your
sol
as
being
well-defined.
um,.
You
know
you're
alerting,
strategies,,
whatever
your
run,
books.
um,,
but
I
do
think
there
is
kind
of
a
tie
in
between
what
we
talking
about
here,
and
that,
and
and
having
like
a
a
set
of
requirements
that
you
can
kind
of
point
out,,
and
maybe
one
of
them
would
actually
be.
where's
your
blueprint?.
B
D
C
C
C
C
C
C
C
C
C
C
C
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):
last
one
number
six.
D
D
Grzegorz
bizon
principal
engineer,,
verify:
hand,,
the
page
that
describes
the
architecture,
evolution
workload.,
it's
a
bit
old..
We
have
not
been
able
to
frequently
update
the
content
there..
We
could
definitely
make
it
much
easier
to
consume
by
people
meeting
that
page.
D
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
oh,,
that's
unnecessary,,
and
we
should
just
go.
mr.
first,
grzegorz
bizon
principal
engineer,
verify:.
I
think
that
those
steps
are
there,
because
of
the
reason,
for
example,.
The
reason
why
there's
the
google
step
was
that
at
some
point
we
were
really
afraid
about.
D
Grzegorz
bizon
principal
engineer,
verify:,
like
exposing
some.,
no
public
information
about
our
uh,.
You
know,
uh,,
far-reaching
initiatives.
uh,,
but
we
can
probably
simplify
the
steps.,
the
workflow
itself,
a
bit..
I
I
feel
like
we
should.
D
D
Grzegorz
bizon
principal
engineer,
verify:
this
content.
We
have
there.,
I
feel
like.
There
are
many
reasons
for
how
why
it
looks
like
it
does
right
now,,
but
still
there
is
a
lot
of
room
for
improvement
in
there,,
so
I
will
try
to
start
working
at.
oh,.
I
will,
on
a
separate
request.
uh,
to
simplify
this
picture.
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
okay,,
I
think
action
items
pretty
much
remain
the
same
from.