►
From YouTube: Dev Engineering Group Conversation
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
Hello,
everyone
and
I'm
getting
this
group
conversation
today
for
the
Deaf
sub
department
or
section
as
it
is
called
now
getting
that
started
today
and
welcome
everyone
and
I
hope
everyone
found
still
to
us
because
of
the
Google
Calendar
downtime,
don't
reload
Google
Calendar,
that's
my
first
advice
for
today
and
then
everything
will
still
be
fine,
and
apart
from
that,
please
take
a
look
at
the
slides.
Put
your
questions,
even
the
document
or
verbalize
them
straight
ahead.
So
let's
get
started
with
Christopher
who
asked
kindly
the
first
question,
so
please
verbalize
your
question.
Sure.
B
A
A
We
rather
focused
first
to
get
elastic,
search
running
only
for
the
group
get
led
org
and
that
made
it
usable
that
make
it
make
it
digestible
and
from
dead
start
on,
we
were
now
able
to
get
it
run,
and
the
dog
fooding
make
such
a
difference,
because
we
found
a
couple
of
topics
that
we
are
already
mentioned
by
customers
and
even
contribute.
We
had
some
chats
and
that
also
picked
up.
We
we
felt
really
the
speed
in
the
performance
of
the
whole
thing
so
as
linked
in
the
slides.
A
C
Thanks
Tim,
the
first
thing
I
was
gonna.
Mention
is
basically
exactly
what
you
just
said
about
dogfooding
and
just
how
important
it
is
that
we,
how
great
it
is
that
we
finally
found
a
way
to
dog
food
this
and
get
left
at
home
without
having
to
enable
it
for
everything
and
honestly,
we
should
have
done
that's
far
far
the
moment.
We
realized
that
this
is
an
important
thing
for
our
enterprise
customers.
Even
though
you
know
we
were
not
in
the
place
where
we
could
nail
it.
C
We
should
have
much
earlier
figured
out
a
way
dog
food
at
least
part
of
it,
and
the
fact
that
we
are
now
going
to
be
able
to
do
that
is
going
to
be
very,
very
valuable,
ultimately,
the
hardest
part
in
the
whole
elasticsearch
story.
We
haven't
gotten
there,
yet
that's
gonna,
be
the
whole
index
size
situation.
Honestly,
from
the
moment,
we
decided
we
want
to
have
an
MVC
on
this
specific
group
and
get
that
become
the
things
that
needed
to
happen
were
relatively
straightforward.
It
still
took
time.
C
Obviously
we
ran
into
a
lot
of
bucks
that
needed
fixing
again.
That's
also
value
of
us.
Actually
trying
to
do
this
at
the
skill
and
at
this
environment,
but
the
hard
part
didn't
last
a
search
story,
for
it
gets
a
comment
still
ahead
of
us,
because
we
need
to
produce
that
index
size
or
find
a
way
to
get
it
to
a
place
where
we
can.
C
You
know
responsibly
turn
this
on
for
Alec,
get
that
home
and
we're
definitely
not
there
yet
I
think
the
lessons
when
we
look
back
at
getting
there
will
be
more
interesting
than
the
lesson
surrounds.
You
know.
How
do
we
modify
this
in
a
way
that
we
can
enable
it
only
for
a
subset
of
groups?
Of
course,
it's
great
that
that
was
done
and
over
just
a
lot
of
work
went
into
that.
A
Thanks
a
lot
who's
next
I'm,
not
a
question
from
the
audience.
Please.
D
May
10
minutes,
Mac
I'll
check
it
up.
So
the
last
slide
you
mentioned
security
release.
Theater
is
moved
to
dev
instance,
but
we
also
have
another
overarching
effort
to
move
it
back
to
calm
in
a
step
in
a
private
project.
Is
that
like
a
MVC
intermediary
step
for
now,
because
that's
everybody
else
is
doing
and
what
what's
the
long-term
plan
there?
D
A
E
Exactly
we're
trying
to
follow
the
same
sort
of
pattern
that
give
up
has
and
on
the
private
yeah
Debbie
I
get
lapto
org
side.
We
have
a.
We
have
a
security
harness
now
so
that
you
can
only
push
to
that
specific
remote
and
before
it
was
just
a
private
fork.
So
it
was
really
easy
to
accidentally
pushed
up
or
make
a
merge
quest
go
out
to
the
public
free
pony.
Then
you
have
to
rush
to
get
it
up
or
to
production.
E
F
So,
but
by
reading
those
lights,
it
gives
me
the
perception
that
it's
internationalization
for
Ruby
and
for
the
other
languages
are
being
done
like
in
this
big
merger
class.
Like
merger,
everything
in
one
in
one
chunk
internationalization
can
also
be
done,
like
small
chunks
and
be
murdered
earlier,
if
you're,
just
waiting
for
a
flip,
the
the
switch
in
the
this
big
magic
was
maybe
I
should
split
it
and
ship
it
earlier.
G
So
I
can
take
this
one
since
some
managing
manager
who's
working
on
the
internationalization
and
stuff.
So
we're
not
doing
one
big
wedge
requests
for
this.
What
we're
and
we're
actually
doing
completely
the
opposite
right,
I
think
we're
all
trying
to
make
deliver
everything
in
small
iterations
as
much
as
possible,
so
we're
breaking
up
as
many
internationalization
updates
as
much
into
small
merge
quest
as
possible.
G
Maybe
I
could
have
been
better
in
the
wording
of
the
slide
and
that
we
are
waiting
to
merge
the
linter
into
master
so
that
it
will
be
linking
all
the
merge
requests
that
are
coming
in
for
untranslated
strings,
at
least
in
the
cases
that
we're
catching
right
now
so
other
than
that
you
know
each
one
is
happening.
Iteratively
all
the
auto
fixes
are
being
added
iteratively,
so
yeah,
no
big.
G
A
H
I
Go
ahead
and
spoil
it
first
and
then
okay
recently
and
that's
December
and
January
people
started
to
ticket
any
team
and
both
of
them
had
no
prior
knowledge
of
Ruby.
They
did
have
prior
knowledge
in
other
dynamic
languages,
but
Ruby
wasn't
one
of
them.
So
if
kids
only
will
hire
more
engineers,
that's
probably
the
route
we're
gonna
take
here
as
well.
A
Thanks
and
yet
my
two
lines
that
I
want
to
add
is
that
we
are
also
looking
at
pooling
the
composition,
as
as
my
other
head
at
the
moment,
with
verified
release
in
package
interim
position.
They
are
also
looking
into
having
more
compact
round
for
different
areas,
so
we
are
also
looking
because
the
pooling
situation
cannot
always
give
you
a
measure
and
better
and
more
stable
pipeline
of
candidates,
because
it
then
you
are
not
like
opening
up
or
we
found
someone
and
it
closed
it.
For
two.
A
B
Is
a
conversation,
so
one
thing
that
I
just
did
was
I
did
a
quick
look
on
jobs,
a
job
supply
and
nothing
jumped
out
at
me
to
kind
of
call
set
out
for
an
advertisement
perspective.
So
if
we're
good
that
direction
10,
let's
get
a
proposal
together
to
get
that
updated.
So
we
can
better
reflect
that
either
either
be
a
separate
polls
or
within
potentially
the
back
end
engineering
generic
description.
B
J
So
I
had
actually
maybe
three
or
four
weeks
ago
come
across
this
blog
post.
We
wrote
in
March
about
our
attempts
for
bringing
a
last
search
and
scaling
Alaska
surgeon.
It's
great
to
see.
We've
learned
a
bunch
of
lessons
in
this
slide.
I'd
love
to
see
that
updated.
The
kind
of
end
of
that
blog
post
is
but
we're
still
trying
and
it'd
be
great
to
have
a
follow-up
that
says,
and
we.
H
J
I,
don't
know
how
blogs
work
if
you
should
do
an
update
like
that
or
do
a
follow-up
follow-up
seems
worthless.
I,
don't
know
how
blogs
work.
I
do
blog
for
an
update
or
a
follow
up
would
seem
more
appropriate
since
it
ends
with
kind
of
a
like
and
we
kept
trying-
and
there
seems
like
enough
content
in
my
mind,
based
on
ok
improvements.