►
From YouTube: Let's talk about contributing - Specification
Description
How to start contributing to the AsyncAPI specification
A
On
okay,
we
are
live,
hey
everyone
I'm,
so
sorry
about
the
so
I
was
having
some
technical
issue.
I
always
have
problem
with
restroom
when
it
comes
to
my
microphone,
which
I
was
able
to
like
resolve
as
soon
as
possible
or
as
soon
as
I
can
right.
So
welcome
to
this
live
stream.
This
is
going
to
be
an
interesting
one,
and
this
is
our
first
live
stream
right.
This
is
our
first.
A
Let's
talk
about
contributing
live
stream
for
this
year
right
for
2023,
which
is
why
I'm
super
excited
about
this
today
and
so
I'm,
going
to
give
you
a
tip
or
or
an
idea
of
what
this
live
stream
is
about
right.
So
I
have
a
very,
very
an
important
guest,
a
very
good
friend
of
mine
at
the
backstage
which
I'm
going
to
bring
up
stage
because
you'll
be
dinner,
I'll
be
talking
and
walking
us
through
everything.
So
to
this
live
stream.
You
know
from
the
title:
it's
called.
A
Let's
talk
about
contributing,
but
the
specification
360
specification
right,
because
a
lot
of
contributors
commentary
come
to
the
escape
by
Community
to
contribute
and
yes,
I
know.
We
have
tons
of
tools
in
the
repositories
in
the
project
which
you
can
contribute
to
as
a
contributor,
but
I
see
very
few
people
tend
to
contribute
to
the
async
API
spec
itself,
right
and
yeah.
I
know
for
some
reason
right,
because
they
mostly
don't
understand.
A
A
It
would
be
a
single
live
stream,
but
I
don't
know
how
that,
because
it
might
get
along
that
we'll
have
to
like
do
a
part,
two,
a
second
part,
but
without
no
further
Ado
I'm
gonna
bring
our
guests
for
today,
Fran,
so
I'm
gonna
introduce
him
he's
gonna
introduce
himself.
He
said
himself
so
so
before
before
I
bring
front
on
so
I
was
also
like
in
one
of
France
take
out
loud
episode,
which
I
was
like
so
glad
to
be
there.
A
So
if
you
don't
know
about
the
thinking
out
loud
and
stream,
so
you
can
go,
join
just
recent
API
playlist
and
look
for
thinking
out
loud.
It's
what's
fun
like
post,
really
really
interesting
talks
with
amazing
people,
so
I
was
also
like
opportunity
to
be
the
so
I'm
gonna
bring
Fran
up
now
so
Fran
if
you're
ready.
Just
let
me
know,
I
see
you
already
so
I'm
picking
you
up
now
front.
C
B
A
C
C
B
B
B
B
B
The
version
two
version
two
I
already
got
some
contributions,
but
but
yeah
mainly
it
was
my
my
work
and
and
I'm
getting
less
and
less
work
to
do
over
the
the
years
on
the
spec,
which
is
cool
but
yeah
as
Ace
said,
is
it's
complicated
I,
don't
know
why
people
often
don't
contribute
to
the
spec
I,
don't
know
if
it's,
because
it
sounds
boring.
If
it's
because
it
sounds
difficult
or
what
is
it
so
yeah
happy
to
answer
any
questions.
A
B
A
B
A
A
Yes,
so
front
already
introduced
himself.
An
interesting
Folk
I
certainly
know
he's
a
creator
of
Eastern
kpi
and
he's
also.
He
has
like
build
so
many
interesting
tools
and
which
one
of
my
one
of
my
most
favorite
one
is
Glee
right.
So
Glee,
an
amazing
project
also
always
looking
for
contributions.
So,
if
interested
just
add
the
front
is
looking
for
help.
So,
but
today
we're
not
talking
about
Glee,
because
I
already
did
a
less
talk
about
contributing
live
stream
about
Glee
separately,
which
one
of
Team
maintainers
solvish,
very,
very
interesting.
A
A
A
So
I
think
people
wants
to
know
first
thing
how
to
start
contributing
like
the
first
step,
to
contributing
to
this
baby
aspect
right
and
me
right
from
from
my
own
personal
point
of
view
right
when
I
want
to
start
contributing
to
spec.
The
first
thing
that
actually
chased
me
away
was
like
okay.
This
looks
very
simple
right,
like
the
the
the
codes
and
everything
and
I
don't
even
understand
what
are
we
changing?
What
are
we
writing?
A
What?
Oh,
we
adding
features
to
these
things
right
and
the
first
thing
I
felt
was
just
the
first.
The
first
step
right,
I
didn't
actually
get
the
first
step
on,
like
other
other
tools
in
the
in
the
community,
in
the
project
right,
I.
Think
this
page,
just
I,
don't
know
yeah
it's
kind
of
complicated.
A
B
B
C
B
Unavoidable
right
so
yeah,
but
I,
I,
I,
think
I
I
get
what
you
say
like
you,
don't
have
a
way
to
see
if
it
works
or
not
right,
like
you,
don't
have
a
way
to
exactly
try
it
to
test
it
to
to
play
with
it.
Yeah.
The
thing
with
this
is
that
when
you're
writing
this
back,
it's
true
that
there
are
many.
There
are
multiple
factors
here
right
that
you
need
to
take
into
account
for
sure
the
development
experience
or
the
writing
experience
of
the
spec,
because
it's
not
really
development.
B
The
thing
is
that
it's
what
you
said
like
like
you,
don't
have
a
way
to
easily
test
it
to
easily
try
it,
but
so
what
I
do
usually
is
I
open
code,
editor,
vs
code,
for
instance?
That's
what
I
use
mainly
and
I,
don't
type
the
spec
I,
don't
write
the
spec
I
write.
What
I
want
the
async
API
to
look
like
right.
So
if
I
want
to
add
something
to
the
async
pay
file,
that
is
not
there
yet,
then
what
I
do
is
I.
B
Add
this
to
my
sqpay
file
like
assuming
or
imagining
that
this
is
already
on
the
spec,
so
I
start
from
the
end
from
the
very
end,
like
imagine
that
this
thing
is
already
on,
the
spec
has
been
added.
How
will
you
like
it
to
look
like
and
that's
what
I
do
and
and
I
do
tests
trials?
If
you
want
with
these
documents
and
trying
to
imagine
like
how
will
it
look
like
on
on
code
on
code
generation,
on
documentation
generation
and
on
other
tools
right?
How
will
it
be
interpreted
by
Glee?
B
How
will
it
be
interpreted
by
code
generators?
How
will
it
be
interpreted
by
other
tools,
what
if
it's
used
in
a
websocket
API,
what,
if
it's
using
an
HTTP
API?
What
if
it's
used
with
Kafka
with
mqtt
with?
Will
it
still
make
sense
or
is
just
for
a
specific
use
case?
So
I
ask
myself
all
these
questions,
but
I
think
it's
a
it's
just
it's
the
product
of
multiple
years,
right,
working
on
it
and
making
a
lot
of
failures
and
making
a
lot
of
mistakes
on
the
spec
as
well.
B
The
most,
the
most
famous
One,
probably
in
the
community,
is
the
publish
And
subscribe
confusion.
This
has
been
my
biggest
mistake.
If
you
want
it's
not
really
a
mistake,
but
but
yeah
it
wasn't
an
it's
an
unfortunate
decision.
I
will
say
it's
not
a
mistake
per
se.
It
makes
sense.
Well,
it
makes
sense
it.
A
Funniest
thing
is,
I
was
I,
was
in
a
live
stream
and
I
was
doing.
You
know
doing
this
nice
example
right.
A
real
life
example
with
an
async,
API
and
yeah
I
was
trying
to
like
I
got
to
the
point
of
publishing
and
I
was
so
confused
and
I
was
embarrassed
because
I
was
like
I'm
live
and
I'm
so
confused
about
when
to
publish
when
you
subscribe
and
I
was
like
no.
A
B
It
happened
to
me
as
well
during
a
workshop,
I
was
I,
was
using
published,
And
subscribe
reversed
right,
so
I
was
using
the
subscriber
it
will
be
published
and
and
and
the
opposite
right
and
and
it
wasn't
working
and
I
was
like
why
it's
not
working
like
the
code
generation
wasn't
working
and
I
was
like,
oh
damn
it
I
I
used.
It
reverse,
like
the
other
way
around
and
and
I
used
it
reversed,
and
the
problem
is
that
I
already
explained
the
meaning
of
publish
And
subscribe
to
the
attendees
of
the
workshop.
B
So
then
I
had
to
go
back
and
say
you
know
what
forget
about
what
I
said
subscribe
forget
about
that,
let's
restart
the
whole
thing,
because
that's
the
basic
thing
and
yeah
published
actually
doesn't
mean
what
you
think
it
means
right.
It's
actually
something
completely
different
from
the
other
point
of
view
and
and
yeah,
and
it's
like
even
this
thing
like
from
the
other
point
of
view,
like
some
people
are
like
what
point
of
view
like
what
is
the
other
point
of
view?
Why?
B
B
I
have
to
run
and
I
don't
run
a
lot
so
so
yeah,
so
that's
even
worse.
So
the
thing
is
that
you
gotta
make
you're
gonna
make
mistakes,
that's
not
a
problem.
The
problem
is
that
you
get
a
start.
You
gotta
start
imagining
I,
think
or
that's
what
I.
That's
my
Approach,
you
gotta
start
adding
stuff
to
the
cqba
file,
changing
something
like
I.
B
Don't
like
this
I
I
want
this
to
look
instead
of
this
way,
I
wanted
to
look
this
other
way
or
I
want
to
add
it
like
this
or
like
that,
and
you
basically
write
a
and
invalid
asynkp
file
right.
It's
an
invalidating,
API
file
because
it's
not
yet
in
the
spec,
but
you
want
to
make
that
file
valid
right
so
after
that,
what
I?
What
I
usually
do
is
okay,
so,
let's
scale
through
all
the
things
that
I
just
added.
B
Hopefully
it's
just
a
couple
of
things,
one
or
a
couple
of
things.
So
let's
go
to
the
spec
to
the
section
where
it
it
is
described
or
the
parent
object
is
described
and,
let's
add
it
there.
Let's
add
this
property
there.
Let's
add
the
definition
of
what
it
is,
what
it's
doing
why
it
like?
Why
will
people
use
it
and
and
probably
on
the
spec?
You
do
not
know
why,
but
you
add
what
it
is.
B
You
need
to
add
what
it
is
and
what
it
does
and
and
all
the
potential
restrictions
but
I'll
get
into
that
in
a
second
and
then
on
the
pull
request.
I
will
explain
to
the
to
the
maintainers
to
the
rest
of
the
maintainers.
I
will
explain
so.
This
is
why
I
want
to
add
that
right.
So
here's
a
little
bit
of
context
I,
want
to
add
the
possibility
to
I,
don't
know
authenticate
using
scram
scrum
512
whatever.
B
Why,
because
I'm,
using
Kafka
and
Kafka,
is
supporting
this
authentication
method
and
it's
not
in
the
spec
yet
actually
this.
This
is
a
real
example
that
I
didn't
do
it's.
It
was
Dale
Lane
who
added
it.
He
wanted
to
add
this
kind
of
authentication
to
the
to
the
spec
and
it
wasn't
there
right
so
and
he
called
and
use
it
on
Kafka.
So
that's
a
valid
case
like
okay,
so
yeah
Kafka
peoples
will
be
able
to
use
a
spec
with
this
authentication
method.
B
So
so
that
is,
that
is
the
first
step.
Definitely
I
mean
that
is
the
second
step.
Adding
it
to
creating
a
pull
request
thing
is
that
it's
a
spec,
it's
a
it's,
not
documentation
right.
Some
people
think
it's
documentation,
it's
not
documentation.
It
can
serve
the
purpose
for
documentation
for
reference,
but
it's
not
that
it's
not
meant
to
be
documentation.
B
It's
not
meant
to
be
human
friendly
in
the
sense
of
oh
look.
How
well
explained
it
is
that
it
even
has
examples
and
tutorials,
and
so
no
no,
no
it's
it's
it's
a
formal
document.
It's
a
law
right!
It's
a
law
definition,
so
you're,
creating
you're
a
lawyer,
basically
you're
a
lawyer
I
mean
you're,
not
a
lawyer,
you're,
actually
a
politician
creating
laws
right
in
this
case,
but
yeah
you
cannot
lawyer,
you're,
creating
a
law
or
modifying
a
law.
So
so
you
gotta
be
super
specific
right.
B
You
got
to
be
super
specific
and
super
clear
about
what
things
do,
because
if
you
leave
some
door
open
to
misinterpretation,
then
people
are
gonna
open
that
door
right.
So
that's
a
problem
like
you
need
to
really
think
deeply
and
say:
I'm
gonna.
Add
this
description
to
this
new
property
that
I
just
added,
and
not
just
that
I'm
gonna.
Consider
all
the
potential
ways
that
people
might
want
to
use
this
in
a
different
way
that
it's
intended
so
I'm
gonna
make
it
super
clear
here.
B
It's
intended
to
be
used
like
this
for
this,
and
for
that
nothing
else,
and
you
have
to
use
specific
vocabulary
of
specifications
you
should
be
using,
must
should
things
like
this
right
so
when
or
it's
recommended,
so
you
need
to
be
careful
with
these
words
right
and
learn
them
in
the
beginning
of
this
pack.
There's
a
link
to
the
RFC
that
it's
that
we
actually
follow,
which
is
exactly
using
this
language.
B
B
We
just
recommend
that
you
do
it
like
this,
but
if
you
don't
want
to
or
if
you
don't
want
to
even
support
the
the
field
at
all,
that's
up
to
you
right
so
so
yeah.
So
we
we
have
a
few
of
that.
We
have
a
few
of
recommended
shield
and
and
Mast,
and
this
is
something
that
you
have
to
get
familiar
with
when
you
want
to
write
this
back,
but.
B
Actually,
it's
not
when
you
went
when
you
want
to
write
the
spec.
It
says
this
is
when
you
want
to
master
writing
a
spec.
Actually
thing
is
that
for
contributors
looking
or
at
this
or
watching
this
live
stream
or
watching
the
recording,
what
they
need
to
know
is
just
make
a
change
on
one
of
your
async
pay
files
and
see
if
it
makes
sense
for
you
then
go
to
the
spec,
which
is
a
markdown
file.
B
Doing
that
and
don't
worry
about,
must
should
recommend
that
blah
blah
blah
and
so
on,
because
we're
gonna
be
there
we're
going
to
be
there
reviewing
the
pull
request
so
I'm
out
I'm,
actually
one
of
the
the
the
the
people
there
of
the
maintainers
who
are
gonna
chase
you
to
make
it
clear
that
this
is
a
must
that
this
is
not
a
must
but
Kinder
immersed
and
that
something
is
actually
just
optional
right.
So
I'm
gonna
chase
you.
So
don't
worry,
I'm
gonna,
just
rebuke!
B
Your
your
code
and
leave
a
message
and
even
leverages
a
suggestion
on
how
you
could
regret
the
same
sentence,
so
it's
less
open
for
interpretation
and
so
on,
and
and
so,
and
so
this
is
for
contributing
to
this
pack
right
that
that
is
just
I'm,
not
even
touching
on
the
stages
of
the
of
the
spec,
because
I
think
for
the
initial
contribution
process.
It's
not
needed.
She
just
you
just
make
a
contribution,
a
pull
request
or
an
issue
suggesting
that
you
are
gonna.
B
A
B
C
B
B
B
C
C
B
Happening
I
can
I,
cannot
hear
you,
but
I
can
read
your
lips.
We
can
probably
continue
like
this,
so
yeah
and
and
continuing
with
what
I
was
saying
about
the
spec.
The
most
important
thing
is:
don't
we
still
don't
hear
you
thanks?
So
don't
don't
fear
it
don't
fear
introducing
a
change
in
the
spec,
because
it's
I
think
it's
a
beautiful
journey
and
sure
it
this.
It
requires
some
knowledge
about
apis
and
even
driven
architectures.
B
B
You
don't
have
to
be
an
expert
on
everything,
because
you
you
will
not.
You
will
not
never
be
able,
so
so
even
myself,
I'm
working
on
this
for
many
years
already
and
I
still
don't
know
most
of
the
the
protocols
I
and
I
never
touched
them
at
all,
and
we
still
and
we
support
them,
but
we
gotta
trust
the
community
right.
If
the
community
says
that
this
is
the
way
it
works,
I
trust
them
because
I
don't
know
so
so.
Yeah.
B
B
B
So
as
as
Ace
was
saying,
it's
a
media
that
I
cannot
leave
messages
on
the
chat
here.
I
have
to
sign
in
I
think
so.
I
am
I,
run
the
Thinking
Out
Loud
podcast,
video
podcast,
and
this
year,
I'm
starting
again,
I
actually
started
already,
but
this
year
is
not
going
to
be
live,
it's
going
to
be
recorded,
episodes
and
and
yeah.
B
So
if
you
want
to,
if
you
want
to
purchase,
if
you
want
to
actually
watch
what
we
did
was
or
or
want
to
have
a
look
at
what
we're
preparing
next
head
over
to
L
thinking
out
loud
t-o-l
dot
show
so
that
is
the
URL
I
love
this
new
tlds
top
level
domains,
so
yeah,
t-o-l
dot,
show
Shameless
plaque
as
genus
is
saying
and
exactly
I'm
gonna.
Do
it
of
course.
C
B
So
speaking
of
seamless
plaques
as
Jenna
said
yeah,
there
is
a
book
coming
up,
but
not
for
racing.
Api
3
release
it's
going
to
be
for
it's
going
to
be
for
even
driven
architectures,
but
I'm
gonna
be
using
async
pay
3
as
a
as
a
way
to
explain
how
to
build
event,
driven
architectures
right
and
I'm
now
working
in
it.
So
it
and
version
three
of
the
spec
is
going
to
be
released
on
June
this
year.
So
yeah
I'm,
not
gonna,
have
the
the
book
on
June.
B
But
definitely
not
this
I
mean
maybe
June,
but
not
this
year,
so
so
yeah,
most
probably
for
next
year.
The
the
book
will
be
live
so
so
yeah,
but
that's
another
problem,
because
we
have
a
great
Community
doing
and
writing
great
documentation
and
tutorials.
So
they
will
be
updating
the
the
documentation
and
the
tutorials
so
that
you
can
learn
a
Singapore
3
properly.
So
yeah.
B
I'm
I've
never
explore
LinkedIn
learning,
but
but
yeah
I
agree
with
you
like.
If
we
can
be
on
in
any
in
many
platforms,
that
would
be
perfect.
I
suggest
that
you
join.
If
you
didn't,
do
it
yet
or
Slack,
and
there
is
a
training
channel
on
slack
and
barbano
will
be
super
glad
to
hear
all
this
feedback,
because
so
you
can
type
a
message
there
and
say:
Hey
I'm
I
will
be
super
interested
in
some
LinkedIn
learning,
resources
about
texting,
kpi
or
any
other
platform
that
you
might
like.
So
so,
yeah.
B
So
you're
saying
that
you
want
to
know
what's
my
process
while
finding
a
new
feature
or
for
finding
a
new
feature,
I
guess
it's
usually
coming
out
of
a
need.
I
need
to
do
something:
I'm,
building
an
application
or
an
even
driven
architecture
myself
to
test
something
and
I
want
to
do
it
with
this
in
kpi
and
I
can't
if
it's
related
to
code
I,
go
to
the
tool
and
update
the
tool
right.
But
if
it's
related
to
the
spec,
then
I
cannot
Define.
B
B
C
B
A
C
C
C
B
B
A
C
B
A
B
So
we
gotta
we,
we
got
a
few
questions
and
I
was
answering
I,
already
answered
all
the
questions
and
and
yeah.
That's
that's
cool,
yeah,
I,
don't
know
what
else.
Maybe
people
can
suggest
what
questions
they
have,
what
they
want
to
know
about
to
about
contributed
to
this
bag
in
the
meantime,
something
that
comes
to
my
mind
is
that
I
I
will
want
to
remark.
Is
that
when
contributing
to
the
spec
we
gotta
be
careful
right,
like
not
I
mean
not
the
person,
that's
contributing!
B
B
C
B
B
B
Please,
don't
fear
that
don't
fear
that
situation.
So
it's
completely
okay
and
it
still
happens
to
me
from
time
to
time
that
I
suggest
something
that
actually
doesn't
make
sense
right
or
yeah
like
when
I
suggest
it.
It's
like.
Oh,
that
would
be
super
cool
to
have
it
blah
blah
blah
right,
like
it's
a
cool
super
use
case,
but
the
reality
is
that
once
you
think
twice
and
you
get
the
argument
of
your
faults
of
the
community-
it's
like
okay,
yeah,
it's
true!
C
B
C
B
B
So
yeah
there
are
four
stages
of
a
contribution.
One
is
called
strowman,
so
strawman
contribution
is
just
like
just
have
a
thought
and
you
just
throw
it
there
in
some
way.
Usually
it's
an
issue
right.
It's
not
a
pull
request,
because
it's
just
like
I'm
just
gonna
leave
the
comment
here
just
to
see
what
people
think
and
it
doesn't
have
to
be.
B
Really
you
don't
have
to
describe
it
really
well,
so
it's
just
a
yeah
as
a
as
implied
by
the
name
right,
so
it
it
has
to
be
just
that
that
you
grind
it
there
it
you
started
you
you
leave
it
there.
So
people
get
to
think
about
it.
If
it's
not
clear
enough,
then
everyone
else
is
going
to
ask
you
like.
Can
you
please
clarify
because
I
don't
still
get
it?
What
you
mean?
That's
completely
fine,
then
at
some
point
you
open
a
pull
request
because
yeah
people
seem
to
like
what
you're
proposing.
B
B
So
you
edit
the
spec,
but
it's
not
really
complete,
but
at
least
you
know,
like
you
start
doing
it
you,
you
provide
some
illustrative
examples
if
you
have
them
or
identify
potential
concerns
and
challenges
and
drawbacks
I'm
reading
the
I'm
reading
this
back
right
now,
I
sound
like
it's,
it's
all
coming
from
my
head,
but
it's
not
I'm
reading,
so
so
yeah.
So
so
that
will
be
the
the
stage
one
The
Proposal
stage
right,
but
it
will
be
a
pull
request.
B
Even
if
it's
a
stupid,
pull
request
stupid
as
in
small
right,
then
at
some
point
you
keep
developing
this
pull
requests.
You
keep
improving
it
and
at
some
point
your
your
pull
request
will
will
contain
a
precise
definition
of
the
of
what
you
mean
right
and
it
will
be
like
everything
like
it
would
will
be.
Super
clear
and
or
mostly
clear
right
and
the
maintainers
will
ask
you
to
implement
that
feature
in
the
async
API
parser
and
in
decent
pages
and
schema
right.
B
So
you
have
to
add
it
to
those
two
tools:
the
parser
and
the
schema,
because
the
Json
schema
definition
of
the
spec
is
like
kinda,
like
a
machine,
readable
definition
of
the
spec.
That
tools
are
going
to
leverage
right,
so
you
need
to
Define
it
there
as
well
and
you
and
you
need
to
Define
it
on
the
parser,
because
the
parser
is
again
it's
like
an
if
it's
not
in
the
parser.
B
It's
not
going
to
be
useful
for
anyone,
because
if
the
parser
doesn't
understand
that
feature
that
new
feature
that
you're
adding,
then
people
will
not
be
able
to
develop
tolling
on
top
of
your
feature,
because
they
will
not
see
it
right
so
so
yeah.
You
need
to
add
that
at
these
two
things
and
don't
worry,
if
you
don't
know
about
GS
or
if
you
are
really
bad
at
writing
code
or
whatever,
which
might
happen.
B
I
am,
for
instance,
I
am
super
bad
at
that
and
and
and
the
more
and
the
more
I
grow
the
the
worse
I
become.
So
so
yeah
don't
worry
about
that.
There
are
always
community
members
saying
helping
like
that.
It,
for
instance,
happened
to
one
of
our
community
members
making
a
contribution
to
the
spec.
He
was
like
you
know
what
I'm
proficient
in
Java,
right
and
Scala
and
so
on,
but
I
I
know
nothing
about
JavaScript.
So
I
think
it
was
magic.
B
Who
said
like
don't
worry,
I'll
take
care
of
this
I'll.
Take
care
of
this
and
I'll
help
you
and
I'll
implement
this
feature
on
the
JavaScript
parser.
So
you
don't
have
to
do
everything
right
so
forget
about
that.
We're
a
community!
It's
a
it's!
A
team
work
right.
It's
a
community
work!
It's
just
that
your
team
is
huge
right
and
you
probably
don't
even
know
who
they
are
so,
but
that's
the
beauty
of
this
right.
That's
the
beauty
of
the
community
work.
B
You
don't
have
to
know
it
just
say
it
loud.
Like
I,
don't
know
anything
about
this
messaging
protocols,
so
if
someone
knows
them,
can
you
please?
Let
me
know
if
it's
if
it
makes
sense
for
you
as
well
and
that's
it
it's
a
community
work.
So
it's
not
all
your
responsibility.
It's
just.
We
need
people
to
start
the
conversation
right.
B
You
know
I'm
still
dummy
on
typescript,
even
though
I
started
using
it,
but
I
still
feel
like
I'm,
not
even
professing
them.
It
I
keep
forgetting
that
I
have
to
add
types
so
so
yeah,
so
that
so
that
happens,
and
that's
completely
fine
and
and
for
instance,
I
never
used
AWS,
SMS
or
sqs
services,
and
it's
probably
the
most
widely
used
messaging
service
and
messaging
protocols.
B
Right
now
that
that
have
that
has
to
do
with
async,
API
and
I
never
use
them.
I
never
never
did
so,
because
I've
never
found
the
need
or
time
so
I
people
sometimes
ask
me
about
this
services,
or
or
protocols
and
I
am
like
I.
Don't
know,
I
just
know
that
they
exist,
but
I
have
no
idea,
that's
it,
but
but
that's
really
I
don't
need
to
know
right,
so
you
don't
have
to
know
as
well.
B
B
Imposter
syndrome
yeah
so
remove
your
imposter
syndrome,
because
it's
big
it's
it's
big
on
on
all
of
us
right,
not
not
just
on
you,
so
try
to
try
to
destroy
it
or
at
least
block
it
right.
That's
what
I
do
I
still
have
it,
but
I
just
don't
listen
to
it.
That's
that's
the
thing
so
just
shut
it
down
and
the
spec
is
really
a
driver
for
imposter
syndrome,
because
it's
usually
seen
as
a
something
that
only
the
gods
can
touch
right,
like
only
the
people
exactly.
B
Touch
because
these
people
are
the
ones
that
know
exactly
what
they're
doing
and
I
who
am
I
to
catch
this
right
so
but
the
reality
is
that
it
cannot
be
like
this
and
nobody
is
a
god
actually
and
and
even
and
even
if
you're
a
God,
you
were
never.
You
were
not
a
god
when
you
started
right,
so
you
might
become
an
expert
on
something.
B
Writing
the
spec.
I
never
grow
this
back
myself,
but
I
was
like
okay.
So
this
is
a
markdown
file.
What
can
go
wrong
right?
So
and
yes,
so
if
you
write
it
yourself
alone,
then
it's
a
huge
job
and
it's
a
huge
responsibility
but
we're
in
a
community
and
we
can
all
collaborate
as
a
as
a
distributed
brain
right.
So
we
can.
We
can
multiply
the
knowledge
because
it
will
be
my
knowledge,
your
knowledge,
the
other
ones,
the
other
people
knowledge.
So
all
combined.
B
C
A
Yeah
so
I
am.
It
is
quite
related
to
Pedro's
question
about
you
know
as
a
contributor.
You
might
eventually
not
have
I
hope,
I'm,
audible,
this
time
cool.
So
as
a
new
coach
as
a
new
contributor
right,
you
might
not
have
this
proposal
to
do
right,
so
it
might
be.
You
want
to
fix
existing
issue
right
or
or
just
like
you
know.
A
Sometimes
somebody
just
drops
a
proposal
there
right,
but
not
implementing
it,
but
maybe
somebody,
let's
say
Pedro,
for
instance,
jobs
a
proposal
about
on
his
back
right,
but
he
doesn't
want
to
implement
it
or
he
doesn't
have
time
to
implement
it,
and
it
sounds
like
a
really
nice
proposal
right.
Somebody
in
the
community
wants
to
implement
it
right,
but
this
is
the
first
time
this
person
is
contributing
to
respect.
So
I
was
thinking
right.
We
this
this
old
session
is
about.
A
You
know,
breaking
down
all
these
packets,
how
to
contribute
to
respect
and
stuff.
Then
I
was
thinking
what,
if
we
can
have
a
recession
right
about
where
you
walk
us
through.
You
know
how
this
contributions
phase
looks
like
right.
Writing
the
code
implementing
a
simple
proposal
or
fixing
just
a
simple
good
first
issue
on
the
call
right.
What
do
you
think
they
think
it
is
something
you
are
up
for.
B
B
B
That's
a
that's
a
good
way
to
to
start
with
it
to
start
contributing
pick,
something
that
that
might
look
appealing
to
you
or,
if
you
don't
know,
because
that
might
happen
as
well,
that
you
don't
know
what
can
be
easy
or
what
can
be
manageable
for
you
just
head
over
our
Slack
workspace,
there's
a
how
to
contribute
Channel
there,
where
Ace
is
continuously
monitoring
even
during
the
night
during
the
in
his
dreams
in
his
dreams.
He's
also.
B
He
is
trust
me
so
so
yeah,
so
you
can
ask
for
guidance
there
and
and
yeah,
and
if
Ace
doesn't
reply,
someone
else
will
do,
but
yeah
Ace
is
going
to
reply
at
some
point
there
because,
as
I
said
like
Ace
is
monitoring
it
or
Lucas
might
be
monitoring
it
or
maybe
someone
else
from
the
community.
Since
your
comment
and
say
sure,
I'll
be
happy
to
help
you
so
so
yeah
or
maybe
something
as
easy
or
as
stupid.
B
I,
don't
like
to
say
stupid
because
I
might
have
another
meaning
in
English,
but
as
just
going
there
and
asking
okay,
can
you
please
help
me
find
an
issue
that
you
think
I
will
be
able
to
to
solve
and
that's
completely
fine.
We
can
do
a
call
or
something
we
can
have
a
chat
and
say:
okay,
so
you
want
to
solve
one.
B
B
B
C
B
B
C
A
A
So
so
talking
about
that
now,
we've
learned
so
much
about
you
know
contribution
to
respect.
You
know
just
by
the
fact
that
I
was
on
and
off,
but
I
feel
it
was
really
amazing
and
yeah.
So
did
my
my
last
question,
which
is
actually
suggestion
is
right?
Do
you
feel
we
should
have
a
second
part
to
this
live
stream
right,
I
want
you
to
quote
no,
no
seriously
man
seriously,
because.
A
A
Okay,
cool
cool
half
of
it,
half
of
it.
You
know
I'm,
so
sorry
about
that.
My
internet
was
shitty
and
I
haven't
I
haven't
turned
my
laptop
off
for
like
a
month
now
close
to
three
weeks,
so
I
thought
everything
was
like
jump
packing
I'm
like
restart
me.
Please,
so
I
have
to
restart
my
laptop
and
stuff.
Let's
do
it
so
so.
A
So
the
next
section
I
would
love
us
to
you
know
technically,
oh
briefly,
we're
gonna
have
these
summary
of
this
first
section.
Then
we're
gonna
go
into
this
contribution
phase
where
we
react,
where
you
like
write
code
or
you
just
maybe
fix
a
good
first
video
or
you
know
just
work
on
a
dummy
proposal
right
when
you
do
to
do
the
implementation
of
the
feature
which
is
not
making
it
out
there
just
for
the
sake
of
for
the
sake
of
the
live
stream.
A
C
B
B
C
A
Use
this
video
as
a
reference,
because
you
don't
know
how,
like
you
said
earlier,
you
you,
you
don't
understand
how
you're
gonna
test
your
spec,
how
to
know
your
changes
is
working
or
stuff
like
that
and
I
feel
using
this
video
as
a
reference,
or
this
recording
as
a
reference
would
help
like
we
go
a
long
way
and
and
I
know
there
are
some
contributors
right
where
they
they
want
to
reach
out
to
you
to
like
contribute
but
and
I
feel,
but
with
tools.
I
expect
that
is
pack
itself
they're
gonna.
A
C
B
I
I
get
the
sentiment,
so
that's
that's
why
I
was
I
was
trying
to
to
motivate
people
right
because
it's
really
a
lack
of
motivation
and
it's
a
fear
of
people.
They
fear
looking
dummy
and
and
it's
a
distant
it's
an
imposter
syndrome.
Always
it's
always
the
same.
So
yeah
like
Let's,
Do,
It
Let's
make
it
a
little
bit
easier.
So
we
can
then
cut
this
video
and
probably
even
put
it
on
the
in
the
into
the
spec
repo
on
the
readme.
So
people
can
can.
B
So
that
so
that
people
can
find
it
there,
right
and
and
or
in
the
contributing
guide,
there
is
a
contributing
document
that
you
shared
on
the
chat.
So
maybe
we
can
put
it
there
as
well,
so
yeah
so
explaining
what
it
looks
like
to
to
contribute
to
to
the
spec
right
and
and
hear
me
out
like
for
many
people
in
the
community,
in
the
specs
Community
right,
not
just
async
API,
but
other
specs
I.
Am
this
kind
of
person
that
I'm?
B
Let's
say
my
way
of
working
is
not
precisely
the
master
academic
one.
So
I
I
like
to
do
things
in
a
pragmatic
way
in
a
practical
way
right,
so
I
prefer
to
do
small
things,
practical,
small
things
and
and
that
I
can
immediately
see
value
right
and
some
other
people
in
other
specs
are
like
in
the
HTTP
spec,
for
instance,
and
I
and
I
understand
like
HTTP,
has
reached
a
point
where
you
need
to
be
really
academic.
B
A
B
Which
is
not
I
mean
it's
not
really
like
that,
because
I
mean
it's
not
really
that
because
it's
it's
another,
it's
another
community.
So
it's
not
it's
not
someone's
fault.
It's
it's
a
it's
a
mistake
that
they
will
all
make
collaboratively.
So
it's
the
same
way
that
you
can
win
together.
You
can
fail
together
as
well,
so
you
actually
fail
together.
B
B
So
so
then
it's
not
just
your
responsibility,
right
and
and
yeah
on
the
and
on
the
community,
let's
say
of
spec
editors,
spec,
writers
and
so
on,
I'm,
not
that
kind
of
academic
super
pulchris
person
trying
to
Oxford
Oxford,
exactly
that's
for
the
English
trying
to
put
things
perfectly,
considering
all
the
cases.
Let
me
study
this
down
and
make
a
huge
document
explaining
why
no,
no,
no,
no,
no,
no
I
prefer
to
be
more
pragmatic
and
I
probably
write
just
a
paragraph
explaining
what
I
want
to
do.
B
If
you
don't
understand
it
or
if
you
think
that
you
need
more
context,
I
will
I
will
add
it,
and
you
still
don't
have
enough.
I
will
add
it.
I
will
add
more
and
like
this,
not
right
in
this
long
documents
explaining
the
current
state
of
event-driven,
architectures
and
I'm
gonna
make
a
research
about
it
and
after
that,
only
after
that
I
will
propose
this
change
in
the
spec,
because
I
need
to
research.
What's
the
current
state
of
even
doing
architectures
and
apis,
no,
no.
C
B
B
What's
your
preferred
way
of
working
right?
That's
it
I,
for
instance,
I
favor,
pragmatism,
I,
favor,
user
experience,
development
experience
above
being
super
academic
and
specific
and
use
it
they're,
using
the
proper
words
in
proper
English
perfectly
described
and
now
wait.
I
mean
I,
try
to
be
good
at
writing
stuff,
but
yeah
I
don't
get
mad
at
it
right.
So
so
yeah.
A
And
I
think
I
think
I'm
gonna
add
something
so
concerning
the
pubs
of
like
concept
right.
One
thing
I
noticed
right,
even
even
despite
the
fact
that
you
get,
you
know
confused,
sometimes
about
what
is
publishing.
What's
subscribing
well,
I
feel
right.
If
you
get
to
understand
this
concept
and
how
they
work
right.
It
also
like
gets
you
thinking
about
how
you
how
what
your
application
is
doing,
right
and
I
understand
like
when
you
say,
publish
I'm,
like
okay,
publish
from
the
word
publish
means,
I'm,
publishing,
right
and
subscribe
means.
A
I'm,
subscribing
and
I
was
watching
one
of
your
live
streams
with
I
think
on
Postman,
YouTube
channel
I
think
it
is
on
this
kpi
channel
right
and
you
you
were
explaining
this
old
publish,
subscribe
concept,
and
it
was
really
interesting
right.
It
was
like
I
was
like
okay.
This
English
isn't
right
like
if
we
had
to
follow
the
English,
like
the
words
I
published,
then
I'm
like
I
think
front
is
not.
What's
he
saying.
B
B
So
the
subject
of
the
of
the
of
the
sentence
is
not
who
you
think
it
is
that's
the
problem
so
self-publish
when
I
say,
publish
you,
you
were
saying,
I,
see,
publish
and
it
means
that
I
can
publish
sure
cool,
but
there's
another
way
of
seeing
things
there,
which
is
if
I
see
publish
it,
means
that
others
can
publish
so
the
sentences.
So
so
the
subject
is
not
I
can
publish.
B
I
said
I
right,
the
subject
is
they
artists
can
published
to
me
right,
so
that
is
so
English
wise
is
is
correct,
but
it's
good
that
you
mentioned,
because
this
is
precisely
when
I
was
starting
to
write
the
spec
on
version
one,
because
this
problem
has
been
in
version
one
already
any
version
two
when
I
was
when
I
was
I.
Was
writing
the
spec
I
precisely
had
that
imposter
syndrome
at
that
time?
B
B
Like
you
know,
I
was
following
their
advice
right,
but
the
problem
is
that
even
experienced
people
can
be
grown
as
well
right
and
that's
something
that
we
don't
realize
and
and
they
can
be
wrong
and
the
more
senior
not
the
more,
but
usually
the
more
experience
that
you
become
the
harder.
It
is
to
change
your
point
of
view
on
something
right,
because
you
think
you're
right
because
you've
been
doing
this
forever
right.
So
so,
how
are
you
gonna
be
grown
right
or
not
completely
right,
at
least
so?
B
What
happened
is-
and
it
happened,
for
instance,
in
the
past,
with
react-
you're,
probably
too
young
in
the
space.
But
when
react
was
introduced
and
when
react
was
introduced
to
the
community
and
and
it
was
announced
and
everything
the
whole
the
whole
way
of
mixing
HTML
with
JavaScript
and
so
on.
That
was
completely
forbidden
that
was
like
there
was
a.
There
was
a
best
practice
that
was
unavoidable.
B
That
was
saying
like
never
never
ever
mix
HTML
and
JavaScript
in
the
same
place,
because
it's
a
mistake
categorically,
it's
a
mistake,
and
we
were
all
all
of
us
living
by
this
we're
living
by
this
best
practice.
Don't
break
this
practice
because
it's
true
right
well,
the
react
faults
prove
us
wrong
right
like
well.
There
is
a
way
to
do
this
in
a
different,
different
way.
B
So
so
what
what
we
were
trying
to
do
is
trying
to
mimic
or
trying
to
how
can
I
say
like
we
were
trying
to
extend
HTML
tax
to
do
loops
and
things
like
this
and
ifs,
and
things
like
this
and
things
that
you
have
in
a
programming
language
in
a
real
programming
language
right,
so
so
that
you
can
embed
a
piece
of
a
script.
But
the
four
is
actually
an
HTML
tag
and
so
on.
So
it's
not
that
it's
wrong,
but
it's
it's
limited.
B
C
B
Good
for
the
for
the
for
the
case,
but
the
react
Falls
came
in
and
say
like
no
wait,
I'm
not
proposing
that
I'm
proposing
that
you
write
the
Javascript
file,
not
an
HTML
file.
You
get
the
Javascript
file
and
it's
gonna.
Let
you
return
kinda
HTML,
it's
not
HTML
precise,
but
it
looks
a
lot
like
HTML,
so
you
can
return
HTML
right
and
so
because
JavaScript
doesn't
support
that.
We
will
need
to
build
some
kind
of
tool
that
will
translate
this
into
proper
JavaScript,
because
HTML
is
not
allowed
in
JavaScript
right.
B
B
Here
we
are
it's
the
number
one
framework
and
it's
and
I'm
not
freaking
in
love
with
it.
It's
like
it's
kind
of
standard
and
I'm
freaking
love
with
that
with
jsx
and
and
not
just
with
react,
but
with
jsx
right
so
embedding
HTML
into
the
Javascript
file.
That
sounds
now.
That
makes
sense,
but
they
were
like
they
were
Brave
and
said,
like
no
I,
don't
care
about
the
best
practice
and
actually
yeah
the
best
practice
says
that,
but
what
we're
trying
to
do
is
is
doing
this,
but
in
a
different
way.
So
so
what?
B
When
I
was
starting
to
ride
the
spec?
The
version
one
and
trying
to
make
it
stable,
I
was
surrounded
by
a
lot
of
people
like
this
telling
me
like,
what's
the
best
practice
for
apis
and
for
interfaces
and
defining
interfaces.
Defining
things
like
this
and
and
I
want
to
say
this
clearly
like
they
were
not
doing
it
in
a
in
a
with
bad
intentions
or
anything,
but
they
were
telling
me
many
times
like
the
way
you
should
do.
This
is
like
it's
it's
wrong
that
you
define
the
application.
B
You
should
be
defining
the
the
the
interface
so
the
way
people
interact
with
your
API,
so
pretty
much.
It's
like
what
open
API
does
open
API
for
graphql
or
whatever
so
cool
yeah
makes
sense
and
I
did
it
like
this,
but
I
was
even
though
I
did
it
like.
This
I
was
feeling
like
there's
something
wrong
with
this
approach,
because
it's
confusing
me
every
time
right
and
and
then
I
realized
that
okay,
it
makes
sense
when
the
architecture
is
client
server.
B
B
B
B
B
So
that's.
Why
published
subscribers
defined
at
that,
because
by
academic
definition,
let's
say
or
by
being
like
pure
in
terms
of
yeah,
you
got
to
be
pure
because
you're
going
to
be
a
a
real
software
engineer
and
you
have
to
do
things
properly
by
the
best
practices
and
so
on
right.
You
should
be
defining
an
interface
and
that's
what
I
did
and
that
failed
miserably
right
that
failed
miserably
right.
It's
true,
like
everyone
finds
it
confusing
everyone,
because
it
is
because
it's
confusing
it
might
be
right.
B
A
B
B
Is
it
really
like?
You
can
be
academic,
sometimes,
and
that's
cool,
that's
useful,
but
in
some
in
some
cases
for
version
three
now
we're
breaking
this
best
practice
completely
we're
breaking
it
like
we're,
not
gonna,
We're,
Not,
Gonna
Define,
the
interface
as
it's
supposed
to
be
like,
like
you,
define
the
interface
of
your
service
and
publish,
will
mean
what
others
can
do
to
you
and
subscribe
with
me.
What
others
can
do
to
you?
No,
no,
not
anymore.
We
actually
changed
the
name
of
publishing
subscribers
and
then
request
reply
to
to
a.
B
B
So
we
changed
it,
we
changed
it
for
two
reasons,
but
one
of
them
is
to
differentiate
from
thousands
and
subscribers,
so
people
don't
get
confused
and
they
actually
notice
that
there
has
been
a
change,
and
so
they
have
to
go
to
the
spec
and
look
what's
the
new
meaning,
because
if
you
keep
using
publish
And
subscribe
and
you
are
already
used
to
publishing
subscribe
from
version
two,
you
might
think
this
is
the
same
thing
this.
This
hasn't
changed.
B
No,
it
has
changed
and
that's
why
we
changed
the
name
as
well,
so
that
you
we
forced
you
to
go
to
the
spec
and
learn
the
new
meaning
right.
So
in
this
news,
spec
in
version
three
send
is
the
same
as
published,
but
the
published
that
you
were
understanding
in
the
beginning
or
defining
in
the
beginning,
which
is
I,
am
sending
the
information.
I
am
sending
the
message
to
the
broker.
I
am
receiving
it
from
the
broker.
B
That
is
so
that
is
so
that
whole
confusion
is
solved
right,
but
now
the
purists
will
come
to
you
right
and
because
it
already
happened
right
a
few
times
the
purists
will
the
academics
will
come
to
you
inside.
This
is
plainly
wrong.
That's
not
an
API!
That's
not
an
interface
definition!
That's
not
well
I'm!
B
Sorry
man,
then
I,
don't
care
it's
more
useful,
so
you
don't
want
to
call
it
an
API,
don't
call
it
an
API
I,
don't
care
who
said
that
we
should
be
doing
sticking
to
the
typical
or
proper
bio
academic
rules,
API
definition.
Nobody
said
that
right.
Nobody
said
that
we
need
to
be
building
things
that
are
useful
for
the
community,
not
for
the
academic
definitions
right.
So
it's
the
other
way
around.
So
definitions
will
be
serving
the
people,
not
people
serving
the
definitions
right.
B
So
that's
what
it
is
now
like.
It's
a
it's
still
an
interface
definition,
but
it's
not
the
way
we
are
accustomed
to
that's
the
thing.
It's
the
other
way
around.
It's
probably
kinda
like
Behavior
definition,
because
you're
defining
the
behavior
of
your
application.
Your
application
is
sending
or
is
subscribing
or
receiving.
A
B
You
know,
but
it's
a
very,
not
simple,
it's
a
very
simplistic
programming
language.
It's
like
saying:
please
send
this
message
to
the
broker,
so
you
it's
been
imperative
right,
so
it's
not
declarative.
It's
imperative
now
so
you're
saying
what
your
application
has
to
do,
instead
of
what
it
might
accept
right.
So
it
is,
it
is
more
imperative
now
cool.
B
We
found
it
to
be
after
testing
it
and
after
discussing
it
for
a
long
time,
we
found
out
that
that
actually
makes
sense
with
a
few
more
changes
around
the
spec
to
actually
make
it
more
make
it
make
sense.
But
but
that's
how
we
we.
We
came
up
with
this
decision
and
it's
breaking
the
the
the
academic
definition
of
or
the
best
practices
of
how
things
will
be
done,
and
it's
all
all
of
this
is
coming
to
or
the
reason
I
was
explaining.
B
B
B
After
more
than
a
year
now,
we
haven't
seen
any
problems
and
nobody
has
realized
about
any
problems,
and
everyone
who
was
coming
to
us
saying
like
this
is
plainly
grown.
This
is
this:
is
the
not
the
way
it's
supposed
to
be?
It
was
just
because
it
was
not
their
preference,
not
because
it
wasn't
wrong
per
se.
It's
just
it's
just
because
it
wasn't
their
preference
or
it's
because
it's
not
it's
not
matching
their
expected
definition
of
of
an
API
or
an
interface
Okay.
B
So
worst
case
scenario
here
is
that
now
it's
their
turn
to
be
frustrated
by
the
meaning
for
a
few
years,
and
then
we
change
it
again
back
a
few
more
years
and
then
it's
like
we
may
get.
We
make
it
fair.
We
make
it
good
for
some
people
for
some
group
of
people.
Then
we
change
it
back
to
this,
and
now
we
favor
these
people.
A
Nice,
nice,
that
was,
that,
was
an
interesting
breakdown
there.
We
got
so
serious
for
a
few
minutes
for
a
couple
of
minutes
actually
and
I'm
pretty
sure.
Whoever
is
without
the
focus
I'll
be
watching
this
recording
later
and
they
got
to
these
points
they're
gonna
be
like.
Are
they
still
talking
about
contribution
to
respect?
B
Yes,
so
what
I'm
trying
to
say
here
is
that
don't
fear
contributing
to
the
spec?
Just
because
you
don't
know
something
or
you
don't
know
anything
about
it
like
who
cares
even
people
who
think
they
know
what
they're
doing?
Most?
Probably
they
don't
so
so
yeah
and
I
can
tell
you,
like
the
more
I
grow
in
my
career,
the
more
I
get
to
meet
people
in
high
positions
and
the
more
I
realize
that
they
have
no
idea
what
they're
doing
so.
B
Whatever
the
more
you
see
these
people,
the
more
you
realize
they
have
no
idea
they're,
just
for
some
reason,
they're
good
at
communicating
and
at
convincing
you
that
this
will
be
the
ones
who
are
leading
the
team
and
and
that's
it,
but
they're
really
not
good
at
engineering
at
all.
Of
course,
this.
This
is
not
the
norm.
I'm
saying
that
you,
the
more
you
find
these
people,
that's
what
I'm
saying
so
so
you
buy
one.
You
probably
might
be
looking
at
these
people
thinking.
This
is
director
of
engineering.
He
must
be
really
good.
B
A
Nice
this
this
has
been
an
interesting
session
front.
Oh
man
I
really
appreciate
you
honoring
this
call
and
you
actually
Rock
On
Stage.
You
know,
I
was
offline
for
a
few
minutes
and
you're
like
keeping
it
rolling
I'm
like
yo,
Best,
Best,
Host
ever
and
I'm
like
yeah,
because
you
also
have
your
own
live
stream
and
thinking
out
loud.
So
it's
probably
your
thing.
You
know
how
to
do
it
so
and
you've
been
you've
been
doing
community
meetings
like
back
then
before
workers
took
over
right
so.
C
B
Yeah
actually
yeah
I
was
I
was
so
I
was
tired.
I
was
tired
of
doing
community
meetings
because
I
got
tired
of
it.
I
was
so
tired
that
the
very
first
meeting
that
Lucas
joined
has
already
working
for
me
because
at
the
time
he
was
working
for
me
for
a
friend
not
for
racing
kpio
for
or
for
possible
the
very
the
very
first
moment
he
he
joined.
He
was
working
on
the
async,
API
and,
and
he
joined
the
meeting.
I
was
like
okay,
you
take
it
from
here.
C
B
I
mean
he
was
he
he
was
in
the
previous
meetings
as
a
as
a
community
member
for
probably
months
already.
So
so
he
knew
what
what
it
was
like,
and
it
was
just
a
few
of
us
showing
up
probably
two
or
three
people
at
most,
so
so
yeah
and
it
was
all
like
it
was
all
friends
chatting
and
that's
it
so
so
I
was
like
okay,
I'm,
tired,
I'm,
tired,
because
I
have
to
run
these
meetings
and
I
have
to
I
have
to
code.
The
tools
I
have
to
do
everything
else.
B
So
so
yeah
so
and
actually
paying
him
and
my
wife,
because
my
wife
was
at
the
time,
hits
he
was
helping
with
the
videos
and
and
the
conference
and
so
on.
So
so
I
I
needed
to
find
a
way
to
to
actually
organize
this
whole
thing
and
find
money
so
so
yeah
so
I
was
like
what
I
was
saying
is
I
was
so
tired
that
it
was
like
I'm
not
showing
up
in
a
few
months,
probably
on
the
community
meetings.
I,
don't
care
like
I.
Don't
you
take
it
from
here?
B
B
A
B
A
C
A
I
think
we're
way
above
we
are
way
past
way
way
way
above
time,
so
I
guess
we
have
to
like
end
this
live
stream.
Oh
thanks
for
joining
this
call
front
and
I
guess
we
have
we
eventually
going
to
do
a
part
two
of
this
live
stream
right
so
in
the
second
part,
we're
going
to
be.
Writing
calls,
let's
talking
more
coding,
so
no
more
motivational
speech
for
France,
so
we
just
code
in
okay,
so
we're
gonna
have
the
second
part
of
this
live
stream.
So
just
keep
I'll.
A
Keep
you
updated
on
the
community
channel
on
slack,
so
without
no
further
Ado
I
guess
this
is
the
end
of
the
call
of
today's
live
stream.
Thanks
for
Jennifer,
it's
me:
Ace
I'm,
only
I
love
Austin
live
streams,
even
though
sometimes
I
get
off.
Sometimes
this
network,
so
I
live
in
a
shitty
country.
So
so.