►
From YouTube: Engineering Dev Section Call - December 2019
Description
Looking back at 2019 and an outlook to the next quarter for the engineering Dev Section
A
So
this
is
how
it
caught
it
sounds
when
a
German
computer
is
saying
it
starts.
Recording,
let's
get
started.
I
will
share
my
screen
on
top
of
that
and
yeah.
Thank
you.
Everyone
for
joining.
This
is
the
first
time
that
we
are
doing
this
experiment
of
a
deaf
section
called.
The
idea
is
quite
simple:
I
would
like
to
do
this
on
a
regular
basis
we
receive
perhaps
every
second
month
or
once
a
quarter
or
something
like
that.
A
It's
simply
to
let
you
know
what
happened
last
couple
of
months,
especially
for
everyone
who
just
joined
and,
on
the
other
hand,
give
everyone
a
little
bit
of
perspective
where
we
are
going.
What
is
going
on?
There
is
simply
a
lot
of
information
happening
all
the
time
we
get
left
so
I
think
summarizing
that
in
in
a
short
form
in
a
short
meeting
and
hearing
all
the
feedback,
which
is
the
most
important
part
and
giving
you
all
your
questions,
and
hopefully
I
can
and
me,
and
the
rest
of
the
team
can
answer
all
of
them.
A
A
A
A
Do
it
so
that's
great
to
see,
but
it's
also
really
important
by
the
help
of
other
people
who
reviewed
resumes
assessments,
interviews,
everyone
that
was
an
onboarding
body
and
everyone
that
is
simply
very
open
and
very
helpful
for
all
our
team
members,
and
here
there's
a
lot
in
in
the
first
skip
levers
and
a
lot
of
personal
feedback
where
people
are
like
yeah.
It's
awesome.
A
My
onboarding
time
was
there's
a
lot
of
new
stuff
happening,
but
one
of
the
main
things
that
stood
out
to
a
lot
of
people
is
simply
how
helpful
everyone
is,
and
this
is
apart
from
everything
that
we
can
do
on
a
process,
never
end
that
we
can
do
on
a
tooling
level.
I
think
this
is
one
of
the
most
important
things
that
we
simply
help
a
lot,
the
people
that
are
actually
joining,
and
thank
you
for
that.
A
Thank
you
for
11
releases
this
year
we
have
done
five
thousand
999
much
requests
until
yesterday.
I'm
pretty
sure
I
hope
that
we
have
across
the
mark
five
thousand
one
hundred
by
now.
We
have
currently
an
average
from
eight
point:
seven,
five
Mrs
over
the
whole
year.
We
are
targeting
ten.
So
this
is
definitely
something
we
can
improve
and
we
talked
about
this
at
the
later
point.
A
But
overall
it's
it's
a
lot
of
contributions
that
we
have
made,
and
it's
a
lot
of
stuff
that
went
into
the
problem
and
if
I
especially
look
at
a
couple
of
areas
that
were
non-existent
in
January,
it's
really
great
to
see
where
we
have
and
to
find
out,
there's
another
thing
that
a
lot
of
people,
perhaps
don't
know
is
there
is
to
keep
the
area
and
that's
why
I
want
to
put
a
little
bit
of
spotlight
on
them.
Also,
today
we
had
62
releases
of
kipper.
A
This
year
they
went
from
closed
source
and
non-deployable
to
open
source
deployable.
We
even
had
not
one
iphone,
have
release
by
help
of
the
community
and
have
done
that
and
everyone
that
it
was
ever
involved
in
iPhone
release
knows
how
hot
that
stuff
is.
We
have
21,000
active
users
there.
We
have
five
thousand
active
rooms
on
a
daily
basis,
so
it's
also
really
great
to
see
in
there
and
the
great
accomplishment.
A
Another
thing
that
is
really
important
in
the
progress
that
we
are
making
to
becoming
more
robust,
becoming
more
performant,
become
simply
a
better
product
is
all
the
improvements
that
we
are
the
only
on
the
database
and
if
you
just
take
a
look
at
these
beautiful
crafts,
I
should
have
put
hearts
on
them.
Those
are
like
dropping
from
a
very
high
percentage
to
almost
none,
and
this
is
not
because
this
stuff
is
not
working
anymore.
A
This
is
because
it
was
improved,
and
this
is
really
great
to
see,
and
but
we
have
also
done
tons
of
bug,
fixes
UI
polishing,
UX
improvements
and
I
know.
We
are
some
of
the
hardest
customers
to
ourselves
by
saying,
okay,
we
should
improve
this,
and
here
there
are
freed
pixels
off
and
have
pictures
there,
but
we
are
improving
on
a
daily
basis
and
as
to
do
step
by
step
and
I.
Think
thanks
for
that
for
everyone
who
is
really
simply
taking
care
of
the
stuff,
and
on
top
of
that
we
are
all
engineers.
A
Perhaps
I
think
this
is
something
also
very
important
for
us
and
it's
it's
really
important
that
we
are
also
driving
forward
making
the
product
more
robust
by
putting
it
on
better
infrastructure
from
the
engineering
perspective
by
removing
technically
death,
but
also
advancing
our
technical
stuff
and
I
still
remember
the
beginning
of
the
year.
It
was
a
little
bit
of
let's
get
craft
to
L
going.
A
But
the
men's
team
has
done
a
great
job
to
bring
international
internationalization
out
to
speed,
to
create
limiters
that
yeah,
not
that
we
are
doing
this
in
a
very
nice
way
forward,
that
they
are
not
introducing
any
more
strings,
and
this
help
has
helped
us
a
lot.
Css
single,
codebase,
I
think
one
of
the
biggest
accomplishments.
That
is
not
something
that
you
feel
in
the
first
place
and
I'm
pretty
sure.
A
In
a
year
when
all
the
people
new
people
have
joined,
they
will
be
like
what
they
were
have
been
to
code
bases,
so
everyone
who
was
still
there-
and
there
were
two
code
bases-
need
to
tell
them
how
painful
it
was.
At
that
point,
we
have
integrated
external
services
with
sauce
crafts.
We
were
able
to
get
elasticsearch
going
on
the
common
all
those
things
where
we're
driven
by
really
a
lot
of
technically
inputs
in
order
I
just
want
to
say
thank
you,
everyone
I
think
thank
you.
A
Everyone
for
all
your
hard
work
and
all
your
contributions
and
I
know
that
sometimes
we
put
a
spotlight
on
some
someone
who
is
doing
something
great,
which
is
fantastic,
but
in
this
case
I
just
want
to
thank
everyone
as
a
whole
of
being
a
great
team
and
having
brought
something
that
at
the
beginning
of
the
year,
was
in
a
completely
different
place
and
it
completely
different
size
to
where
we
are
right
now.
And
so
thanks
very
well.
B
A
That
brings
us
already
to
the
next
level,
as
we
always
do
during
the
year
going
from
one
development
cycle
to
the
next.
This
is
definitely
not
where
we
are
stopping.
So
what
are
we
expecting
for
next
year
and
where
do
we
want
to
go
I
think
this
is.
These
are
some
of
the
most
important
topics?
Team
growth,
we're
in
the
middle
right
now
of
the
head
complaining
there's
a
lot
of
hair
complaining
stuff
going
on.
There
will
be
definitely
way
more
hair
here.
A
Cuts
to
the
head
counts,
I've
linked
their
preliminary
headcount
planning,
so
there's
nothing
finalized
yet,
but
there
will
be
growth
and
I
think
this
is
what
everyone
needs
to
be
prepared
of
that
this
will
happen.
So
I
want
to
inform
you
as
much
as
we
can
already
right
now
and
as
soon
as
we
have
some
more
numbers
that
the
whole
thing
will
also
have
them
on
the
company
level.
A
They
were
one
of
the
main
things
that
we
are
looking
currently
at
is
introducing
senior
managers
who
take
care
really
of
a
whole
stage,
and
most
probably
honor
technically
area,
because
to
reduce
the
bandwidth
of
reports
to
me
and,
on
the
other
hand,
simply
keep
an
organization
that
is
possible
to
grow.
There
is
something
around
the
crate
static
site,
editor
team,
which
was
just
created
in
the
growth
area.
A
This
is
going
to
move
in
the
next
couple
of
weeks
to
the
Deaf
section,
and
one
of
the
biggest
challenges
that
I
foresee
personally
is
is
also
information
management,
and
this
is
one
of
the
the
thoughts
that
goes
behind.
This
call
is
as
we
grow,
we
create
more
more
information,
and
what
we
need
to
do
is
get
the
information
from
wherever
it
was
created
to
exactly
the
people
who
need
to
know
about
it
and
to
some
extent,
of
course,
this
is
simply
starting
with
everyone.
So
please
remind
yourself
to
read
the
begin
review
days.
A
This
is
one
of
the
main
topics,
but
we
are
currently
collecting
information,
that
is,
that
is
really
important
to
engineers.
So
I
really
encourage
everyone
to
read
that
part
and
on
the
other
hand,
we
will
try
our
best
to
streamline
really
the
information
channels
inside
our
teams
and
inside
the
section
and
again
as
what
I
said,
what
I
was
already
thinking
everyone
for
is.
We
need
everyone's
help
to
scale
smoothly,
why
we
are
keeping
our
productivity
and
hopefully
increasing
it
even
more
and
also
our
venues.
A
I
think
this
is
the
part
of
everyone
to
keep
doing
what
we
are
doing
by
being
open
and
being
welcoming
to
new
people
and
then
I'm.
Looking
forward
to
the
context,
this
growth
really
nicely
to
give
you
a
better
picture.
If
you
look
at
the
first
slide,
where
I
was
telling
a
little
bit
about
the
different
teams
and
the
subsections,
this
is
currently
the
plan
of
how
much
we
will
split
in
the
next
year
and
where
we
are
going.
This
is
currently
the
different
area
names.
A
Where
do
we
want
to
go
on
the
Deaf
section,
but
overall
in
engineering
we
want
to
improve
ourselves.
So
this
means
really
that
we
want
to
improve
on
honors
level
of
each
individual
on
the
team
level
honor
whatever
there
is
a
senior
manager,
but
on
the
whole
section
level
that
we
improve
on
a
constant
basis
so
that
we
don't
need
to
work
more
hours,
but
that
we
simply
work
110g.
A
So
I
think
one
of
the
most
important
things
is
that
if
you
have
the
feeling
that
something
is
needs
to
be
changed
or
something
needs
to
be
be
done
differently
or
if
you
have
input.
Please
speak
up.
It's
really
important
for
me
and
I
know
also
for
all
the
engine
managers
in
the
Test
section
that
we
want
to
be
as
actionable
as
possible,
especially
on,
for
example,
the
feedback
from
the
engagement
survey,
but
also
on
everything
else.
A
That's
going
on
and
I'm
not
pinpointing
that
on
one
thing
that
is
happening
at
the
end
of
the
year,
but
if
it's
needed
that
everyone
really
chips
in
and
really
helps
that
we
are
improving
everything
that
we
are
doing
and
the
classic
topic
is
what
is
the
hardest
part
about
or
a
daily
job
ask
that
ourselves
and
think
about
it?
Is
there
something
that
we
can
automate?
Is
there
something
that
we
can
optimize?
Is
there
something
that
you
do
every
day
and
we
could
replace
this?
Is
there
something
that
our
reviews
could
benefit
from
it's?
A
It's,
not
that
someone
needs
to
decide
how
this
is
done.
This
is
something
that
everyone
can
bring
up
in
the
sense
of
let's
do
this
together
and
I'm,
pretty
sure
we
can
improve
on
that
another
part.
There
is
knowledge,
sharing,
I,
think
it's
really
important
to
do
knowledge
share
on
a
global
level
and
on
an
engineering
specific
level.
So
this
means
the
fountain
caused
a
tear,
there's
also
a
bacon
collar.
They
want
to
embrace
this
a
little
bit
more
simply
in
the
sense
of
if
there
is,
for
example,
a
performance
thing
happening
on
production.
A
There
will
be
three
engineers
who
go
out
and
finish
that
stuff,
but
the
most
important
part
to
some
extent
is
what
happened
there.
What
happened
exactly
the
incident?
How
can
we
improve
that?
We
don't
do
this
again.
How
can
we
write
fast
for
a
few
queries?
How
can
we
look
at
monitoring
tools?
So
simply
skill,
sharing
knowledge,
sharing
I
think
is
a
very
vital
part
that
everyone
has
the
tools
that
they
need
on
a
daily
basis
to
do
the
right
things
in
with
their
their
work.
A
A
A
What
was
something
that
you
would
do
immediately
if
you
would
have
known
it
earlier,
and
this
is
my
tool
in
comes
in
and
I-
think
it's
really
important-
that
we
everything
that
we
can
do
to
improve
our
workflows
and
especially
I,
can
get
rid
of
doing
it
simply
by
doing
limiters
and
parts
is
a
huge
step,
but
there's
also
really
something
magical
that
we
have
in
our
hands.
What
a
lot
of
other
people
don't
have,
which
is
Keita?
A
It's
it's
the
easiest
thing
that
everything
that
we
do
for
us
and
we
can
be
very
selfish,
simply
go
to
the
product
team
and
say
we
would
love
to
have
a
team
overview,
because
we
want
to
do
better
team
management.
We
want
to
have
something
that
is
doing
better
code
reports.
This
is
internal
custom,
and
everything
that
we
saw
for
ourselves
is
most
probably
something
that
helps
also
others
and
other
other
engineering
teams
or
other
engineers
are
simply
waiting
that
this
problem
is
getting
soft.
A
So
please
think
about
that
stuff
as
much
as
we
can
the
biggest
topic.
We're
aware
that
we
are
currently
looking
at,
and
we
already
started
in
the
last
month
that
we
want
to
get
all
the
teams
on
its
ownership.
We
believe
that
raising
the
ownership
can
definitely
help
us
on
our
new
strategy
with
availability
or
velocity.
Simply
in
the
sense,
what
we
want
to
use
more
is
more
robustness,
better
performance,
better,
better
scaling
of
our
software,
especially
in
the
dev
section.
Does
their
section
is
a
very
high,
frequently
used
area.
A
So
this
means
that
there's
simply
a
lot
of
stuff
going
on
and
the
more
we
know
and
the
better.
We
have
an
understanding
how
our
code
is
actually
running
in
production
and
s,
because
these
dev
ops
that
we
are
putting
in
our
marketing
materials
so
that
we
rather
do
this
all
on
our
own.
It's
really
the
most
important
thing
that
we
bring
all
engineers
close
to
that,
and
we
believe
that
it's
really
important
that
everyone
takes
care
of
their
of
their
area,
that
they
are
in
it's
your
area.
A
It's
really
the
area
that
you
can
take
ownership,
see
it
like
a
little
small
little
garden.
This
is
your
backyard
that
you
and
your
team
are
basically
taking
care
of
that.
It
is
fast
that
it's
real,
fast,
it's
reliable,
and
that
is
simply
a
really
great
thing
to
use
and
most
of
the
times,
we
can
also
solve
problems
on
a
global
level
that
everything
that
we
help
to
improve
the
performance
outside
simply
reduces
the
pressure
on
their
whole
overall
infrastructure,
or
it
helps
other
areas,
and
things
like
that.
A
So
the
first
step
that
we
are
I've
already
started
and
that
we
have
taken
is
really
bringing
and
all
the
tools
that
we
have
in
place
and
we
have
tons
of
tools,
bring
them
to
all
the
engineers
and
bring
into
all
to.
You
is
really
like
the
performance
by
kaneki
bananas,
century
Prometheus,
site
speed
on
the
front
and
side,
which
is
really
that
everyone
has
understanding.
You
want
to
provide
everyone,
the
right
training
around
is
that
really
everyone
can
go
in
and
can
say:
hey
yeah.
A
So
really
that
you
are
in
a
situation
where
you
can
fight
fire.
I
always
said
if
the
homework
was
an
actual
fire
situation.
So
if
you're
doing
your
homework
and
next
to
you,
there's
a
fire
that
just
started
and
please
help
and
put
out
that
fire
and
I
think
it's
also
very
important
that
we
work
very
closely
between
front
end
and
back
end,
because
then
we
can
improve
the
performance
and
especially
the
perceived
performance
and
even
much
better.
The
same
goes
for
UX
quality
infrastructure
security.
A
Good
examples,
quality
has
tons
of
reference
architectures
by
now
that
can
help
really
on
testing
performance
already
beforehand,
yeah,
and
that
should
lead
us
really
to
constant
improvement
when
we're
not
just
taking
the
issues
that
we
assigned
but
really
have
a
proactive.
You
on
our
area
have
a
proactive
approach
to
our
area
and
and
really
get
to
a
scale
that
we
are
getting
here.
So
we
will
provide.
We
will
take
a
look.
What
do
we
need?
A
Thank
you
for
listening,
everyone
and
I'm
jumping
over
to
the
chamber
of
questions,
and
there
are
or
into
a
question.
So
this
is
awesome.
Do
we
have
documentation
trainings
on
how
to
use
tools
like
Ravana
would
be
great?
Yes,
what
we
have
done
is
we
have
started,
especially
in
the
back
inside,
because
there
we
have
more
tools
already
in
place
there.
A
We
have
already
more
access
to
it,
so
Michelle
and
our
been
leading
the
charge
there
to
create
a
lot
of
videos
and
we
can
reuse
a
lot
of
those
videos,
but
we
will
also
trade
simply
our
own
front-end
dedicated
video,
so
century
s1,
as
soon
as
that
is
completely
placed
what
Dennis
mentioned,
and
we
already
have
like
a
small
site,
speed
demonstration
video.
We
will
create
some
more
stuff
around
the
performance
part
so
that
we
really
create
the
same
things
and
for
the
second
there
is
linked
in
the
slides.
A
We
also
have
already
like
two
different
playlists
and
we
have
a
lot
of
handbook
pages
and
as
soon
as
we
have
that
everything
in
place
for
from-
and
we
will
do
exactly
the
same
for
bacon
as
we
had
also
a
lot
of
learnings.
Also
in
that
area,
I
hope
that
was
I
was
able
to
answer
the
question.
Shawn.
Could
you
talk
through
the
current
shape
of
hiring
plans
for
next
year?
Obviously
they
are
still
subject
to
approval.
Yes.
So
far,
it
looks
like
that.
A
We
overall,
there
was
already
from
product
side
a
clear
focus
that
on
strengthening,
for
example,
plan
which
is
one
of
the
highest
priorities
to
really
strengthen
plan
and
import.
We
are
also
looking
currently
at
a
high
priority
areas
in
the
sense
of
importing
and
things
like
that,
which
are
simply
super
important
for
all
the
huge
customers
that
are
coming
in
created
anyhow
with
much
requests
and
edit.
Your
stuff
is
also
in
very
high
demand
on
product
and
the
main
thing
that
we
have
done
so
far
from
our
sights.
A
Things
looked,
cool
I
mean
if
there
are
no
more
questions,
then
thank
you
for
your
attention
and
if
there
are
some
more
questions
coming
up
in
the
meantime
feel
free
to
ping
me
put
something
in
select.
You
know
how
to
reach
everyone
if
there
is
also
a
second
edition,
because
we
are
taking
care
of
all
the
people
in
the
impact
time
zone,
so
there's
another
one
on
Monday,
it's
also
very
nicely
for
the
u.s.
time
zone.
If
you
have
more
questions,
please
feel
free
to
drop
in
and
ask
some
more
questions.