►
From YouTube: Dev Backend 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
welcome
to
today's
group
conversation,
engineering
def,
which
is
brand
new
just
with
a
brand
new
staff
department,
which
was
just
formed
two
weeks
ago
and
I'm
very
happy
to
do
this
today.
For
the
first
time
it's
a
great
transition,
I
have
to
say
meant
it's
it's
a
great
focus
that
we
have
now
on
the
product
side,
and
it's
really
energizing
and
I'm
hoping
for
a
lot
of
questions
today
or
that
the
presentation
was
explained
explanatory
enough.
A
So
yeah,
please
take
a
look
and
I
only
dive
right
into
the
questions
that
are
already
here
so
Sean,
and
this
was
not
free
defined,
discussed
that
I'm
getting
a
question
for
him.
Is
that
what's
the
having
plan
for
it?
So,
yes,
we
have
a
couple
of
candidates
quite
far
along,
and
our
current
target
is
to
hire
one
more
full
stack
engineer
that
we
see
two
people
that
especially
Eric
has
accountable
not
a
counterpart
but
like
a
buddy,
so
that
we
have
also
easier
flexibility
on
time
off,
etc.
A
A
So
that
is
really
great
to
see,
and
now
it's
really
that
we
can
push
along
features,
and
that
also
should
help
us
on
having
a
factor
develop
integration
and
with
that
we
hope
that
we
can
also
raise
activity
and
employ
users.
There,
yes,
Sean.
Another
question
graphical
means
only
one
API,
but
isn't
there
an
element
of
there
are
15
competing
standards.
Let
me
click.
Oh
it's
there.
Yes,.
A
Yes,
that's
a
problem
I've
heard
from
some
people.
That's
the
nice
thing
that
we
have
just
hired
a
couple
of
people
who
have
already
graphical
production
standard
or
some
bigger
implementations.
There
is
the
definition
and
the
philosophy
about
having
no
versioning
our
SQL
so
that
it's
like
in
flux,
living
document,
schema
and
I
think
there
are
two
or
three
competing
standards,
and
that
is
I.
Think
we
even
have
an
issue
on
that.
A
That
is
that
one
of
the
open
questions
that
we
definitely
have
to
answer
and
figure
out
along
the
way
how
to
do
fabrication
of
things.
How
can
we
do
this
in
a
way
that
the
graph
field
users,
either
us
or
other
other
outside
customers,
are
happier
fit
influent,
etcetera,
but
it's
definitely
easier
to
version
and
deprecated
stuff?
Oh.
B
Sorry,
what
I
meant
was
like
you
know,
we're
talking
about
graphic.
You
are
replacing
the
internal
API
as
we
have
in
rails
controllers
and
also
the
public
REST
API.
But
at
the
moment
we
just
have
three
api's.
We
have
the
internal
rails,
controller's
API,
okay,
the
public
rest,
api
and
the
graphic
UL
like
we
haven't.
A
I
think
that's
a
nice.
There
was
a
great
suggestion.
I'm
really
sorry
I
forgot,
from
whom
it
was
in
one
of
the
meetings
for
craft
year,
and
there
is
an
issue
it
should
be
also
linked
in
the
epoch,
which
is
one
of
the
tasks
that
we
want
to
look
in
is
like
reverse
proxy,
which
means
that
as
soon
as
we
have
gradual
in
place
that
we
recreate
some
of
the
rest,
API
endpoint
from
the
public
API
that
still
want
to
support
over
a
longer
period
of
time,
so
I
think
internal
and
API
inference.
A
We
can
easily
deprecated
because
we
simply
deprecated
them
and
replace
them
of
graphical
and
what
some
have
done
and
we've
quite
good
success,
because
there
are
also
some
proxy
servers
and
relative
for
graphical
is
like
you
create
an
REST,
API
endpoint,
which
is
simply
doing
a
specific,
very
against
craft
here
and
through
that
you
have
have
the
API
endpoint
to
the
outside
world,
but
you
don't
have
any
code
for
it,
because
it's
just
proxying
to
the
graph
here.
So
that
is
one
of
the
strategies.
That
is
definitely
I.
Think
quite
a
nice
thing
to
do.
D
A
Not
really
so
at
a
reticule
endpoint
that
that
would
be
new
to
me
is
really
based
on
on
race.
Has
nothing
to
do
with
note.
As
far
as
I
know,
we
are
using
even
the
same
gem
that
it
helped
Shopify
and
a
couple
of
others
are
using,
so
it's
100%
race
based.
We
are
starting
nothing
new.
We
are
really
building
on
on
the
controller's
and
the
code
that
we
already
have
and
simply
expose
it
through
progress
here.
A
A
My
pants,
the
fy2010,
has
only
one
person
keep
the
totally
star
disconnected
yes,
that
could
be
because
the
the
target
for
having
it
if
the
person
is
already
coming
from
last
year,
so
it
could
be
that
there
wasn't
anything
transferred
over
I
will
have
a
look
at
it.
Thanks
for
that,
and
thanks
a
lot
to
Sean
for
keeping
up
the
agenda
so
nicely
any
other
questions
well
inform.
C
So
Tim
we're
gonna
have
we
have
a
manage
team?
We
also
have
a
fulfillment
team,
which
focuses
more
on
like
the
billing
aspects
and
the
license
of
the
license
ordering
they
used
it
that
used
to
be
done
by
the
manage
team,
but
the
fulfillment
team,
it's
probably
under
enablement.
Now.
How
do
you
see
that
is
that?
Well,
that
split
costs
problems
because
they
report
up
to
a
different
director
or
how
do
you
see
that
I.
E
C
A
C
C
Also,
the
security
is
trickier
because
there's
less
it's
less
defined,
what
you
do
so
I,
there's
there's
people
doing,
for
example,
giving
only
a
materialized
view
of
the
database
so
that
you
restrict
what
people
can
query
in
the
beginning.
What
do
you
think
about
these
development
speed
and
security
challenges
of
vacuo
yeah.
A
So
I
think
with
the
throughput
I
think
we
can
definitely
raise
a
lot
of
topics
with
graph
QL
on
our
side
and
athlete
or
in
one
of
the
nature,
slides
that
make
it
look
which
money
was
I,
think
number
16,
there's
a
there
are
some
links
to
other
companies
and
their
experiences
with
Greg
field.
The
main
thing
was
really
that
resolving
a
lot
of
dependency
stuff.
So
right
now,
if
we
have
a
smaller
topic
and
it's
suddenly
something
that
the
fronton
engineer
needs
to
X
is
just
part
of
the
query.
A
I
pick
an
engineer
it
needs
also
to
come
in.
We
create
most
of
the
time.
A
new
end
point.
Another
end
point
is
create.
That
means
also
need
to
be
maintained,
etc,
and
in
the
future.
We
don't
need
that
anymore,
absolutely
in
effect
of
that,
the
front
and
person
can
write
their
clue,
which
is
specific
to
their
use
case.
So
this
is
reduces
the
dependency
between
those
two
teams,
which
gives
the
front
and
a
little
bit
more
flexibility
and
the
back
end.
A
On
the
other
hand,
more
focus
on
specific
topics
according
to
the
end
point
and
reduces
also
maintainability.
So,
especially
with
a
lot
of
the
use
cases,
we
have
seen
that
group
wood
is
raised
through
that,
especially
on
the
front
end.
The
other
part
is-
and
that
is
also
one
of
the
biggest
topics
on
concerns
that
we
are
trying
to
resolve
pruning.
This
q1
OPR
is
really
to
resolve
that
the
big
questions
around
authorization
authentication,
how
can
be
prevented.
Someone
is
simply
doing
a
complete
database
dump
in
reality
from
the
floor.
Sql
query.
A
So
this
is
done
through
performance
by
performance
points
on
the
query,
so
every
query
get
some
performance
cost
and
you
can
only
create
well
up
to
a
certain
amount
of
points
and
stuff
like
that.
So
those
are
really
the
main
questions.
I
would
say
it's
80%
of
the
questions
that
we
are
trying
to
resolve
now
and
this
in
the
next
release
cycle
are
mainly
beckoned.
A
We
are
working
closely
with
the
security
team
early
on
to
to
really
minimize
any
risks
by
exposing
more
as
we
are
simply,
and
that
is
something
we
need
to
keep
also
very
close
eye
on
it,
and
that's
why
we
want
to
have
a
lot
of
blueprints.
A
lot
of
helping
things
is
because
we
are
the
transferring
the
analyzes
and
the
strategy
of
the
query
from
the
back
end
to
the
front
end.
So
it
can
happen
of
course,
data.
A
Suddenly,
a
front-end
engineers
write
in
a
complete
super,
complex
query,
which
is
like
taking
two
minutes
every
time
you
call
it
and
that
shouldn't
happen
and
that
something
need
to
figure
out
along
the
way.
How
can
we
do
this
during
development
that
we
feed
out
on
a
bigger
scale?
This
clearly
will
not
work
so
what
we
currently
have
in
place
for
taking
engineers,
which
is
like
the
database
review,
that
we
have
the
same
thing
in
place
for
front-end
engineers
in
future
steps
that
they
can
have
like
a
review
of
new
graph,
GL
queries,
etc.
C
And
address
a
lot
I
think
that
company's
a
bit
hesitant
to
post
about
graph
key
or
failure
stories,
because,
like
right
now
it's
it's
a
cool
thing
to
do.
It's
on
the
peak
of
inflated
expectations,
I!
Think
it's
a
good
direction,
long
term,
but
I'm,
seeing
when
you
talk
privately
with
people,
I'm
hearing
some
some
some
big
challenges
where
the
tooling
isn't
ready,
where
the
security
that
kind
of
the
sandboxing
of
the
queries
is
much
harder
and
people
are
developing
custom
solutions
to
that.
So
we
should.
C
A
Enemy,
we
are
also
having
an
eye
on
new
hires,
because
we
just
hired
in
the
front
and
I
think
now
three
for
people
who
have
actual
production
experience
on
all
the
bigger
scales
with
graphic
yell
that
bring
us
also
tons
of
knowledge
into
the
team.
But
your
total
director,
most
people
write
about
the
nice
things
and
yeah.
C
A
Now
is
everything
that
we
are
using
is
open
source.
We
are
using
the
same
gem
that
also
github
is
using
that
Shopify
and
a
couple
of
other
huge
graph.
Ql
implementations
is
already
using
production,
so
everything
new
that
it
lakita
is
already
using
is
built
on
top
of
that.
That
shows
us
that
there's
a
lot
of
activity
in
that
stuff
and
we
don't
need
to
rewrite
anything.
A
The
same
is
that
we
are
using
view
Apollo,
which
is
working
on
some
of
the
client
exactly
as
Lucas
wrote,
the
open
source
library
in
the
front-end
that
we
are
using
is
Apollo,
so
I
think,
right
now,
from
the
tooling
side,
we
have
a
good
combination
and
the
proxy
server
could
be
something.
There
are
two
free
open-source
tools
out
there
at
the
moment,
but
definitely
something
that
we
need
to
take
a
look
cool
thanks.
F
It's
a
mistake
here:
I
had
a
question
on
our
API
direction
in
general,
but
I
can
see
us
requesting
more
REST
API
to
set
up
test
data
for
bacteria
and
such
on
slide.
15
you're,
saying
that
I'm,
long-term
REST
API
is,
can
build
on
top
of
graph
feel.
So
are
you
saying
any
new
REST
API
requests
will
be
built
on
top
of
graph
Creole
or
what's
your
direction
here,
yeah.
A
The
idea
is
that
we
simply
replace
all
the
rest
api
and
in
front
of
you
currently
have
in
place
that
we
still
want
to
support
for
a
very
long
time
that
we
simply
replace
them
by
proxy
requests
to
Bradfield.
So
if
we
see
that
the
customer
needs
still
rest
and
they
want
to
use
rest,
there
are
a
couple
of
tools
that
are
pretty
easy
to
configure.
A
The
soup
doesn't
manatee
it
a
rest
call
list,
not
nothing
else
in
a
graphical
called
with
a
specific
query
with
a
specific
result
set,
and
it
is
something
that
we
could
so
that
we
are
able
to
actually
the
race
codes
to
minimize,
to
maintenance
and
also
security
topics
and
security
access
area.
So
I
think
that
could
be
quite
a
viable
strategy
to
reduce
and
as
soon
as
everything
is
ready
for
FTL
that
will
reduce.
A
So
it's
it's
a
different
topic
and
it's
not
directly
connected
to
the
others,
and
it's
currently
not
under
create,
in
my
my
opinion,
but
I
will
definitely
have
a
look
at
it
to
see
if
we
need
to
clarify
some
parts
and
in
the
handbook
there,
as
it
I
think,
the
connection
to
to
create
is
the
air
to
some
extent.
But
it's
it's
a
it's.
It's
separate
thing.
My
well.
A
Kaifi,
how
is
the
higher
pipeline
looking
from
management
issues?
One
of
the
teams
that
could
use
more
help
with
resolving
security
vulnerabilities
from
new
slacks?
How
many
of
the
six
I
see
head
counts
are
currently
on
board
and
British
really
can
tell
much
more
in
detail
and
much
better
than
I.
Can
texture.
E
Extent,
and
at
the
moment
we
have
five
back-end
engineers
in
manage,
and
the
pipeline
is
looking
quite
strong.
Actually
I
was
talking
to
tell
me
about
this
earlier,
it's
as
strong
as
its
look
for
a
while.
We
have
one
Canada
reference
checks
and
I
think
we
have
seven
or
eight
in
the
pipeline.
So
hopefully
we
can
fulfil
the
target
of
six
in
the
coming
weeks.
Then
we'll
be
in
a
good
position
to
complete
for
the
rest
of
the
year
as
well,
and
then
I,
don't
know,
I
just
saw
Dennis's
note.
H
E
It's
really
positive
I
think
we
had
Gator
and
pebble
join
us
earlier
in
this
month
and
I
think
with
other
changes
that
happen
in
as
well
with
the
scape
have
managed
becoming
more
focused
with
the
fulfillment
team
and,
for
example,
and
yeah.
We're
certainly
gonna
be
able
to
put
more
capacity
in
solving
some
of
the
security
issues
we
have
in
the
back.