►
From YouTube: FE Pairing - 20230127 - Chatting and fixing bugs
Description
00:00 - Discussing lack of "Checkout branch" feature in new Web IDE
04:52 - Picking an issue to pair on
08:38 - Discussing ChatGPT
18:00 - Fix error thrown when "Mark as ready" clicked
A
No
in
in
retrospect,
this
was
an
oversight
from
the
when
we
were
just
putting
together
the
ux
of
the
beta
web
ID
to
replace
the
old
web
ID,
because
the
old
web
ID
the
only
place
you
checked,
you
can
check
out
a
branch
is
in
the
committing
flow
and
so
kind
of
assumed
that
we
incorrectly
assumed.
That
would
just
be
the
intuitive
flow.
But
now
a
lot
of
people
didn't
see
that
as
an
option
and
just
felt
like
wait.
I'm
not
going
to
just
commit
to
Maine,
so
I
can't
make
any
changes
here.
A
A
B
A
Know
we're
all
excited
about
it,
yeah!
No!
It's
it's
already
super
super
more
enjoyable
to
use
than
the
web
idea.
Son
I
find
myself
using
it.
What
I
find
myself
using
it
for
kids?
Here's
an
awesome!
Here's
an
interesting
use
case
of
I,
find
myself
I'm
writing
code
locally,
but
I'm.
Also
taking
notes
and
I
will
take
notes
in
the
web.
Id
and
like
this
markdown
thing.
I'm,
like
dropping
in
references
to
Links,
is
like
this
big
thing
of
developer.
Notes
that
I
might
want
to
commit
to
my
project.
A
A
B
A
A
B
A
C
Instead
of
it's
to
the
point
now
at
least
on
this
Branch,
where,
like
in
your
local
GDK,
you
theoretically
should
be
able
to
run
the
vs
code
back
in
and
just
you
know,
as
long
as
you
follow
the
instructions
to
set
up
ranch
or
desktop
with
kubernetes
you
can,
you
can
have
as
many
local
workspaces
as
you
want.
I
should
actually
start
dog
fooding.
That.
C
C
A
A
Okay,
but
like
Natalia
and
I
did
a
lot
of
collaboration
of
the
initial
approach
and
then
possible
other
approaches,
but
I
think
landed
on
a
approach
that
has
a
smaller
footprint
than
what's
currently
merged,
and
so
that's
something
we
might
want
to
consider.
So
that's
one
to
do
I
have
is
this
patch
I
put
together,
I
need
to
open
up
a
separate
Mr
for
it
and
write
some
tests
for
it
and
try
that
out.
So
that's
something
I
gotta
do.
Did
anyone
else
have
any
other
ideas.
B
B
B
I've
done
a
reasonable
amount
of
the
back
end
stuff,
there's
still
some
kind
of
mutations
of
this
pieces.
But
you
know
one
of
the
real
next
steps
is
around
the
front
end,
so
I'm
gonna
cheat
and
stick
to
kind
of
graft
to
our
for
kind
of
creating
the
achievements
for
awarding
the
achievements
for
evoking
and
managing
them,
etc.
For
kind
of
an
MVC
or
MVP.
A
B
B
B
A
B
I
I
don't
know
Chad.
If
you
saw
in
the
the
back
end,
Channel
I
I
wondered
if
anyone
had
done
any
kind
of
automation,
completely
nothing
to
do
with
GPT,
but
automation
of
kind
of
stubbing,
our
specs,
because
I
I
find
it
quite
hard
to
I,
don't
know
if
it's
the
motivation
more
than
anything
but
gets
started
with
the
r
specs
and
thinking
of
how
to
set
it
all
out.
B
A
A
B
B
C
What
I
did
like
I
I
was
using
it
for
the
remote
development
stuff,
like
I
needed
to
write
a
state
machine.
So
I
was
like
okay
write
me,
a
state
machine
and
it
sort
of
did
that
and
then
I
was
like
wait.
A
minute.
Actually
I
want
you
to
use
named
named
parameters
instead,
and
it
did
that
and
I
was
like
okay
and
actually.
C
C
B
C
C
End
of
that
story-
I-
don't
know
if
you
saw
but
like
when
I
was
looking
at
that
aspect
that
it
had
generated
and
I
was
like
yeah
and
I
was
like
wait.
A
minute.
I,
don't
even
need
a
state
machine
here,
I'm
over
complicating
this
really
the
state
is
already
handled
by
kubernetes.
All
I
need
to
do
is
just
expose
that
state
that
it
already
handles.
Okay,.
A
C
A
C
A
A
C
C
A
A
B
A
C
A
A
A
C
A
B
A
A
A
A
A
A
B
A
C
A
A
A
A
C
B
B
A
A
A
Said
failed
to
execute
Quarry
selector,
oh
because
you
can't
even
execute
on
oh
because
it's
not
even
about
oh,
but
that
should
be
fine,
though
I,
don't
think
that's
the
one!
That's
throwing
the
error!
Okay!
Let's
keep
going
then
boom.
Okay,
okay,
all
right!
Yes,
this
isn't
throwing
the
air
let's
keep
going
boom
boom
boom.
Let's
keep
going
oh
geez
all
right.
Let's
keep
going!
A
A
A
B
B
A
A
B
A
B
B
A
B
B
A
A
A
A
Oh,
how
interesting,
oh
this
is
interesting.
That's
why
we
hadn't
run
into
it
before,
because
we
removed
jQuery
from
it
and
jQuery
will
just
silently
fail.
So
it
wasn't
opening
it
wasn't.
Updating
the
title
which
I
think
I
remember
seeing
this
wasn't
updating
the
title.
It
just
wouldn't
throw
an
error.
B
C
C
A
C
A
A
A
C
C
B
B
A
C
B
B
C
A
B
C
I
want
to
challenge
your
assertion
file
that
it's
not
okay,
to
fail
hard
and
do
nothing,
because
this
was
apparently
in
a
state
a
long
time
where,
like
in
halfway
work,
but
there
was
a
misleading
UI
and
nobody
knew
about
it.
To
me,
that
is
a
worse
statement.
It
blows
up
hard
and
hopefully
never
makes
it
to
production.
That's
the
way.
I
I
try
to
approach
things,
I.
A
Think
I
think,
though
it
was
still
working
because
of
this
thing,
this
feature
flag,
like
so
I,
think
it
was
there's
a
lot
going
on
here.
I
could
I
get
it,
though.
What
I
think
is
my
issue.
Is
it's
really
weird
to
say
we
we're
ready
and
something
wrong
happened.
What
I
would
pretend
to
do
is
Let's
and
also,
if
like,
if
we
were
in
typescript
typescript
would
force
us
to
do
it
this
way,
because
doc,
Quarry
selector,
returns
something
that's
possibly
falsy.
So
it's
like
I
mean
it's
a
case.
A
C
A
A
This
really
only
applies
to
did
our
request
fail,
but
because
our
linter
is
not
smart
enough
to
know
that
this
is
the
catch
on.
So
if
you
do
dot,
then
you
can
pass
two
callbacks.
The
first
one
is
when
it's
resolved
and
the
second
one
is
rejected,
but
it's
only
if
this
rejected
not
if
this
thing
failed.
So
then,
ideally,
we
just
have
a
console
error
that
we
would
notice
and
then
we'd
be
fixing
the
console
error,
but
anyways.
A
B
A
A
B
Right,
yeah:
well,
the
other
thing
that
I
I
sort
of
always
think
it's
a
bit
smelly
is
when
we
sometimes
put
no
checks
in
place
because
specs
cause
like
no
no
failures.
If
you
know
what
I
mean
it's
like
well,
we
we
don't
want
to
set
all
this
fake
data
up
just
to
write
a
spec
that
doesn't
care
about
this
bit
of
code.
Let's
put
an
old
handling
in
and
that's
a
bit
of
a
smell
as
well
right.
C
A
C
A
C
C
A
B
A
A
A
Yeah
I'm
wondering
is
this
because
we
just
have
technical
debt
that
we
need
to
pay
off.
This
is
a
lot.
Is
this
not
what
the
other
thing
does?
What
does
the
other
thing?
Do?
Let
me
look
for
what
what
is
it,
how
poor,
poor
people
in
this
Mr
I'm,
sorry,
foreign,
keep
notifying
your
I
probably
should
have
done
a
test
tomorrow
in
this.
C
A
B
A
C
C
Maybe
this
is
a
great
one
for
Lee
to
take
to
Brussels
yeah
yeah.
This
is
a
good
one.
This
is
a
good
like
it's
a
good
journey.
It's
like!
Oh
here's,
a
bug.
It
was
hard
to
find.
We
found
it.
Then
we
looked
at
the
test
and
that
led
us
to
some
technical
debt.
Like
that's,
that's
a
good
journey
to.
He
had
story
to
tell
yeah.
A
A
A
In
that
regard,
from
that
perspective,
if,
if
we're
just,
if
we
have
unit
tests
for
this
I,
don't
even
feel
like,
we
should
add
a
feature
spec
for
it,
because
that
code
path
is
already
covered
with
the
feature
spec,
you
know
and
feature
specs
are
expensive,
so
I
don't
know.
If
we
need
now
that
we're
we
have
Consolidated
the
duplication.
Let's
just.
A
B
A
We
weren't
even
testing
the
success
page
of
this.
All
right
I
have
to
write
some
tests
for
it
yeah
well,
that
was
that
was
fun.
This
isn't
going
to
take
a
long
time.
I'm
we're
I'm
gonna
test
it
out.
I'm
gonna
write
some
tests
for
it.
I'm
gonna
create
an
MR
for
it,
I'd
like
to
see
it
fixed,
but
do
you
think
we
should?
Are
you
doing
a
thing
this
weekend
or
is
it
next
week.
B
A
B
A
B
C
B
It's
the
the
the
challenge
is,
and
you
know
we
have
them
on
these
parent
sessions
and
I
have
them
on
the
community
pairing
sessions.
I
do
every
week
where
we're
we're
fortunate,
because
we've
been
there
and
done
that
with
so
many
bits
and
pieces
that
you,
you
sort
of.
You
forget
that
that
you,
you
hit
snags
all
of
the
time
and
you've
got
that
kind
of
muscle
memory
or
whatever
that's
just
kind
of
oh
yeah,
I
know
what
to.
A
B
Around
that
or
ignore
this
or
do
that,
but
for
a
newer
contributor,
you
know
the
fact
that
we're
constantly
bumping
the
Ruby
version
and
that
causes
GDK
to
break
get
pod
to
break
and
you
know,
bundle,
won't
work
and
there's
just
constant
barriers.
So
it's
really
nice
when
we
find
something.
That's
that's.
A
B
It
includes
the
only
the
only
challenge
I'd
have
is
and
I'll
be
up
for
the
challenge,
but
it
would
be
a
challenge
because
I've
not
tried
to
like
spinner
I
I,
don't
know
the
steps
and
I
hope
it's
I'm
sure.
It
is
well
documented
how
to
like
spin
up
the
local
development
environment
and
but
but
yeah
we're
totally
busy.
B
A
That's
really
helpful
what'd,
you
say
to
run
on
gitpod,
if
no
so
there's
one
issue
that
I
need
to
fix,
so
that
we
can
open
it
up
for
merger,
quests
and
I'm
expecting
to
be
able
to
fix
that
early
next
week
and
then
but
I'll
just
keep
an
eye
out
for
it
and
if
that
looks
like
an
option,
I'll
send
it
your
way,
so
that
yeah
just
so
you
have
a
plan
B.
Maybe
if
GDK
is
causing
some
some
issues.