►
From YouTube: Community Standup: 12/10/19
Description
Community Standup: Dec 10, 2019
A
A
B
You
you
looked
at
the
code
more
recently
than
I
have
and
I'm
pretty
sure
what
we
do
is
we
just
pull
everything
together
and
in
like
a
big
counter,
and
that
doesn't
let
us
do
a
lot
of
filtering
uh-huh
and
what
I
would
like
to
what
I
would
like
to
do?
Actually
at
you
know,
in
terms
of
the
production
and
every
lab
site,
I'd
like
to
get
to
a
point
where
we
can
actually
publish
the
in
flux,
DB
instance
publicly,
and
let
people
just
run
their
own
queries
right
now.
B
B
B
C
B
B
C
I'm
so
another
question
so
yeah
for
it
like
next
task
like
is
there
so
I
can
also
like
look
into
the
Python
code
like
work
on
the
Python
code.
Is
there
like
higher
priority
tasks
like
are
there
more
prior
for
any
tax
on
the
annual
ops
or
the
NRI
curriculum,
or
which
one
would
you
guys
have
like
more
resource
on
over
yeah.
B
B
Okay,
well,
we
there's
not
really
there's
there's
little
bits
of
Python
here
and
there
I
think
there's
there's
parts
like
in
the
platform
in
terms
of
like
the
configurator
image,
if
you
want
to
look
at
that,
but
the
curriculum
always
needs
more
stuff.
If
you
have
experience
with
like,
if
you
have
experience
with
a
particular
tool
or
whatever
there's
there's
always,
there's
always
work
to
be
done
on
the
curriculum
for
sure
it.
B
Also
broken
lessons,
as
Olivier
pointed
out
recently
and
as
we've
pointed
out
over
the
last
few
weeks,
there
are
some
lessons
that
just
simply
don't
work
right
now,
Macie
and
and
and
that
could
always
use
more
attention,
so
I
would
say
if
you
want
to
get
involved
the
curriculum.
That's
probably
that's,
probably
a
good
good
thing
to
do
as
well.
Okay,
okay,
cool,
there's
issues
there.
You
can
of
course
look
at
the
site
live
and
see.
B
C
B
But
Derek's
by
the
way
and
I'm,
Anna
and
I
looked
at
the
the
forum
site.
I,
don't
think
we
have
a
really
formal
agenda
for
today,
other
than
open
discussion.
I
can,
of
course,
if
you,
if
anybody,
has
any
follow-up
from
last
week's
agenda,
I
know
that
a
lot
of
the
stuff
that
we
dumped
on
everybody
last
week
was
basically
read
this,
and
let
us
know
what
you
think.
A
A
Matt
and
I
are
actually
in
a
hotel
room.
We
we
have
one
of
those
bi-level
shared
residents
in
rooms
in
California
and
I.
I
woke
up
precisely
nine
minutes
ago,
at
8:01
a.m.
so
I
must
I
want
to
apologize
for
that.
My
I
just
I,
slept
because
I'm
in
a
different
time
zone
and
I
just
want
to
say
that
Matt
is
an
angel
for
for
a
roommate.
A
A
B
D
I'm
on
the
professional
services
side,
as
some
more
more
on
the
consulting
side,
I,
don't
know
what
I
can
can
say
and
can't
say
right
now,
so
I'll
stick
with
that
sure
cool
I,
like
the
new
dock
site,
yeah
I,
haven't
seen.
If
there's
been
any
changes
over
the
last
week,
but
last
week
when
reviewing
it,
it
seemed
to
flow
a
lot
better
and
I
like
the
new
view
of
the
side
and
yeah.
D
B
B
They
said
you
know
it's,
you
know,
I
I,
don't
really
know
where
to
you
know
where,
on
the
docks
I'm
supposed
to
be
right
now
and
I
struck
me
as
odd
I'm,
like
I,
don't
know
it's
a
reference
we'll
be
talking
about,
but
anyway,
I
think
adding
editing
making
it
more.
Chronological
does
make
sense
in
this
case
and
I
think
that
that's
helped.
B
You
know
the
the
sort
of
the
review
process,
the
release
process,
all
kinds
of
stuff
like
that
I
think
that
that's
helpful.
Does
everybody
generally
agree
that
that
having
a
separate
entry
labs
documentation
site
is
is
useful
because
we'll
still
have
the
antidote,
Docs
and
I
want
to
make
sure
that
that's
not
like
overly
cumbersome
to
have
two
separate
doc
sites,
even
though
we'll
obviously
we'll
have
links
to
each
other
like
in
the
in
the
current
area,
labs
doc
site,
there's,
actually
a
link
in
the
you
know,
first
level
navigation.
B
D
B
Okay,
cool
yeah,
I
I
do
I
actually
like
the
idea
about
moving
that
to
get
booked
eventually
to
right
now,
basically
I'm
afraid
to
do
much
with
the
docs
on
the
antidote
side.
Just
because
of
fp1
everyone
is
gonna
kind
of
throw
everything
out.
Almost
almost
almost
and
so
I
think
I
think
one
one
thing
that
I'll
do
is
once
the
bulk
of
the
changes
are
complete
or
nearing
complete.
B
Actually,
let
me
I
think
if
there's
interest
seconds
I
can
just
show
briefly
how
that's
going
if
anybody's
interested
in
MP
one
I
think
it
probably
would
be
a
good
idea
for
me
to
give
a
brief
update
on
on
how
that's
doing.
Let
me
get
out
my
laptop.
Give
me
like
a
minute
or
two
and
I
can
show
that
if
there's
interest,
sure
okay.
A
We're
also,
we
have
a
roadmap
that
we
started
putting
together
yesterday.
That's
like
more
I,
guess,
holistic,
I,
don't
know.
The
very
word
is,
but
in
every
aspect
of
the
project,
because
we
have
to
deliver
on
that
anyways,
you
know
so
that
our
company
keeps
sponsoring
it
and
lets
them
and
continues
to
let
us
working
on
it
work
on
it.
So
we
should
have
that
posted
soon.
C
A
And
so
actually
before
Matt
starts
sharing,
if
there's,
if
you,
if
you
want
to
you,
can
either
edit
this
stand-up
post
on
our
community
site
or
maybe
start
a
new
one
that
doesn't
really
matter.
But
if
there's
things
you'd
like
to
see
on
the
roadmap,
you
know,
please,
please,
you
know,
make
a
post
about
it
and
this
and
please
keep
them
all
on
the
same
post.
A
If
and
it's,
and
if
you
could
because
I
know
people
are
in
you
know,
everyone
has
an
interest
in
the
outcome
and
the
project
divide
them
up
into
things
that
you'd
like
to
see
happen
and
things
that
you
might
be
able
to
work
on
yourself.
That
would
be.
That
would
be
good.
You
know
what
long
Wow
seems:
yeah
I'm,
gonna
I'm.
B
Gonna
make
it
posts,
and
also
is
it
does
David
specifically
on
it.
I
mean
it
outside
of
things.
Please
just
post
that
to
the
mp1
pull
requests,
if
it's
higher
level
de
Malaga,
it's
in
the
curriculum
or
they're
broadly,
where
you
want
the
project
to
go,
then
go
ahead
and
and
comment
on
Derek's
post.
That
way.
We
keep
things
where
they
you
know
were
they
most
relevant.
B
The
work
I'm
about
to
show
you
is
is
in
a
poor
quest
called
database
package,
hi
Johannes
there.
You
are
over
the
last
database
package,
so
this
was
this
is
the
first
milestone
in
mp1
and
it
was
more
or
less
one
of
the
least
I
guess
the
least
potentially
controversial.
You
know
subjects
with
an
empty
one.
Everybody
kind
of
agrees
that
there
needs
to
be
a
database
package,
the
way
that
it's
implemented.
It's
just
going
to
take
a
few
weeks.
B
It's
just
letting
out
the
functions
and
the
types
that
I
want
in
the
way
that
I
want,
and
we
can.
You
can
certainly
make
different
decisions
if
we
absolutely
need
to
so
I
know
means.
Does
this
mean
there's
you
know
that
the
Train
is
less
the
station.
It's
just
I
wanted
to
get
started
because
there's
there's
a
few
other
pieces
of
the
project
that
are
actually
waiting
on
this
work.
To
finish,
and
so
as
a
result,
I
think
it's
important
to
at
least
start
it.
B
So
that's
what
that's
what
I've
done
plenty
of
work
left
to
do,
but
the
way
the
way
that
this
is
working
out
at
the
moment
is
in
the
new
and
you'll
notice.
I
haven't
renamed
syringe
yet
so
that'll
still
happened,
I
don't
know
when
maybe
before
I
merge,
this
I
don't
know.
I
haven't
thought
through
exactly
what
I
want
to
do
that,
but
that's
happening
we'll
have
to
figure
out
when
that
happens,
but
you
notice
I
created
a
new
directory
DB.
This
didn't
exist
before
so
this
is
a
net
new
code.
B
That's
one
of
the
cool
things
about
this
is,
since
nothing
is
depending
on
this
I'm
actually
taking
my
time-
and
you
know
thinking
through
exactly
how
all
of
this
should
work,
including
the
way
that
lessons
are
defined
because
those
are
modeled
here
and
and
all
of
that
and
it's
actually
been
really
it's.
It's
been
a
really
useful
experience,
because
I
can
I
can
make
sure
that
everything
is
well
tested.
B
Not
all
of
syringe
has
a
really
good
test
coverage,
unfortunately,
but
because
the
DB
package
is
met,
new
and
I
have
the
opportunity
to
effectively
start
from
scratch
and
build
it.
The
right
way,
I'm
making
a
point
to
do
that.
So
I'm
actually
pretty
excited
about
the
database
package.
It's
gonna,
be
it's
gonna,
be
a
pretty
pretty
decently
laid
out.
You
know
piece
of
code
because
I've
got
the.
You
know
you're,
basically,
two
years
of
history,
on
syringe
to
inform
the
decisions
that
I
make,
which
is
which
is
nice
inside
the
database
package.
B
You've
got
models,
so
these
are
effectively
go
structs
for
any
any
piece
of
effectively
any
model
that
we
need
to
make
use
of
within
syringe
or
I
guess
antidote.
Please
call
me
out
if
I
keep
using
that
term
shouldn't
a
good
example
is
lesson
so
we've
got
sort
of
source
models,
any
any
resource
that
you
pull
from
the
file
system.
As
you
can
imagine,
a
lesson
and
current
collection
are
both
resource
definitions,
because
those
are
those
are
things
that
you
pull
from.
B
You'll
find
some
two
DS
every
once
in
a
while,
and
it's
pretty
normal,
but
what's
really
cool
is
inside
of
each
ghost
struts
you.
These
are
effectively
the
go
struts
that
I
actually
ripped
these
from
the
existing
protobufs
generated
code,
because
previously
what
we
did
is
we
had
in
the
old
API
package.
We
had
protobuf
definitions,
you
see
less
than
that
proto,
and
you
see
these.
These
messages
that
were
defined
here.
B
The
protobuf
generator,
would
generate
that
code
and
effectively
result
in
this
struct.
So
really
what
I
did
was
I
just
started
with
this
code,
because
it's
pretty
it
you
know
it
started.
It
started
in
a
pretty
good
place.
It
just
has
a
bunch
of
protobuf
stuff
attached
to
it.
I
took
that
and
I
migrated
it
to
its
own,
not
an
auto-generated
code
here
in
Lesson
dot,
though,
and
then
I
ripped
off
all
I
ripped
out
all
of
the
protobuf
references.
B
B
That
sort
of
describe
the
the
provide
additional
context
on
that
property,
and
you
can
access
these
properties
using
reflection
within
go
and
a
lot
of
projects
do
that
so,
for
instance,
the
the
the
Postgres
driver
that
we're
using
uses
reflection
to
access
keys
like
SQL
or
PG
and
and
those
those
keys
add
additional
context
on
things
like
oh
yeah.
We
want
this
field
to
be
the
primary
key
for
this
table
and
by
the
way,
this
this
lesson
struct
becomes
its
own
table
in
in
the
database,
and
so
that's
how
this
is
laid
out.
B
You'll,
most
you'll
notice
also
that
there
are
JSON
schema
references
I'm
this
in
the
mp1
design.
Doc,
I'm
actually
very
excited
about
this,
because
JSON
schema
will
be
useful
for
us
in
two
ways
when
we
ingest
data
from
the
file
system.
When
you
look
say
when
we
ingest
lesson,
definitions
into
the
database
it'll
be
useful
just
to
validate
that
certain
things
are
in
the
right
place
like,
for
instance,
we
have
a
JSON
schema
pattern
here,
not
for
all
fields,
but
for
some
fields,
for
instance,
the
metier
field
needs
to
be
local,
PTR
or
prod.
B
Well,
we
can
just
put
a
regex
there
in
the
json
schema
tags
and
when
we
validate
the
lesson,
it'll
automatically
say
hey.
This
field
is
not
within
the
expected
pattern,
and
so
this
straight-up
rejected.
So
we
don't
have
to
do
anything
like
you
know,
setting
up
our
own
enum
checkers
and
all
that
stuff.
We
just
define
it
in
JSON
schema
and
it's
there.
The
other
cool
thing
about
that
is.
We
can
use
the
full
JSON
schema
document
to
iterate
over
the
available
fields.
B
B
Okay,
so
this
is.
This
is
working
you'll
also
notice,
I
created
a
new
antidote
command,
so
s
where
fctl
still
exists,
but
obviously
that
whole
name
is
going
away
so
rather
than
modify
syr
CTL
I'm
just
building
a
new
command
line
tool
called
antidote
and
you'll.
See
that
there's
antidote,
import
and
there's
also
antidote
lesson.
Is
the
database
running
note?
The
databases
I
have
a
little
cheat
sheet
connected
right
here.
B
B
B
B
B
B
So
when
you
run
a
create
command,
if
you
say
edit,
a
lesson
create
it's
gonna,
say:
okay,
I'm
gonna,
look
at
the
full
JSON
schema
document
for
the
type
lesson
and
what
I'm
gonna
do
is
I'm,
going
to
iterate
over
all
of
the
fields
and
prompt
the
user
to
provide
a
value
for
them.
I'm
gonna
create
a
new
instance
of
this
of
this
type
and
I'm
gonna
and
I'm
gonna
go
over
all
the
fields
and
prompt
the
user
for
their
values
and
and
the
user
will
type
them
in.
B
B
Please
provide
input,
value
for
lesson,
name
so
test
lesson
and
so
on
and
so
forth,
and
that
means
the
yeah
I
need
to
encapsulate
that
better
anyway,
that's
the
kind
of
experience
that
we
can
get
now,
because
we
have
all
of
the
Tal
the
fields
that
are
in
a
specific
lesson
type,
as
well
as
the
constraints
around
those
fields
like
it
should
be
this.
It
should
be
a
string.
It
should
be
no
longer
than
you
know
these
many
characters.
It
should
fall
under
one
of
these
particular
values
and
read
in
a
regular
expression
pattern.
B
All
that
stuff's
in
the
json
schema
decorating
each
of
these
type
fields,
and
because
of
that
we
can,
we
can
do
some
really
cool
tooling
around
creating
lessons.
I
think.
That's
mostly,
I
I
think
that's
really
useful,
because
right
now,
the
way
that
you
create
lessons
is
effectively
copying
an
existing
lesson
and
tweaking
it
which,
which
is
actually
not
ideal.
It
sounds
it
sounds
doable.
It
is
doable,
it's
a
passable
way
of
doing
things,
but
you
actually
end
up
not
taking
advantage
of
most
of
the
features
of
the
nno
platform.
B
If
you
do
that,
because
what
if
the
lesson
you
copied
from
also
doesn't
take
advantage
of
any
of
many
of
the
features,
so
this
creation
wizard,
I
think,
will
help
folks
understand
what
antidote
can
offer
and
see.
Oh,
my
gosh
there's
there's
so
much
more
than
I
didn't
know
about,
because
now
I'm
following
the
official
sort
of
creation
wizard
and
by
the
way
one
of
the
reasons
I
selected
JSON
schema-
is
because
it's
also
usable
not
just
within
a
CLI
context,
but
we
can
also
very
easily
extend
that
to
be
used.
B
B
B
A
B
A
Okay,
I,
that
does
look
good
by
the
way
I
was
just
joking
around
I'm,
tired,
so
I'm,
my
brain
is
only
half
half
firing
right
now,
so
I
made
that
post
for
the
curriculum
roadmap
in
the
general
category
of
the
forum's.
Please
please
go
ahead
and
add
to
it.
If
you'd
like
to
see
more
lessons
or
I
divide
it
up
into
things
things
you'd
like
to
see
in
things
that
you
know
you
can
help,
contribute
and
and
I
put
some
examples
in
there.
That
are
things
that
I
know.
A
A
A
C
C
A
Alright
I
think
then
we'll
call
it.
The
time
of
death
is
8:34
a.m.
thanks
for
joining
us
and
we'll
see.
Oh
one
other
thing,
so
we've
been
kinda.
We,
as
you
know,
we
discussed,
and
we
decided
to
move
our
our
bi-weekly
stream
to
Thursday's,
hopefully
to
get
better
participation
of
people
who
we
interview,
because
we
had
three
out
of
four
cancellations
in
the
last
month,
but
also
pop.
You
know
possibly
get
more
views.
We
did
post
the.
We
have
a
two-part
interview.
A
We
did
with
someone
who's
just
getting
started
in
network
automation
and
he
actually
manages
a
team
of
people
that
they're
all
network
engineers
and
he's
trying
to
spend
some
of
them
up
to
be
Network.
Automation,
people
and
he's
he's
got
good,
interesting,
fresh
insights
on
you
know
the
challenges
that
he's
facing.
So
we
posted
the
first
half
of
the
interview.
I
did
over
the
weekend
actually
and
the
second
part
of
the
interview
will
appear
on
the
19th
of
December.
A
We
I
don't
believe
we
might
do
maybe
a
fun
and
not
serious
stream
over
the
Holika
holiday
stream,
but
I
wouldn't
bet
money
on
it
and
but
but
we
might
I
mean
there's
no
reason
really
for
us
not
to.
We
will
take
a
minute
to
do,
but
but
you
should
expect
regular
streams
again,
probably
starting
the
second
or
third
week
of
January.