►
From YouTube: [2022-07-26] 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).
A
A
A
A
A
A
A
A
A
A
A
A
A
B
B
B
B
B
A
A
A
A
A
A
A
A
C
C
C
C
C
C
C
C
C
C
D
E
E
C
B
B
B
B
B
F
A
F
A
A
F
Gerir
engineering
fellow,
infrastructure:
and
we're
not
there's.
gerir
engineering,
fellow,,
infrastructure:,
1000
engineers
and
various
different
companies
trying
to
solve
these
problems
that
are
different.
Two
different
companies
were
a
similar
scenario:
station,
with
about
600
and
in
aaron's,
I'm
just
not
sure
that.
F
F
F
E
A
A
A
A
A
Marshall
cottrell
principal,
strategy
and
operations
(technical):.
What
we
need
to
do
in
this
working
group
is
like
figure
out
how
we
facilitate
that
process.
And,
specifically,,
I
think,.
When
we
talk
about
the
larger
initiatives,
if
we
don't
have
some
framework
for
engineering
managers
to
coordinate
across
multiple
teams.
A
B
B
B
B
D
Chad,
woolley
senior
engineer,
editor
(he/him):.
I
think
those
two
things
are
tied:
together.,
chad,
woolley
senior,
engineer,
editor
(he/him):.
You
can't
prioritize
correctly,
unless
you
fully
understand
a
scope
and,
to
some
extent
the
context
of
the
architecture
and
the
implications
of
what
the
competing
proposals
are.
C
C
C
C
C
C
C
C
E
E
Andrew
newdigate,
d.e.,,
infrastructure:,
primarily
focused
the
primary
stakeholders
are
engineering,,
but
there
are
other
stakeholders,,
but
primarily
we
trying
to
coordinate
ourselves
on
a
solution
and
align
across
various
engineering
departments
and
qa.
And
you
know,
security
and
engineering
focused
departments.
E
E
A
A
A
A
A
A
A
A
A
A
A
A
A
F
F
F
F
F
F
F
F
F
F
F
F
F
F
Gerir
engineering
fellow,
infrastructure:,
and
it
was
all
for
not
because
it
never
saw
the
light
of
day,,
which
is,
I
think,,
where
the
problem
lies,
like
at
this
point,
I
don't
really
care,.
I
am
just
happy
that
people
are
writing
so
that
when
somebody
tells
me
about
a
problem,
I
can
go
and
read
and
not
ask
82
questions.
F
F
Gerir
engineering
fellow,
infrastructure:,
because
it's
more
than
what
we
have
today,,
which
is
either
issue,
commands
some
random,
epic
or
stuff
on
slack.
So
if
I
have
a
single
place
where
I
can
read
about
a
problem
and
you're
super
happy,
yeah,
but,
again,,
I
think
the
the
the
the
issue
here
is
you
go
through
that
thing.
F
F
F
A
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
yeah,
I
mean,.
I
broadly
agree
with
everything
you're
saying
I
even
mentioned
in
the
last
meeting
that
I
think
architecture
blueprints
in
general
are
some
of
the
best
documentation
that
we
produce
as
an
organization,.
I
think
the
container
registry,
one
in
particular
like.
A
A
A
A
A
A
A
A
A
A
A
F
F
A
F
Gerir
engineering,
fellow,
infrastructure:
the
things
that
we
see
into
something
that
is
more
homogeneous
with
the
stuff
that
is
coming
out
of
the
product,,
because
then
that
will
that
will
give
us
a
good
understanding
of
oh,.
You
know
what
blueprints
are
actually
belong
to
layers
down
inside
engineering
and
what
we
need
to
produce.
F
F
F
F
Gerir
engineering,
fellow,
infrastructure:,
but
there's
gotta
be
a
summarized
in
artifacts
right,,
something
that
you
can
just
hand
over
to
somebody
in
product
or
somebody
in
order
to
eric
to
steve
or
to
christopher
or
to
any
engineer,,
and
they
can
we
get
into
it
and
and
say
okay,.
I
get
this.
I
understand
where
this
begins
and
designs.
G
G
G
G
G
G
G
Joshua
lambert,
director
of
product
management,,
enablement:
we're
going
to
want
to
have
product
help,.
I
think,
to
calculate
the
roi
on
some
of
these
things
like
a
venting
right
like
it's
super
cool,.
What
can
we
do
with
it
like?
Where
should
fall
into
the
backlog
of
other
things
like
fed
ramp
and
vulnerability,
backlog
and
things
like
that.
G
A
A
A
G
G
A
G
G
Joshua
lambert,
director
of
product
management,
enablement:,
and
we
can
start
but
yeah.
I
mean,
I
think,
with
with
dedicated
started
with
a
long
deck
and
then,
once
that
got
kind
of
finally
approved
and
we
had
a
good
day
where
we're
gone.
They
thought,
thank
god,
changes
and
over
into
a
wealth
of
docs.
A
Joshua
lambert,
director
of
product
management,,
enablement:,
yeah.,
marshall,
cottrell,
principal,
strategy
and
operations,
(technical):
and,
and
I
think
also
like
things
like
unifying
our
off
tokens
and
service
accounts
and
stuff.
Like
all
that,,
like
by
definition,
impacts,
everybody
and-
and
I
would
say,
most
teams
probably
have
use
cases
or
opinions
or
like
yeah
that
things
that
they
want
to
see
achieved.
There.