►
From YouTube: Layer5 Community Meeting (Nov 6th, 2020)
Description
Welcome @sudo_navendu, Edwin Villa, and @toheebolushesi! A @graphql presentation by @_devkalra.
A
B
A
A
B
A
A
If
you
go
to
a
conference,
you
get
some
swag
occasionally
and
anyway,
there's
a
I've
gotten
this
in
the
mail
this
this
is
the
conference
all
day,
devops,
I'm
not
not
that
special
or
anything,
but
I
feel
weird
because
I'm
drinking
out
of
that
coffee,
mug
and
then
they
sent
a
they
sent
the
jacket
as
well
and
I'm
wearing
the
jacket
I
feel
like.
I
may
as
well
have
gotten
an
addo
tattoo
right
here
right
there,
because
yeah,
okay,
anyway
good
meeting
minutes
it's
well
the
week
after
halloween.
A
There
are
the
meeting
minutes
in
the
chat
and
and
we're
off.
Let
me
let
me
share
the
meeting
minutes.
Let's
get
rolling
on
today's
community
call
everyone!
That's
on
the
call,
as
of
now
has
a
link
to
the
meeting
minute
so
pop
your
name
into
the
attendees
list.
If
you
would
it's
always
nice
to
reflect
on
who's
here,
who
we
should
send,
you
know
signed,
signed
copies
of
books
to
at
the
end
of
the
year.
We
just
go
back
to
the
list.
A
We
then
raffle
off
what
like
a
thousand
dollars
to.
You
know
eight
different
names
that
we
pull
out
of
the
bucket.
No,
no,
we
don't
do
any.
No!
No,
we
do
do
some
of
that.
We
do
not
raffle
off
thousand
dollar
the
you
know
eight
thousand
dollars
based
on
who
shows,
but
we
actually
do
send
out
some
some
books
or
some
other
things.
Occasionally
it
was
cush
who
had
mentioned
recently
that,
just
as
like,
I
think,
a
point
of
reflection
for
him.
A
A
They've
got
a
button
maker
where
they'll
cut
these
out
they'll
stamp
the
buttons,
and
now
that
I'm
talking
about
it,
I
should
have
a
button
on
hand,
but
I've
got
a
big
fat
bag
of
buttons
that
look
just
like
that
with
the
logo,
so
those
are
probably
cheap
enough
to
put
into
the
mail
too.
So
so
I
guess
my
prattling
on
has
led
me
to
committing
to
sending
out
buttons
to
people,
and
this
friday
is
going
well.
A
Along
with
that,
we've
sent
out
some
books
and
other
things,
and
I
know
I
hope
that
the
that
short
report
has
been
helpful
to
most
of
you,
who've
gotten
it
before
it's
a
short
report
on
service
meshes.
If
you
don't
have
it
just
just
mention
it
and
I'm
and
before
I
can
do
it
myself,
someone
else
will
post
a
link
to
where
you
can
download
this
one
for
free.
It
gets
distributed
around
our
community.
A
A
lot
on
that
subject
actually
faith,
I'm
not
sure
if
she's
on
the
call
or
not,
but
she
just
got
done,
helping
with
the
second
edition
of
that
book.
It's
it's
coming
out
any
time
now
and
and
we'll
make
sure
that
anyone
who
wants
one
of
these
gets
one
in
their
hand
as
well
at
least
digitally,
if
not
physically.
A
So
speaking
of
I
don't
mean
to
talk
about
these
things,
a
lot
it
just
sort
of-
I
guess
they're
top
of
mind.
But
I'll
say
this
on
the
record
and
say
that
I
intend
to
follow
up
with
me
who,
on
on
this,
because
some
of
the
work
that
you're
doing
is
lines
right
up
with
some
things
that
are
going
to
be
inside
of
the
patterns
in
that
book
and
there
are
there's
opportunities
to
engage
there.
A
So
I
just
need
to
go
highlight
what
that
is
and
how
to
how
we
can
shine
some
more
light
on
your
work.
Put
your
slap,
your
name
somewhere
in
there
and
so
okay.
Well,
I
like
how
we're
doing
the
community
meeting
this
time.
It's
just
a
bunch
of
random
notes.
For
me,
it's
also
good
to
welcome
a
bunch
of
newcomers
into
the
slack
channel
for
better
or
worse.
I
think
we
sort
of
consider
the
the
center
of
the
community
ends
up
being
in
slack
in
the
layer,
five
community.
A
We
don't
make
a
lot
of
use
of
mailing
lists,
so
we
don't
send.
We
don't
have
kind
of
group
mailers
where
we
have
discussions
on.
What's
going
on,
not
that
that's
a
bad
thing,
we
just
hadn't
gotten
that
practice
going
so
we
use
slack
pretty
heavily
last
week.
We
heard
from
pratik
who's
been
within
the
community
for
a
while
he's
been
helping
in
terms
of
community
management.
He
had
had
a
quick
note.
A
A
A
I
was
about
to
fall
asleep
and
it
was
just
an
opportunity
to
remind
him
and
and
everyone
else
that
when
you
can
try
to
chat
publicly
in
slack,
it
helps
help,
helps
everybody
less
repeating
more
engagement,
more
opportunity
for
people
to
chime
in
and
and
help
and
learn
and
so
yeah.
So
if
you
can
chat
publicly
in
slack,
that's
a
good
thing.
Another
thing
that
we
would
do
well
to
reflect
on
and
and
before
anyone
else
highlights
it
I'm
going
to
have
to,
and
that
is
that.
A
A
Lucky
and
also
by
design
we've
had
what
are
we
on
now?
Wow
cool
we're
getting
up
there,
we're
almost
to
2000
issues
which
which
is
fantastic,
but
it's
also
the
case
that
they
get
stale
after
a
while.
So
some
of
you
are
familiar
with
the
fact
that
there
is
a
small
bot
that
runs
around
git
that
we've
configured
to
run
around
github,
it's
the
stale
bot.
It
will
mark
any
issues
and
I
think
prs
as
well,
but
any
issues
that
haven't
had
activity
on
them.
A
A
But
I
wanted
to
call
out
a
second
public
service
announcement
or
like
thing
to
consider,
is
that
it's
healthy
for
us
to
go
back
and
groom,
groom,
grim,
groom.
You
hear
a
lot,
I
think
you
hear
the
term
the
word
groom
in
context
of
a
backlog
generally
backlogs
are
more
about
features
than
they
are
bugs,
but
they
include
both.
You
know
you're,
constantly,
grooming,
the
backlog,
that's
like
the
product
managers,
the
product
owner's
job,
and
so
it's
our
job
as
a
community
to
also
groom
our
issues
either.
A
So
in
a
long-winded
way,
the
the
what
I'm
asking
people
to
do
is
if
I
know
it
can
be
entirely
uncomfortable
to
go
over
and
like
suggest
that
someone
get
off
of
an
issue,
it's
can
be
really
sensitive.
It
can
be
a
lot
like
asking
your
next
door
neighbor
to
turn
their
music
down
like
I
don't
know
if
you've
ever
done
that,
but
I'll
tell
you,
there's
no
right
way
of
doing
that.
A
You
will
only
end
up
hurting
someone's
feelings
if
you've
ever
been
successful
in
doing
it
and
it
didn't
actually
hurt
their
feelings.
Then
please
tell
me
the
secret,
because,
like
so
many
of
you
are,
and
if
you're
a
member
of
the
layer,
5
io
org,
that
means
that
your
github
user
has
per
the
permission
the
rights
to
triage
issues
which
includes
like
assigning
yourself
assigning
others
updating
things,
I'm
making
a
call
for
your
assistance
in
just
even
just
just
comments
just
just
help
to
just
your
assistance
in
grooming
through
the
issues.
A
Speaking
of
we're
going
to
talk
about
a
new
project
today,
but
as
you
go
through
the
different
projects,
some
of
you
are
probably
already
hip
to
this,
whereas
maybe
it
took
me
a
while
more
is
that
when
you're
you
can,
you
know
you
can
search
through
github
for
a
lot
of
things.
You
can
also
do
something
like
an
organization-wide
search,
so
so
this
particular
search
is
the
ur.
A
So
it's
good
and
then
with
that
we've
got
something
much
more
interesting.
Dev
cholera
is,
inter
is
interning
through
community
bridge
focused
on
well
two
projects,
most
notably
a
project
called
mesh,
sync,
which
some
of
you
are
playing
around
with
or
I'm
sorry
interacting
with
the
first
version
of
mesh
sync,
which
is
currently
inside
of
the
stable
release
of
meshri
mesh
sync
is
just
a
component
in
measuring
that
will
actively
go
over
and
interrogate
kubernetes
for
anything
that
might
for
a
bunch
of
information
about
kubernetes.
A
One
of
those
is
graphql,
and
so
I
gave
dev
a
lot
more
lead
time
than
most
on
providing
then
much
of
the
time
that
I
do
when
I
ask
someone
to
come
and
present,
and
so
it
was
22
minutes
ago
that
I
asked
dev
to
present
a
graphql
today.
So
I
thought
it
would
be
nice
for
all
of
us
to
get
more
familiar
with
that
piece
of
tech
if
you're
not.
B
A
B
Okay,
I
can
do
the
system
start
with
this.
I
don't
know
okay,
so
this
is
just
an
introduction
to
crafting
like
why
we
should
use
this
thing.
What
exactly
is
this?
This
was
addressed,
which
currently
we
are
using
in
ministry
somewhere
and
you
may
have.
If
someone
has
worked
on
web
development,
then
usually
we
start
with
rest
api
that
is
guest
get
post.
Something
like
that.
So,
let's
just
start
with
this,
so
first
an
introduction.
B
So
first
thing:
actually
I
was
studying
about
escape
rates
in
the
past
and
the
first
thing
that
the
one
thing
that
was
really
interesting
to
me,
that's
that
that
get
postponed
is
there
is
no
architecture.
It's
just
that
is
a
restful
architecture
is
just
a
specification.
It
just
defines
what
the
request
and
what
the
response
will
look
will
look
like
what
should
they
appear
in
that
architecture.
Something
like
that.
So
graphql
is
something
similar.
It's
a
specification
and
or
some
library
which
you
can
just
use
to
develop
things.
B
It's
a
specification
which
specifies
the
request
and
response,
like
requests
will
be
like
this,
and
the
response
will
be
something
like
this,
so
what
it
provides
us,
it
basically
provides
us
with
the
declarative
way
to
fetch
data.
Now
I
will
come
to
that
like
what
is
the
regulative
way
here.
Another
thing
is:
it
makes
our
api
goals
a
lot
more
efficient
and
flexible.
I
will
cover
that
in
the
next
slide.
So
this
is
the
declarative
way.
Okay.
So
this
is
my
browser
and
I
am
requesting
the
data
something
like
this.
B
Like
I
want
user,
whose
idea
is
this?
I
want
his
name,
the
post,
that
he
has
written
the
follower's
name
and
things
like
that,
and
you
can
see
that
I
am
basically
it's
it's
the
declarative
way.
I
have
no
close
point,
I'm
just
giving
it
some
fields
that
give
me
this
thing
and
the
in
the
back
end
of
the
server
will
just
return
that
much
like
name
post
followers
name,
something
like
that.
So
this
is
the
declarative
way
and
yeah.
B
Let's
go
graphical
and
I
will
tell
you
like:
why
is
it
more
efficient
and
it's
certainly
faster
than
there
is
so
yeah
rascal
is
more
efficient
because
we
can
get
all
the
data
that
we
need,
like
not
only
of
a
single
user.
We
can
get
multiple
users
to.
We
can
get
all
the
data
that
we
need
in
a
single
requested
goal
requestion
and
we
don't
need
to
do
requests
again
and
again
and
again
to
get
different
data.
B
So
that's
why
it's
more
efficient
and
usually
we
use
a
single
endpoint
to
fetch
better
graphical
letters.
It's
it's
basically
supports
rapid
product
integration.
Why
and
what
how
it
supports?
I
will
come
back
to
this
another
thing:
is
it
solves
the
issues
of
overfetching
and
under
fetching?
So
what
is
overlapping
and
fetching
so
basically
say
they're
in
this?
Let's
go
apis.
There
are
this.
B
There
is
a
get
endpoint
and
that
endpoint
can
give
a
name
to
you
if
you
give
it
the
user
id
so
okay,
so
you
hold
that
get
api
and
you
get
the
name,
but
now
you
won't
post.
So
there
is
another
another
endpoint
for
that
for
followers.
There
is
another
endpoint,
so
that
is
like
under
fetching
for
an
every
single
endpoint.
We
are
getting
data
less
than
what
we
want.
So
that's
something
that
solves
and
overfetching
is
something
similar
to
this
like.
B
We
only
need
the
name,
and
but
we
have
to
get
all
of
all
the
things
supposed
to
write
the
followers
name
to
get
to
that
name.
So
this
is
this
is
something
that
tasks
hold
seriously:
okay,
okay.
I
I
totally
like
I
will
come
back
to
this
integration
so
first
before
going
to
that
first,
I
want
to
define
something
so
graphical
has
a
strongly
typed
system.
B
Okay,
what
we
have
to
do
we
have
basically
it
provides
us
with
a
language
using
which
we
can
define
our
apis,
okay,
and
so
that
example,
that
language
is
something
like
that
jason.
Do
you
just
define
the
types
you
just
find
like
face
that
will
go
in
there
and
something
like
that
if
someone
has
used
something,
so
it's
something
like
that:
okay,
so
to
use
graphql
first,
the
front-end
team
and
the
back-end
team
has
to
work
on.
The
schema
schema
is
nothing
it
will
defines
the
api.
B
So
that
is
something
we
have
to
work
on
once
they
have
defined
the
schema,
they
can
simply
start
working
on
their
own
the
front
end
and
on
the
back
end
like
they
can
work
asynchronously,
they
only
have
to
define
the
schema,
and
this
is
why
it
supports.
This
is
one
of
the
reason
it
supports
rapid
integration
because
we
have
fixed
the
schema.
Now
we
can
develop
it.
B
Right
and
another
thing
is
the
friend
endings
can
just
use
a
diamond
data
to
basically
fix
the
field.
So
there
is
this
concept
of
the
solver
and
graph
here,
okay,
so
using
schema.
This
is
the
schema.
This
is
something
like
schema
user
name,
followers
name
h,
she's,
using
the
schema.
We
can
get
all
this
data
right,
but
how
will
that
work?
B
A
function
basically
that
I
will
define,
which
will
give
me,
which
will
return
the
user
based
on
sub
id,
and
that's
that
that's
that
that
is
what
is
always
okay,
so
yeah.
I
didn't
know
this:
how
to
use.
We
have
to
define
a
schema.
Both
teams
can
work
better
and
there
are
things
like
we
don't
need
to
take
care
of
the
underlying
network
network
layer
like
how
things
will
work,
how
we
will
be
working
with
streaming
data
and
all
those
things
there
are
libraries
that
can
help
us,
for
example,
for
front-end.
B
We
have
relay
and
apollo,
and
I
think,
as
we
have
decided
to
go
over
this
relay
first,
so
we
will
work
with
relative
in
the
front
end
and
go
back
into
their
libraries
that
will
handle
the
underlying
network
related
things
for
us
and
that
and
that's
it.
So
the
thing
is:
okay,
it's
it's
like
efficiently
more
efficient
than
rest,
but
it's
also
points
to
some
other
things
like
we
really
don't
know
the
ui
names,
for
example,
say
for
example.
B
Today,
I
won't,
I
just
want
username
username,
that's
it
and
in
future
I
want
username
and
something
that's
like
user
posts
and
something
so
in
this.
What
we
have
to
do.
We
have
to
go
to
the
back
end.
We
have
to
change
that
point,
maybe
create
a
new
endpoint
or
maybe
create
a
logic
behind
the
certain
endpoint
in
graphql.
We
don't
have
to
touch
the
back
end.
B
In
fact,
we
just
we
can
just
change
the
change
that
declarative
way
in
which
you
are
getting
all
the
data
that
query
in
the
front
end
itself,
and
it
will
just
work.
We
don't
have
to
go
to
the
back
end
and
change
anything
so
that
that
this
is
why
it
is
it
supports
rapid
product
integration,
it's
faster,
that
we
don't
have
to
touch
back
and
just
change
the
front,
and
it
will
just
work
and
it's
clearly
faster
than
that.
B
Another
thing
is
so:
we
write
restored
ones
for
getting
data,
but
it
doesn't
matter
like
what
about
data
sources
like
it
can
be
database.
It
can
be
api,
but
can
be
anything.
The
resource
will
take
care
of
that
and
it
will
just
get
us.
The
data
using
the
graphql,
and
that
is
pretty
much
and
where
we
can
use
craft
will
actually
cover
this
technique
before
this
validation.
We
are
planning
to
use
this
in
messy
server
image
that
is
running
on
your
local
machine
and
the
mesh
ui
right
now
so
yeah.
C
C
Though
open
api
is
used
to
be
called
slacker,
maybe
you
know
about
swagger,
which
was
like
designing
your
your
rest
api
and
describing
it
and
documenting
it,
and
the
whole
okay
is
the
what
does
all
stand
for?
It
stands
for
hypertext
application
language
and
it's
also
sort
of
providing
a
way
to
navigate
your
whole.
Your
whole
resource
tree,
if
you
like,
from
one
entry
point
and
with
you
know,
links
to
other
linked
resources
so
that
you
actually
can
discover
your
resources
and
your
resource
structures
starting
from
one
from
one
end
point.
C
C
I
mean
it's,
it
sounds
like
like
they're
sort
of
like
trying
to
solve
different
at
the
same
problem
in
different
ways.
Like
you
know,
how
do
you
define
the
contract
and
how
do
you
navigate
the
your
resources
and
your
resource
tree?
If
you
like
from
one
starting
point,
so
I
just
wanted
to
know
how
to
relate
to
each
other,
whether
you
would.
What
sort
of
current
trend
is
to
use
graphql
rather
than
open
api
or
swacker
definition
and
twitter.
B
No,
no,
I
I
even
I
you
have
mentioned
this
right
now,
but
I
haven't
even
heard
of
open
api,
but
yeah
I
can
means
as
you're
as
you're
saying
things
like
it
is
something
similar
to
graphql.
So
I'm
getting
some
idea
like
what
this
thing
is,
but
I
really
don't
have
any
idea
about
open
api.
Oh,
I
think
hull.
C
Looks
sounds
a
bit
similar
to
graphql
from
the
sort
of
conceptual
that
you
the
response.
You
know
the
response
you
get
when
you
query
say
for
a
user
and
the
user
is
member
for
a
group,
then
you
would
have
a
sort
of
standardized
set
of
links
that
will
point
to
the
group,
for
instance,
and
then
you
can
navigate
to
the
group
and
then
from
the
group.
You
can
navigate
to
other
members
of
the
group
and
so
on
and
so
forth.
C
C
So
I'm
just
wondering
you
know
how
these
relate
to
each
other
and
whether
it's
like
you
choose
and
whether
you
sort
of
choose
between
graphql
and
hull
and
be
between
graphql
and
and
open
api
or
earlier
swagger,
and
whether
this
is
sort
of
something
you
sort
of
would
compare
to
each
other
and
look
at
the
needs
and
the
solutions
and
then
choose
one
of
those
or
a
combination
or
whether
it's
a
combination.
You
know
whether
you
still
get
a
open
api
definition
out
of
a
graphql.
What
did
you
call
it?
C
A
A
I
will
take
a
swagger
definition
and
help
and
basically
be
a
gateway
between
your
ongoing
swagger
definition
and
graphql,
some
of
them
some
of
those
gateways.
My
understanding
is
that
they
will
they
facilitate
running
both
rest
and
graphql.
At
the
same
time
to
which
I
guess
is
like
inherent
to
what
I
just
said
about
the
the
gateway,
but
which
is
nice,
the
some
of
the
to
to
part
of
your
other
comments.
A
A
A
A
And
so,
if
you
think
for
a
moment
about
how
fluid
this
type
of
an
interface
is
how
much
data
there's
kind
of
so
so.
The
two
two
considerations.
I
think
that
were
at
the
forefront
of
why
graphql
is
a
good
technology
to
use
between
mesh
server
and
measure,
ui
measure
ui
being
the
thing
running
this
mesh
map.
A
Maybe
you
want
to
animate
that
or
show
that
you're
going
to
want
to
have
a
lot
of
real.
You
want
to
have
a
stream.
A
feed
of
updates.
Graphql
incorporates
use
of
websockets
websockets
being
a
nice
way
of
opening
up
kind
of
a
bi-directional
stream
of
info
from
you
know,
from
between
two
between
this
client
and
the
message.
Server
and
the
second
reason
the
graphql
that
it
like
that,
we,
you
know
the
we
were
leaning
into
graphql
over
rest
for
this
is
well
is
because
this
is
just
a
prototype.
A
So
in
my
my
most
recent
previous
role
was
heading
up
technology
strategy
at
solarwinds,
and
so
solarwinds
is
produces
well
60,
something
software
products
and
I'm
going
to
say
the
leading
technology
strategy
for
60
products.
At
a
time,
that'll
give
you
80d,
if
you
didn't,
have
it
before,
but
part
of
doing.
A
A
lot
of
data
and
people
go
to
look
at
it
and
they
they
begin
to
ask
all
kinds
of
questions,
and
by
that
I
mean
they'll,
they
will
ask.
They
will
quote
unquote,
ask
questions
like
well.
I
only
want
to
see
the
reddest
clients
so
they'll.
Ask
that
question
of
the
of
the
map
of
the
visualization
they'll
do
that
by
way
of
maybe
searching
for
a
particular
term
applying
any
kinds
of
filters.
Switching
the
layouts.
They
don't
like
the
concentric
thing.
A
There
are
like
an
infinite
number
of
questions
or
there's
a
lot
of
ways
that
people
are
going
to
want
to
view
the
data,
and
we
want
to
enable
that
and
you
can't
it's
becomes
a
little
constrained
and
difficult.
It's
not
it's
not
that
you
can't
achieve
it
with
rest,
it's
just
probably
easier
with
graphql,
and
so
those
two
considerations
like
facilitating
a
socket
for
live
updates
and
then
facilitating
like
a
very
powerful
query.
As
a
matter
of
fact,
you
think
about
graph
ql
as
its
name,
you
think
about
the
word
graph.
A
Yeah,
so
here's
a
little
bit
of
the
architecture
of
it's.
Actually
it's
right
here,
it's
very
straightforward:
it's
there's
a
graphql
server
in
measuring
that
will
read
from
the
information
that
mesh
sync,
which
I
was
mentioning
earlier,
where
it
would
have
collected
that
information
from
kubernetes.
A
A
There's
something
else
else,
that's
sort
of
being
snuck
into
this
conversation
and
and
it's
this
bubble
up
here,
which
there's
a
repository
in
the
layer.
Five
io
org
called
meschery
operator,
and
it
is
a
young
project.
This
is
where
I
was
mentioning
earlier
that
mesh
think
that
dev
and
others
are
working
on.
C
A
Yeah
yeah,
I
I
character,
yeah
I'll
I'll
bite,
I'll,
say
one
other
thing,
and
that
is
the.
There
was
a
project
at
cisco
that
my
team
was
leading.
It's
a
cloud
management,
cisco's
cloud
management
platform,
and
so
it
was
managing
this
is
you
know
six
seven.
Whatever
years
ago
it
was
managing
openstack
and
vcenter
vcloud,
director
aws,
some
cisco
gear,
but
managing
infrastructure
and
and
the
components
in
the
system
similar
type
setup.
There's
a
there
was
a
client
in
the
server.
The
server
had
a
rest
interface.
A
The
rest
interface
was
constrained
and
it
because
of
the
way
it
was
designed
in
the
ui.
That
was
a
client
of
the
rest
server.
The
user
experience
was
constrained
as
well,
and
it
made
it
very
kind
of
clicky.
You
have
to
kind
of
click,
to
get
more
information
and
and
the
queries
that
you
could
ask
of
rest
just
like
they
weren't
very
powerful
and,
moreover,
the
authorization
of
that
rest.
A
Well,
then
they
were
just
denied
access
to,
and
so
so
what
we
ended
up
doing
was,
you
know,
was
like
creating
an
escape
hatch
to
have
a
rest
endpoint
that
accepted
a
sql
query,
which
is
like
I
wince,
because
it
seems
like
it
sounds
like
you
know,
and
then
and
then
there
was,
and
then
there
was
a
security
hack
and
half
a
billion
dollars
later
there
was
like
it's
a
bad
design,
but
you
could
send
in
a
rest,
sql
query.
That
was,
you
know.
A
Well,
there
was
a
lot
of
security
applied
to
it
on
the
back
end
to
try
to
help
prevent
things,
but
but
the
point
was
is
like:
if
the
project
was
going
to
die,
if
we
couldn't
give
the
right
user
experience,
and
so
in
my
mind,
graphql,
I
use
this
in
mental
analogy.
For
me,
like
graphql
is
almost
what
we
did
in.
That
scenario
was
bring
the
power
of
sql
to
rest
and
that's
kind
of
a
sentiment
that
I
sh
you
know
share
about.
Graphql.
B
C
C
So
yeah
it
was
sort
of
more
of
a
concern.
I
don't
know
whether
you
have
discussed
this
or
that
we,
maybe
you
know,
should
be
aware
of
that.
We
should
you
know
as
you're
writing
down
now.
Maybe
discuss
much
more
on
issues,
especially
things
that
sort
of
like
architectural
decisions
and
other
decisions
that
we
want
to
go
back
to,
but
also
troubleshooting
find
a
good
way
to.
A
C
Scaling
to
2000
members
and
and
lots
more
git
top
notifications,
then
maybe
you
have
a
retention
time
of
a
week
and
that's
then
we
can't
almost
have
no
discussions
on
slack,
yeah
they'd
be
casual
yeah
and
I
I
I
google
quickly
and
slacks
doesn't
sort
of
like
offer
free
enterprise
plan
to
open
source
projects.
I
think
so
you
get
reduction
in
price,
but
it
still
costs
a
lot
of
money.
C
A
D
A
A
D
Are
none
that
I
I
think
would
be
of
major
concerns
actually
also
like
see.
I
am
using
discord
for
the
past
year
and
the
way
I
have
set
up
my
servers
is:
I
have
included
bots
that
allow
for
a
rules,
channel
and
verification
and
all
that,
so
all
in
all,
I
think
it's
quite
feature
rich
and
we
can
use
it
effectively.
A
B
A
A
We
will
talk
about
this
new
project
next
time.
Michael,
I
agree
I
guess
to
for
my
part
like
hey.
I
agree
that
use
of
github
issues
or
using
github
issues
and
using
github
discussions
if
people
like
which
I
think
some
of
you
are
familiar
with.
Some
of
you
maybe
haven't
seen
a
newer
aspect
of
github
discussions
that
those
two
suggestions
are
aligned
with
what
we
started
talking
about
at
the
start
of
the
call
which
was
hey
to
the
extent
that
we
can
you
know
not
everything.
A
It's
not
a
the
one.
When
I
refer
to
public,
it's
not
about
it's,
not
about
things
being
hidden
it's
about
or-
and
I
don't
even
consider
that
that's.
Why
there's
a
ton
of
discussion
that
happens
privately,
that's
not
the
reason
it's
about
what
happens.
Is
you
want
to
just
ch
what
happens
a
lot
of
times?
You
just
want
to
check
with
somebody
like
hey.
I
was
just
thinking
about
this.
A
You'll
save
yourself
a
lot
of
time
and
repeating
of
yourself,
if
you
do
it
publicly
the
reason
that
slack
is
to
be
frank,
like
the
reason
that
slack
is
the
and,
as
a
matter
of
fact,
like
it's
intentional
that
we're
not
using
mailing
lists
for
a
lot
of
communication.
That
would
actually
be
another
way
of
having
things
persistent
but
yet
still
suffer
from
having
to
like
coalet.
You
know
bring
everything
together
to
understand
what
happened.
It's
a
little
bit
easier
in
email.
A
A
But
so
I
don't
yeah.
I
don't
mean
to
be
dismissive
error,
so
I
hopefully
very
encouraging
what
michael's
saying,
which
is
exactly
what
needs
to
be
done.
I'll
admit.
For
my
part,
I
don't
consider
that
it's
out
of
laziness,
but
it's
out
of
not
out
of
being
busy
and
not
forcing
myself
to
take
my
conversation
to
a
persistent
place
to
just
even
go
back
into
what
I
just
chatted
and
copy
and
paste
that
into.
A
A
To
michael's
point,
I
I've
just
this.
Last
week,
I've
even
struggled
a
few
times
where,
just
this
morning,
I
was
working
on
husseina
your
your
issue
on
mastery
ctl
like
it,
my
you
do,
a
mastery
ctl
system
start.
My
doctor
starts
right
up,
it's
pretty
cool
and
I
had
some
more
comments
and
I
had
some
thoughts
to
share
with
you
and.
C
A
A
I
already
given
you
feedback
on
github,
and
my
thinking
was.
Maybe
I
shouldn't
give
you
more
feedback
on
github
because
it
might
feel
to
you
like.
If
I
were
in
your
shoes,
I
might
have
rolled
my
eyes
like,
oh,
like
isn't
this
guy
going
to
let
it
go
like
we
just.
I
feel
like
we're
going
back
and
forth
now
like,
whereas
it
was
fun
to
contribute
this
new
feature.
Now
this
you
know
now
it's
like
becoming
a
hassle
and
that's
actually
why
I
was.
A
I
didn't
switch
into
slack
on
you
and
I
actually
haven't
given
you
this
second
bit
of
feedback
yet,
but
but
I'm
just
thinking
aloud
with
everyone
with
with
me
who
here
like
because,
like
you
ever,
have
an
email
exchange
and
it
goes
back
and
forth
about
two
three
times
and
then
all
of
a
sudden.
It
starts
to
feel
like
we're,
arguing
we're
not
communicating
like
you
know,
and
then.
A
A
I
think
that
we
everyone
should
be
trying
to
communicate
as
much
publicly
as
possible.
For
my
part,
it's
it's
a
it's
a
real
need.
I
was
going
to
talk
about
potentially
spinning
up
a
new
project
with
an
ask
for
interested
parties,
and
I
want
everyone
to
look
at
it
and
see
if
they
are
interested
or
not,
and-
and
so
I
want
to
over,
communicate
that,
like
you
know,
you
want
to.
A
A
Who
it's
a
good,
so
I
so
I
for
my
part,
like
I
wanna,
I'm
gonna,
pledge
to
remind
others
and
myself
to
to
follow
up
the
diligence
of
putting
it
into
a
github
issue
or
putting
it
into
a
dock,
and
it's
really
needed
for
my
part,
because
I
I
get
you
can
see
it
on
my
face.
Sometimes
I
get
frustrated
when
I
have
to
say
the
same
words
have
the
same
conversation
five
times
and
and
whose
fault
is
it
mine?
Because
I
didn't
go
write
it
down.
A
A
Good
now
that
we
got
a
lecture
at
the
start
of
the
call
and
one
at
the
end,
it's
a
really
happy
friday.
Thank
you.
Ayush,
thanks
for
coming
and
rudolph
oswald,
michael,
a
great
call
out
dev.
I
appreciate
you
jumping
up
jumping
in
to
share
your
knowledge,
for
those
that
are
want
to
hear
about
get
nighthawk
well.
Ping
me
in
the
slack
I'll,
probably
send
out
a
different
meeting.
Invite
if
folks
want
to
hang
around
and
discuss
it.
It's
not
an
urgent
thing.