►
From YouTube: GSoC 2023 Office Hours - April 13, 2023
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Out
hello,
good
night
good
afternoon,
good
morning,
everybody
around
the
world.
This
is
an
informal
Google
summer
of
code
office
hour.
Today
is
the
13th
in
April
informal,
because
we're
currently
in
in
the
review
and
ranking
of
The
Proposal,
so
we're
just
hanging
there
and
having
interesting
questions
or
topics
to
discuss
and
I.
Believe
mukul
had
an
interesting
question
where
you
wanted
to
have
some
Reflections
on
experiences
that
he
had
so
mukul
go
ahead.
B
So
my
question
is
like
so
I
start:
for
example,
I
start
with
the
data
repo
or
open
source
project
like
Azuma,
open
source
project,
and
as
for
approaching
that
project
like
people
say
you
don't
have
to
understand
the
whole
code
base
to
work
on
a
issue
or
something
on
or
implementing
a
feature.
B
So
what
I
do
is
like
I
go
to
the
source
file
like
main
dot,
for
example,
if
I
am
working
with
go,
project
like
I
will
go
to
the
me.go
and
see
what
that
is
calling
or
what
the
main
person
is
calling
and
from
there.
B
I
approach
to
the
other
functions
call
that
they
are
called
in
as
soon
but
I
think
this
is
inefficient,
like
I
have
to
do
whole
review
of
the
code
base
to
understand
what
is
going
on
and
what
I
can
do
like
for
that
feature
like
assume
that
I
have
to
search
for
a
file
like
for
a
feature
for
a
feature.
B
Implementation
I
want
to
search
for
a
file
like
where
I
can
put
that
feature,
but
for
this
understanding
itself,
I
have
to
understand
the
code
base
itself
to
some
extent.
B
So
how
can
I
proceed
with
the
understanding
of
the
code
base,
like
understanding
from
the
main
function
itself
takes
a
lot
of
time.
So
how
do.
A
B
A
Now
it's
this
question
is
a
beautiful
one
and
I
will
give
the
word
to
to
mark,
because
I
think
he
has
some
good
experiences
there
just
want
to
say
there.
This
is
a
key
question
and
if
you
master
this
type
of
of
action
so
getting
into
a
code
base
I
think
you
have
the
key
or
an
interesting
and
rewarding
professional
career,
because
this
will
be
so
often
that
you
will
have
to
deal
with
this
kind
of
things
so
Mark.
What
are
the
kind
of
tips,
advice
or
experience
that
we
can
share
with.
C
So
I
think
first
first,
the
most
fair
thing
mukul
to
highlight
is
that's
the
reality
of
software
engineering
for
the
foreseeable
future.
You
will
spend
a
lot
more
time.
Reading
code
than
writing
code,
some
of
the
smartest
programmers
I've
ever
known,
have
consistently
and
repeatedly
told
me
they
spend
much
more
time
reading
code
than
writing
it.
So
so
the
reality
is.
This
is
ahead
of
you
for
a
very
long
time,
this
ratio
of
read
versus
write
because
you've
got
to
understand
first.
So
so,
no
shame
that's
good.
C
Now,
on
the
on
the
sneaky
tricks
to
understand
a
code
base
sooner
okay
I'll
share
a
couple
of
sneaky
tricks
that
I
have
and
let
other
people
speak
up
sneaky
trick.
Number
one
is
run
the
product
and
see
how
it
behaves.
Watch
it
from
a
user
experience
to
see
how
it
behaves
after
watching
how
it
behaves
as
a
user
experience
run
the
product
from
a
debugger
set
break
points
on
things
that
you
find
interesting
and
try
to
hit
them
and
the
the
indicator
there
is.
Oh,
oh
I
did
get
it.
C
I
know
how
this
code
is
behaving
or
I
didn't
and,
and
so
the
debugger
is
my
friend
for
code
comprehension.
Other
people
probably
have
different
techniques,
but
for
me,
I,
like
a
debugger
and
looking
at
the
code
to
see
what
it
does,
how
it
hap,
how
it
works
and
what
my
experience
is
using.
It
inevitably
I
discover
in
the
debugger
that
things
I
thought
I
knew
I
did
not
in
fact
know
or
what
I
knew
was
false.
That's
all
that
I'd
offer.
A
Yeah,
and-
and
this
is
basically
it's
like
a
scientist-
you
take
your
your
magnifying
glass
and
you
look
and
you
try
to
see.
Oh,
the
code
went
through
there
and
when
I
touched
this
button,
this
then
happens
or
or
this
is
exactly
observing
another
tip
I'm
going
to
add
before
giving
the
word
to.
Whoever
wants
to
to
add
there
is
a
very
good
entry
point
is
looking
for
tests
and
the
tests
that
have
in
the
name
end-to-ends
or
integration,
or
these
kind
of
things.
A
They
tend
to
activate
multiple
pieces,
and
once
you
understood
the
global
functionality
of
what
it
is
reading,
the
tests
exposes
in
more
details.
This
is
what
the
code
is
supposed
to
do.
This
happens,
and
the
third
tip
is
that
altered
the
code
on
on
your
on
your
local
copy
and
adds
signals
or
Flags
or
or
things
that
you
know
oh
I,
went
through
here
and
if
I
change
that
value
by
hand.
A
E
Yeah
I'll,
just
like
I,
want
to
add,
like
the
the
best
thing
is
I'll
learn
by
doing
so.
This
is
like
something
you
just
go
through
like
rough
since
I
think
this
the
students
are.
These
are
all
college
students,
so
they
don't
have
like
much
idea
about
the
agenda
so
whatever
they
read
it,
they
go
through
as
a
scratch
like
a
general
as
a
user
perspective,
so
they
get
more
overview
of
something.
E
A
There's
something
I'd
like
to
add,
because
I
I've
seen
that
in
a
question
of
mukul
and
I,
let
him
then
afterwards
react
on
that.
So
the
question
would
be.
Do
you
first
try
to
understand
the
global
picture
of
what
the
code
base
does,
or
do
you
only
concentrate
on
the
feature
you're
going
to
work
on
and
and
you
you
just
fly
into
it,
and
try
to
understand
the
piece
that
you're
going
to
to
change
Mark?
Do
you
have
an
opinion
on
that
before
I
give
mine.
A
A
They
first
need
to
get
the
global
picture
to
understand
the
various
components
how
they
interact
and
how
they
live
together,
and
the
approach
that
we
described
that
Chris
was
hinting
to
first
to
understand
how
it
works
on
the
surface
then
starts
digging
into
it
and
peeling
off
the
layers
of
the
onion
before
you
get
others
go
immediately
to
the
feature
and
and
to
the
active
item
they
they
want
and
then
builds.
The
global
picture
of
it
mileage
depends
depends
on.
A
The
case
depends
on
the
way
you
you
tackle
problems,
so
it
it
really
depends
so
mukul
you
had
plate
full
of
answer
to
your
very
interesting
question.
Is
there
something
useful
for
you
in
it.
B
Yes,
yes,
I,
basically
try
to
run
it.
That's
what
I
do
and
I
execute
I
exit,
not
execute
I
like
understands
it
from
the
main
concern
and
that's
what
I
do,
but
this
still
doesn't
give
me
what
I
was
thinking
like
you,
I
was
thinking
like
you.
You
must
be
using
some
tools
or
something
like
that.
Will
that
would
have
make
it
easier
for
you,
but
that
wasn't
the
case
and
you
guys
are
also
reading
it
understanding
it
by
reading
it
and
that's
how
things
work.
C
Yeah
I
think
I
think
your
IDE
is
a
good,
a
good
friend
right,
be
sure
you
use
it
read
advice
some
years
ago
of
people
who
advise
specifically
to
spend
time
learning
more
about
the
features
of
your
integrated
development
environment
because
it
can
help
you
navigate
code
much
more
rapidly.
Now
that
that's
a
personal
skill,
you
have
to
develop,
not
something
anybody
else
can
can
really
teach
it's.
How
do
I
navigate
from
one
symbol
to
another
inside
my
integrated
development
environment?
How
do
I
set
a
breakpoint?
How
do
I
remove
the
break
point?
C
How
do
all
things
that
you're
spending
time
intentionally
learning
how
to
use
your
IDE
well
are
a
good
thing.
I
I
happen
to
use
a
rather
strange
IDE
environment
and
it
works
for
me,
other
people
use
more
standard,
IDE
environments,
but
knowing
your
environment
or
what
works
for
you
is
really
is
a
is
a
can
make
your
comprehension
process
faster.
A
Yeah
yeah
now
I
I
have
one
comment
I'd
like
to
to
add
to
it.
One
of
the
conclusion
of
the
discussion
we
have
now
is
that
reading
the
codes
is
where,
where
the
majority
of
people
start
and
spend
a
lot
of
time
in
Mark
shared
that
very
experienced
developers
spend
a
huge
amount
of
their
time
doing
that.
A
That
means
that
when
you
write
your
code,
in
fact
your
Hawking
literally
talking
to
the
people
or
to
yourself
in
a
couple
of
months,
that
will
read
your
code
and
so
be
be
wary
of
that
and
and
and
try
to
help
the
person
by
choosing
adequate
variable
names,
method,
names,
an
adequate
comment,
not
a
comment.
This
is
a
function
that
or
a
method
that
does
this
yeah
from
the
name.
You
can
figure
that,
but
why
did
you
choose
that
algorithm?
A
So
it's
a
dialogue
that
you're
setting
up
with
the
person
reading
you're,
not
talking
to
the
computer,
he's
clever
enough
and-
and
he
doesn't
need
you're
talking
too
human
just
wanted
to
add
that
and
for
the
joke.
I
can
I
can
add
that
maybe
remember
that
a
person
who
is
going
to
maintain
your
code
is
a
psychopath.
That
knows
where
you're
living
so
take
care
of
him
and
don't
try
to
make
him
angry.
A
Why
does
this
a
little
bit
too
far,
but
remember
you're
talking
to
either
yourself
or
a
colleague
in
a
couple
of
months?
Does
that
help
you.
B
Yes,
I
have
another
question
like
you
were
talking
about:
choosing
name
for
functions
so
assuming
that
I
have
a
feature,
request
issue
for
feature,
request
and
I
create
a
function
now
what
is
happening
that
that
person
is
like
use,
calling
a
person
that
is
already
implemented,
but
I
didn't
know
about
that
that
the
person
was
present
in
the
code
base,
so
I
created
my
own
implementation
of
that
function.
B
So
how
can
you
know
that
that
person
was
there
or
what
can
I
do
about
this?
Like
the
function
name?
It
can
disorder
by
function.
Name
like
someone
said
that
that
concept
name
should
be
XYZ
and
I
have
my
implementation
that
saying
that
ABC
so
now
there
will
be
two
functions
in
doing
the
same
job,
while
what
I
should
be
doing
is
using
the
function
x,
y
z,
that
is
already
present.
So
what
can
I
do
to
like
handle
this
kind
of
situation.
B
A
Well:
okay,
but
you're
waiting
for
somebody
to
to
to
catch
it
up.
Good
point,
and-
and
this
is
where,
but
here
you're
wasting
your
time
or
or
you
spending
your
time
in
the
maintainers
time,
so
there
might
be
other
strategies
Mark.
If
you
wanted
to
say
something
interesting,
dialogue.
C
Yeah,
okay,
so
so
recent
story,
I
found
by
reading
the
javadoc
of
a
particular
test
method.
A
test
class
called
Jenkins
rule
that
there
were
features
inside
that
thing
that,
after
many
years
of
doing
Jenkins
development,
I
didn't
realize
they
were
there.
Okay,
no
shame:
I
went
in
and
started
using
them,
so
I
think
McCool.
The
correct
answer
is
great.
You
learn
something
you
won't
have
to
learn
that
again:
you're
you're
set.
It's
you
solve.
C
The
initial
problem,
write
the
function,
You,
Needed
Somebody
told
you
hey,
you
know
what
there's
a
way
to
simplify
this
great
now,
you've
learned
and
you
you
simplify
it,
revise
it
and
and
keep
going
it's.
We
start
where
we
are
and
we
learn
more
about
the
things.
In
my
case
there
were
some
impressively
capable
functions
in
Jenkins
rule
that
some
really
smart
people
had
created.
That
I
should
have
been
using
for
a
long
time
and
and
reading
javadoc
would
have
been
a
good
thing
if
I'd
done
it
several
years
ago.
C
A
A
You,
you
have
a
couple
of
of
a
half
an
hour,
an
hour
to
spend
hey
start
digging
into
the
code
or
the
javadoc
of
the
libraries
that
you're
using
can
even
be
the
the
Java
ones
and
or
or
the
mainstream
ones,
and
have
a
look
and
say:
oh
yeah,
I
didn't
know
that
or
this
is
oh,
and
so
you
build
up
your
passive
knowledge
of
the
features
that
are
available.
A
So
mukul,
before
giving
you
back
the
word
I'm
going
to
ask
on
their
comments
on
this
or
other
questions.
I've
seen
that
sonali
joined
the
call
sounds
like
also
joined
a
call,
so
I
want
to
give
you
also
a
chance
to
either
give
your
opinion
on
on
that
or
ask
a
question.
Well,
cool
is
a
very
good
question.
A
F
Currently,
I
don't
have
anything
I've
been
busy
with
my
exams.
I
also
have
an
exam
tomorrow,
so
I
was
just
studying
mobile
computing.
A
Okay,
good,
we
have
five
minutes
left
other
questions.
Other
topics.
B
A
G
So
my
first
question
is
that
how
do
I
negotiate
my
salary,
while
in
an
interview
so
I
have
that
sort
of.
A
That's
an
interesting
question
now:
I
can't
give
you
advice
on
on
on
that
one
besides
trying
a
baseball
bat
and
when
discussing
with
during
the
interview
here,
I
will
not
be
able
to
help
you
on
that
one,
and
the
only
thing
I
can
I
can
give
you
is
by
increasing
your
market
value.
Let's
say
that
way.
A
Building
your
experience
and
being
able
to
show
that
to
the
recruiter
will
make
you
in
a
better
position
for
these
kind
of
discussions,
and
what
we're
doing
here
through
open
source
is
a
wonderful
way
to
build
that
experience.
So
this
is
why
we're
spending
the
time
not
only
for
open
source,
but
also
for
you
that
this
is
a
win-win
situation,
where
the
community
gains
from
the
people's
work,
but
you
as
a
human
being,
learn
so
you're
increasing
your
market
value
as
a
developer.
A
With
that
now,
how
do
you
talk
to
an
employer
or
I
I
I
I
can't
give
any
good
advice,
especially
as
it's
very
cultural,
so
it
really
depends
from
country
to
Country,
so
I'm
I'm,
sorry
for
that
one.
It
was
an
interesting
question
for
him,
but
that
one
I
I'm,
sorry
unless
Mark
has
or
or
somebody
else
has.
C
U.S
salary
negotiations,
I'm
confident,
are
quite
different
than
salary
negotiations
in
negotiations
in
India
I'm
sure
that
Chris
negotiates
very
differently
in
in
Hong
Kong
and
John
Mark
differently
in
Belgium
right.
Each
each
has
their
own
place
and
talk
to
talk
to
people
who
are
geographically
near
you,
preferably
also
company
near
you,
so
that
you
understand
what
your
choices
are
and
what
what
options
you've
got.
B
Yes,
so
this
is
basically
about
the
issues
that
are
marked
as
bug.
So
how
do
we
replicate
environment
like
this
is
that
the
bug
was
produced
in
XYZ
OS?
So
how
do
you
guys
like
do
that?
Do
you
use
AWS,
VMS
or
like
local
VMS,
because
if
I
use
local
VMS
there,
I
will
have
memory
constraints
like
I,
have
16GB,
RAM
and
I?
Don't
think
it
will
be
enough
to
run
the
program
in
a
nice
way
or
and
hold
me.
B
So
how
do
you
like
replicate
a
environment
which
can
produce
that
bug.
C
Try
first
with
what
you've
got,
because
what
you've
got
is
local
to
you
is
convenient,
easy
and
fast.
Try
try,
first
with
what
you've
got,
because
the
difference
between
your
environment
and
the
place
where
it
where
the
bug
was
initially
reported,
may
not
be
relevant,
and
so
your
16
gigabyte
machine,
your
four
gigabyte,
Raspberry
Pi,
maybe
enough
to
duplicate
the
problem.
If
that's
what
you've
got
locally,
if
you
can't
duplicate
it,
that's
good
information
to
tell
to
the
person
who
reported
the
issue
saying
I
attempted
to
duplicate
the
problem.
C
I
took
the
following
steps
and
couldn't
that
will
then
help
them
understand?
Oh
okay,
I
did
not
give
enough
detail
and
you
give
them
back
more
detail,
saying
here's
what
I
attempted
I
ran
this
on
this
equipment
with
this
environment
and
it
didn't
show
the
problem,
and
hopefully
they
will
realize.
Oh
I
need
to
say
more.
If
not,
you
can
tell
them
directly.
Please
tell
me
how
you
duplicated
the
problem.
Give
me
more
precise
steps.
B
Basically,
like
in
few
of
the
issues
they
maintain
a
like
mentioned
that
the
so
is
replicable,
but
for
that
for
the
logs
or
for
I
want
to
see
what
is
happening
wrong
there.
I
have
to
replicate
that.
So
how
can
I
do
that,
like
what
you
guys
are?
What
you
guys
do
for
that
I
want
to
like
the
problem
is
arising
in
specific
environment
like
specific
Os
or
specific
conditions.
Only
so
how
do
you
know
that
is
amazing?.
C
Rare
for
it
to
be
environment
specific,
but
maybe
it
is
that
they
say:
hey
I
only
get
this
failure
when
I'm
running
on
a
system,
390
Mainframe
running
zos,
not
running
Linux
on
that
system,
390
Mainframe
from
IBM.
In
that
case,
you
can
ask
for
log
files.
As
you
said,
you
can
ask
for
log
files.
You
can
ask
for
Diagnostics,
you
can
inject
additional
Diagnostics
and
give
them
a
a
new
build
and
say
this
build.
C
A
Yeah
and,
and
here
focusing
on
trying
to
reproduce
the
environment
is,
is
very
seldom
required,
as
Mark
said,
unless
there
there's
signals
that
show
that
it's
environment
specific,
because
you
have
error
messages
in
in
the
operating
system,
or
you
have
memory
related
problems
so
and
and
try
first
based
on
the
environment
to
reproduce
the
functional
part,
the
sequence
of
steps
that
were
that
were
required,
hello
to
tabim,
they
joined
the
call.
Thank
you
for
turning
the
camera
on
I
like
seeing
the
faces,
so
welcome
aboard
so
mukul.
A
A
Are
there
other
questions
or
topics
that
can
be
discussed
today?
Otherwise
we're
slowly
going
to
close
this
call
and
meet
again
next
week.
Note
that
mentors
are
very
busy
these
days,
so
we
in
org
admins
do
a
lot
of
chasing.
A
Somebody
wants
to
add
something
for,
for
this
call
or
a
question
comment
experience.
H
A
Yes,
yes,
so
this
is
a
general
comment:
I,
just
don't
why,
okay
to
go
on
mute
because
there's
a
loopback
in
there.
So
please
continue
it's
it's
part
of
building
your
muscle
building
your
experience.
A
They
are
a
lot
of
candidates
this
year
a
lot
and
we
only
have
a
limited
number
of
seats,
but
with
all
the
experience
that
you're
gaining,
you
will
be
able
to
compete
again
next
year
with
a
much
better
position
with
the
experience
and
on
the
other
side
professionally.
Also,
you
continue
to
learn
and
see
how
the
the
community
Works
will
also
have
Oktoberfest,
which
is
another
open
source
event.
So
here
don't
hesitate
to
continue.
A
You're
you're
welcome
and
we'll
I'll
try
to
arrange
also
to
have
people
available
from
the
community
to
guide.
You
will
be
maybe
less
focused
than
with
Google
summer
of
code,
but
here
let's
have
fun
together,
don't
drop
the
effort.
A
lot
of
people
spend
a
lot
of
energy
learning
things
investing
and
here
we're
nice
nice
group
of
people
here,
and
we
can
also
help
each
other
here,
so
don't
hesitate
also
to
help
other
students
or
young
contributors
there.
A
So
good
question
here
I
think
we're
going
to
leave
it
that
because
I
generally
go
up
to
the
hour
and
each
time
my
dog
is
getting
upset
because
he's
waiting
behind
the
door
to
have
his
walk
it's
the
evening
here.
So
we'll
we'll
close
the
the
call
here.
Thank
you
very
much
for
everybody
to
have
joint,
we'll
we'll
make
a
little
bit
more
publicity
on
guitar.
If
people
forget
the
exact
time
when
the
office
hour
starts
been
a
pleasure
to
meet
you
all
and
see
you
then
next
week,
okay,
thanks.