►
Description
AsyncAPI Conference 2022 - Day 2
4th November 2022
Abir will be sharing his journey from a contributor to a TSC Member at AsyncAPI. The talk will be help new contributors to get started with contributing to AsyncAPI. He will also share about the project AsyncAPI Problem Interface, which is used across the AsyncAPI organisation for handling errors in the tools like AsyncAPI Server, AsyncAPI parser, etc.
A
Hello,
I'm
abhir,
a
friend
and
software
engineer
at
Serta
and
a
computer
science
graduate
from
2022
batch
I'm,
also
one
of
the
mentees
at
async
API
mentorship
program
2022..
Today,
I'm
really
excited
to
present
my
journey
from
a
contributor
to
an
incoming
TSC
member
at
casing
repair.
So,
let's
get
started
so
it
was
back
in
early
2020
when
sovik
and
we
were
exploring
open
source
and
trying
to
learn
things
like
which
are
not
usually
taught
in
any
traditional
educational
institutions,
so
we're
exploring
about
how
to
build
websocket.
A
Because
that
time
we
were
building
a
chat
application
and
we
were
quite
curious
about
the
technology
behind
web
sockets
and
how
it
works,
how
the
sending
events
and
how
the
receiving
events,
how
it
completely
works
so
that,
with
the
global
search
on
GitHub
trying
to
search
about
different
organizations,
remember
we
searched
on
GitHub,
not
on
Google,
so
we
searched
on
GitHub
and
that's
how
we
landed
on
async
async
API,
and
that
sounds
like
we
started
exploring
it
out.
So
initially
it
was
the
logo
that
to
catch
me
out.
A
Okay,
this
is
something
interesting,
looks
interesting
and
let's
explore
this
out.
So,
as
you
got
to
know
more
about
the
open
source
culture,
we
were
really
impressed
by
it.
Okay,
this
is
where
I
want
to
be
part
of
so
there's.
The
decision
was
taken
that
let's
be
part
of
facing
API
and
we
will
never
miss
any
GitHub
discussion
or
anything
around
racing.
Api,
that's
happening
in
the
organization,
so
with
certainly
with
time
pass.
We
explore
different
things.
It
took
us
time
to
know
the
things
for
me.
A
It
was
around
like
six
months
to
know
about
what
is
the
specification
file,
how
it
works,
how
bundler
works
so
many
things,
it's
not
just
just
putting
up
the
time.
It's
just
about
learning
things.
Then
the
searching
a
lot
of
things
was
going
on
side
by
side.
So
with
this
we
got
a
finally
a
project
known
as
async
API
CLI.
A
So
when
this
over,
the
MVP
was
ready,
we
thought
about
building
out
the
like
missing
features
for
CLI
and
I
took
the
responsibility
for
building
out
some
recent
features
for
CLI,
for
example,
build
a
spec
Watcher,
so
a
spec
Watcher
is
a
flag
which
actually
runs
on
any
commands
existing
commands
or
any
upcoming
future
commands
in
the
async
API
CLI.
So
it's
a
flag.
The
crow
responsibility
was
to
enhance
the
developer
experience
of
the
CLI,
where
one
can
check
about
real-time
validations
or
whatever
the
command
that
has
been
run.
A
Suppose
you
have
a
spec
file
and
you
change
it
to
something,
and
you
want
to.
You
have
to
rerun
the
command
again
to
know
the.
What
are
the
changes
that
has
been
done
and
what
is
the?
Is
there?
A
new
change
working
or
not
so
this
real-time
flag
or
watching
flag?
Helped
me
to
you
know,
help
to
run
the
validations
or
it
can
be
any
any
such
command
in
a
real-time
wizard.
Okay,
if
you
have
changed
anything,
it
will
notice
the
change
okay.
This
has
not.
This
has
been
changed,
let's
run
the
validation
again.
A
This
can
be
optimized
in
more
fashioned
way
like
we
can
have
more
kind
of
optimizations
in
this.
That's
our
the
future
task,
but
that's
how
the
whole
spec
Watcher
flag
started,
and
during
that
time,
I
was
completely
new
to
the
things
about
CLI.
How
things
work
and
I
took
a
chance.
There
is
to
know
the
things,
because
this
was
going
to
be
used
by
tons
of
users
of
async
API,
so
that
was
the
main
reason
that
I
was
a
bit
nervous.
A
Also,
but
yes,
I
want
to
thank
matcha
Urban
set
for
his
timely
reviews
and
on
the
spec
Watcher
PR.
He
has
been
a
great
mentor
for
me,
has
been
guiding
me
on
how
to
design
code
and
how
to
write
a
beautiful
product
which
can
run
on
millions
of
users.
So
that's
how,
like
the
things,
you
need
a
great
mentor
to
be
a
great
engineer.
A
A
We
had
different
number
of
async
API
tools,
so
what
we
wanted
to
do
was
have
a
common
error
interface
for
all
of
them,
because
right
now,
whatever
what
we
are,
having
is
suppose
we
have
a
password,
API
and
password
API
is
having
his
own
error
interface
like
to
manage
all
the
errors
in
the
password
and
whereas
server
API
is
also
having
its
own
interface
for
managing.
Even
the
CLI
also
has
its
own.
Even
the
generator
also
has
the
same
different
interface.
A
So
we
have
different,
like
the
responsibility
of
the
code,
is
same
to
manage
the
errors,
but
we
are
using
it
in
two
different
ways.
So
why
not
have
a
common
error
interface
known
as
facing
API
problem?
And
let's
try
to
solve
this,
so
this
was
the
gist
of
the
problem
that
we
wanted
to
solve.
So
we
discussed
it
and
I
got
to
know
that
after
discussing
it,
it
plays
a
really
vital
role
in
software
development
life
cycle.
A
It
organization
needed
one
such
tool
because,
as
we
scale
and
as
we
grow,
the
community
grows,
we
have
tons
of
developers
working
out
right.
So
there
should
be
something
that
is
very
like
centralized,
like
especially
the
error
interfaces,
so
it's
easy
to
debug
whenever
something
happens
and
any
incident
occurs.
So
it
also
helps
to
do
the
root
cause
analysis
for
any
incidents
in
shortest
time
as
possible.
A
So
I
know,
I
was
waiting
for
the
mentorship
applications
when
it
will
start,
and
we
are
continuously
discussing
how
I
will
progress
about
it
and
what
are
the
different
structures
in
the
issue
itself
in
the
issue
comments,
so
the
voting
happened
for
the
ideas
and
our
idea
was
in
so
you
can
see
that
we
were
happy
here
that
our
idea
is
in
and
I
was
a
mentee
at
async
API.
So
it
was
like
quite
hard
to
give
it
a
creative
name
for
the
whole
repository.
A
So
for
now
we
decided
to
give
it
a
very
simple
and
self-explanatory
name:
async
API
problem
repository,
it's
in
my
personal
GitHub.
It's
public
only
Metro
and
me
are
building
it
out,
and
we
will
be
discussing
more
about
this
in
the
get
up
in
the
February
month
about
how
to
integrate
it
with
different
tools,
and
it
will
be
ready
for
different
tools,
integration,
so
addressing
API.
One
thing
I
have
realized.
Is
it's
really
important
to
maintain
the
tools
and
improve
them
with
type?
A
Hence
we
decided
to
make
this
error
interface
as
a
pluggable
error
interface,
which
can
be
used
across
the
organization.
So
that's
where
the
main
idea
that
building
something
which
is
impacting
whole
organization
in
a
positive
way
and
also
it
will
reduce
the
time
for
a
developer
to
find
rcas
or
anything
like
that.
So
where
the
problem
repository
will
impact
initial
features
like
of
this
error,
interface
will
be
incrementally
added
to
Parcels
repository
server,
repository
async,
API,
CLI
and
Generator
like
in
the
whole
application.
A
Even
if
you
want
to
have
only
your
own
project,
you
can
use
that
error
interface
own
project
in
the
sense
of
async
related
to
async
API,
and
it
will
be
done
effectively
by
q1
of
2023
and
I
also
want
to
thank
my
project
Mentor
again.
Matthew
for
helping
me
out
to
think
about
the
box
and
build
software
that
serve
the
need
of
your
surroundings
right.
A
So
that's
what
I
learned
from
this
whole
mentorship
and
my
journey
and
that's
how
my
journey
started
and
still
going
on
with
this
problem,
repository
merging
to
async
API
I'll
be
holding
one
of
the
four
responsibilities
in
the
world
of
Open
Source,
that
is
being
a
TSC
member
at
an
organization.
So
that's
something
I'm
really
excited
about,
and
this
will
be
a
major
contribution
to
the
world
of
Open,
Source
and
event
driven
architectures.
So
once
again,
thank
you,
everyone
for
having
the
session
and
thank
you
so
much.