►
From YouTube: UX Showcase Verify UI Code Contributions
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
All
right,
well,
I'm
glad
that
I'm,
the
last
because
I'm
gonna
try
to
make
it
I,
don't
know
it's.
It's
gonna
be
a
little
bit
different
because
I
was
planning
to
also,
first
of
all,
let
me
just
put
my
timer
here,
because
I
don't
wanna
run
over,
but
yeah
I
wanted
to
like
basically
do
what
we
usually
do,
which
is
like.
We
show
something
about
verify,
so
I
have
runner
and
testing
and
I
was
like
well.
A
I
can
show
a
run
or
testing
topic,
but
I
was
sucking
weed
with
Nadia
and
we
said
like
well:
let's
talk
about
something
different
for
this
one,
so
I,
basically
yeah
I
decided
that
I
was
gonna.
Talk
about
something
that
that
I'm
very
passionate
about
when
she's
doing
contributions
to
the
UI
code
of
GUID
love
surrounds
on
designer
call
it
on
all
right.
A
So
why
this
presentation
so
there's
two
reasons
why
kind
of
like
I
wanted
to
do
these
wanna
ease
awareness,
so
I
think
that
every
everyone
is
aware,
but
not
fully
aware
that
everyone
did
love
and
that
larger
you'd
love
community
can
make
contributions.
We
are
open
source
in
many
areas
and
everyone
can
make
the
product
better,
and
this,
of
course
includes
all
the
you
Xers
everyone
we
see
in
this
call
right.
So
I
wanted
to
dive
deeper
and
explain
what
this
means.
A
I
wanted
to
show
that
even
tiny
contributions
can
make
a
difference
and
then,
of
course,
this
is
kind
of
baked
in
into
our
values.
So
we
have
the
results
and
iteration
value,
and
many
of
those
things
include
things
like
duck
footing,
and
especially
there's
many
things
within
those
values
like
having
bias
for
action
over.
She
note
waiting
for
small
fixes
and
doing
small
merge
requests,
so
this
is
basically
some
index
baked
into
our
culture
and
I
wanted
to
share
this
as
part
of
that
value
package
that
we
were
always
preaching
and
I'm
working
with.
A
So
let's
first
address
the
the
elephant
question
in
the
room.
So
there's
an
elephant
like
chasing
these
guys
and
that
this
is
gonna
be
a
similar
type
of
question
because,
like
I
I'm
pretty
sure
you
have
seen
this
question
many
times,
which
is
shoe
designers
code
right.
So
many
of
you
guys
have
the
the
camera
off
right
now,
but
I'm
pretty
sure
this
is
your
face
right
now.
It's
like,
oh
god,
like
this
question
again
and
the
short
answer
is
no
I.
A
Don't
think
designers
should
code
VRS,
it's
very
nice
when
they
do,
but
I
honestly
believe
that
designers
are
like
multi-skilled
professional
that
very
rarely
have
a
homogeneous
skill
within
a
company.
So
if
you
think
about
any
tech,
company
design
professionals
are
the
most
unique
professionals
within
the
company.
They
are
always
different.
They
always
bring
different
things
to
the
table.
A
They
have
many
skills
and
that
are
very
rarely
repeating
across,
like
the
individuals
are
part
of
a
design
team.
So
they
are
great
for
design
companies
because
they
they
basically
bring
diversity,
which
is
what
makes
a
product
very
strong
when
it
comes
to
addressing
different
audiences
and
solving
different
problems.
We
definitely
definitely
all
share
methodologies
and
we
traverse
problems
in
similar
ways.
A
Basically,
in
the
case
of
a
lab,
we
do
it
because
we
have
structures
and
we
have
things
and
processes
that
allow
us
to
work
in
similar
ways,
but
it's
very
unlikely
that
we
are
all
solving
problems
in
the
same
way
and
I
think
that's
what's
great
about
being
a
designer.
Everyone
solves
a
problem
in
different
ways.
Everyone
is
approaching
things
in
different
ways
and
brings
different
skills
to
the
table
and
and
I
love,
that
about
being
a
designer.
A
And
I
wanted
to
actually
kind
of
dive
deeper
into
these
because,
like
coding,
is
such
a
great
skill,
but
it's
not
the
only
skill
that
can
make
you
different
as
a
designer
there's,
there's
many
extra
skills
that
can
make
you
very
unique
as
a
designer.
So
there's
visual
design,
there's
copywriting,
there's
product
management
skills,
there's
communication
business.
All
these
things
can
make
you
a
powerful
designer.
A
So
when
you
hear
that
narrative
of
like
oh,
you
should
code
like
it's
not
because
like
like
that's
gonna
make
you
unique
it's
basically
because
it's
one
of
the
many
skills
and
become
make
you
powerful
as
a
designer,
but
of
course
again
I,
don't
feel
that
designers
shoe
code,
they
surely
if
they
want
to
and
if
they
like
it,
but
it's
not
necessary
to
excel
as
a
designer.
Okay.
With
that
question
out
of
the
way,
I
have
another
question
which
is
shoe
designers,
understand
code,
that's
concept
and
personal
opinion.
A
Disclaimer
like
this
is
gonna,
be
very,
very
opinionated
and
I'm
I'm
gonna
say
yes,
that's
that's.
Definitely
yes,
especially
a
company
like
it
lab
where
a
technical
company
where
our
audience
are
developers
and
of
course
we
can
understand
what
code
is
and
how
it
impacts
the
job
of
developers
and
how
it's
used
to
build
products,
web
products
and
Easter
products
and
in
the
case
of
github
I,
think
specifically
like
being
knowledgeable
about
get.
You
know,
I
mean
we
have
get
in
the
name
of
the
company
so
like
it
makes
sense
that
you
understand
that
concept.
A
Right
again,
this
is
a
personal
opinion,
but
it
definitely
feel
that
twelve,
my
career
career
throughout
the
years
that
I
have
been
working
on
technology
I
feel
that
when
you
understand
well
how
these
technologies
are
impacting
and
how
things
are
built
and
how
they
are
impacting
the
overall
product,
you
get
a
better
sense
of
what
you're
doing
as
a
designer,
and
you
can
design
better
because
you
understand
like
maybe
what
you're
doing
it's
not
feasible
or
it's
hard
to
achieve,
or
it's
hard
to
implement
or
execute
and
I.
Think
many
people
are
gonna
say
like.
A
So
what's
this
presentation
really
about
right,
like
many
many
of
you
will
probably
are
like
these
Sofia
Vergara
here
it
saying
here
this
is
so
slow
and
don't
worry,
it's
gonna
get
faster
right
now.
So
these
about
how
to
contribute.
Ui
code.
Add
your
skill
level.
So
this
is
not
about
like
inviting
people
to
a
hey
start
like
making
code
contributions.
Even
if
you
don't
have
the
knowledge.
A
Sorry,
if
you
are
not
interested
it's
about
making
contributions
to
these
Avenue
that
we
have
to
contribute
to
the
product
at
any
skill
level
that
you
have
or
any
level
of
compromise
that
you
wanna
put
on
each
of
these
right.
So
I
put
three
three
things
here:
one
is
I,
don't
have
the
skills
or
the
bandwidth
to
make
UI
contributions.
The
second
one
is
I,
don't
have
the
skills,
but
I
want
to
learn
how
to
make
UI
contributions
and
the
third
one
is
I.
A
Have
the
skills
and
I
want
to
keep
learning
how
to
make
you
icon
code
contributions?
So
let's
start
with
the
first
one,
so
you
don't
have
the
skills
and
you
don't
have
the
bandwidth,
and
perhaps
you
don't
have
the
interest.
That's
so
really
fine.
You
know
so
be
like
dr.
Nick
Riviera,
like
called
called
the
doctor.
You
know,
and
if
you
see
something
that
looks
like
a
small
and
easily
fixable
UI
bar,
please
create
the
issue
and
share
it
in
the
UX
Channel.
A
So
other
people
can
see
it
and
someone
like
me
or
someone
else
can
just
take
a
look
at
it
and
if
it's
easy
and
fixable
we
can
fix
it.
You
know
it's,
it's
so
I
think
it
starts
by.
If
you
see
something
say
something
again,
you
don't
need
to
fix
it.
If
you
don't
feel
comfortable
doing
it
simply
someone
else.
Look
at
it
and
I
truly
believe
that
finding
the
bug
is
50%
of
the
job,
literally
like
it's
harder
to
find
these
things.
A
That
solve
these
things
you
know,
so
if
you
find
them
like,
please
report
them
because
sometimes
finding
these
small
issues
that
compromise
the
UX
of
the
website-
it's
pretty
hard.
So
don't
let
it
go.
Please
report
it.
The
second
one
is
I,
don't
have
the
skills,
but
I
want
to
learn
how
to
make
UI
code
contributions.
Perfect.
That's
amazing
and
I
really
really
appreciate
if
you
are
in
this
mindset.
I
start
by
getting
familiar
with
the
most
important
pieces
to
the
UI
code
contributions.
A
A
These
things
are
not
that
hard
and
you
can
read
a
little
bit
about
them
and
you
will
get
them
very
easily
and
start
small
there's
a
lot
of
opportunities
from
bad
from
mad
mob
that
margins
in
certain
areas,
bad
UI
text.
Those
things
are
pretty
easy
to
solve.
Antiques.
It's
just
about
developing
the
mindset.
A
It's
not
easy
at
the
beginning,
but
it
gets
easier
and
easier.
So
it's
just
about
the
mindset
and
that's
basically
you
reading
the
mindset
really
developing
the
mindset
and
getting
into
the
mindset
of
this
is
not
gonna
be
easy
at
the
beginning,
but
it
could
get
easier
and
it
could
have
a
big
impact
in
the
product
and
the
third
one
is
I.
A
Have
the
skills
and
I
want
to
keep
learning
how
to
make
UI
code
contributions
perfect
just
keep
doing
that,
but
also
please
teach
others
and
spread
your
knowledge
teaching
is,
in
my
opinion,
one
of
the
best
ways
to
learn
so
yeah
testify
be
preached
me.
The
person
who
roll
one
explains
other
people
how
to
make
things
and
I
think
that's
gonna.
A
Take
us
a
long
way
and
it's
going
to
help
us
move
forward
product
in
that
final
canonical
layer
of
polish
that
it
requires
and
I
want
to
make
sure
that
designers
have
it
up
are
already
doing
it.
So,
just
last
week,
Nadia
is
and
Holi
these
contributions.
We
charge
small
contributions,
but
they
have
a
profound
impact
in
the
product
right.
So
Nadia's
contribution
was
changing
a
Confucian
texts
on
a
confirmation
dialogue.
A
This
time
it's
just
changing
a
text
and
it
can
so
profoundly
change
the
product
and
make
it
better,
and
it's
really
a
tiny
change
and
holy
pick.
Some
margin
on
the
issues
bore
that
was
kind
of
like
hiding
some
stuff
and
again
that's
like
little
stuff.
It's
just
a
change
in
the
CSS
code,
but
it
increases
the
quality
of
the
product
overall,
and
if
we
fix
a
lot
of
these
issues,
then
we
raise
the
quality
of
the
product
by
a
lot.
A
Ok
and
I
want
to
address
something
else,
and
is
why
these?
Why
not
let
front-end
developers
fix
these
issues
right,
like
they're,
clearly
better
and
more
capable
than
any
of
us
when
it
comes
to
fixing
these
issues?
I
mean
that's
their
job
and
they
are
great
at
it.
So
why
should
we
put
any
effort
or
bandwidth
into
this?
So
first
of
all,
let
me
clarify
something:
your
focus
should
be
your
design
responsibilities.
I'm,
not
just
in
here
like
go
and
start
coding
and
making
UI
contributions.
A
Maybe
maybe
you
can
make
that
contribution,
but
definitely
be
aware
that
if
your
time
is
better
spent
somewhere
else
or
on
something
something
else,
then
you
probably
should
be
doing
that
so
that's
I
kind
of
want
to
get
that
out
of
the
way.
But
the
real
reason
for
this
is
that
I
think-
and
this
is
again
like
personal
opinion.
Designers
are
excellent
at
context.
Switching.
A
We
are
way
better
than
many
other
people
in
the
tech
industry
when
it
comes
to
jumping
from
problem
to
problem
like
context
which,
in
our
context,
multiple
times
a
day
and
what
does
mold
change
for
a
designer
in
terms
of
context,
it
can
be
highly
the
contextualizing
for
a
developer
and
a
context.
Switching
is
more
expensive
to
a
developer.
So
if
we
say
like
hey,
front-end
developer
COO,
you
fix
this
is
mostly
assess
issue.
Yes,
they
can,
but
it's
gonna
like
put
them
out
of
their.
A
You
know
like
a
focus
on
they're
gonna
get
out
of
the
zone
and
it's
gonna
they're
gonna
be
more
costly
in
terms
of
what
they're
doing,
which
is
feature
sound
like
developing,
like
very
important
things
for
the
product.
So
that's
one
reason
and
I
think
that
the
other
reason
is
that
designers
are
generally
more
skill,
I'm
patient
when
it
comes
to
fit
and
finish
phase
we're
more
willing
to
test
pixel
differences,
reevaluating
my
no
visual
differences
and
kind
of
finding
those
contrasting
things
in
the
UI.
A
So
we
have
a
lot
of
UI
skill
when
it
comes
to
finalizing
and
polishing
and
I.
Think
that's
why
this
is.
Him
is
important
for
us
to
make
these
type
of
contributions,
and
what's
the
impact,
I
think
the
impact
I
wanted
to
summarize
it
as
the
fit
and
finish
developer
theory,
which
is
seed,
has
mentioned
several
times
that
the
average
amount
of
Amar's
per
developer
at
the
lab
right
now
is
about
12
and
Mars
per
release.
A
So
if
we
as
a
department,
we
contributed
and
merge
twelve
is
more
UI
fixes
per
release,
we're
effectively
effectively
adding
with
our
efforts
and
extra
headcount
of
development.
I
know
we
are
not
creating
like
massive
amounts
of
development
contributions,
so
it's
not
the
regular
development
contributions,
but
they
are
very
significant
for
the
final
UI
and
UX
and
and
I
definitely
think
that
they
have
an
impact
in
the
experience.
A
So
the
way
that
I
see
it
is
like
we
are
adding
this
new
person,
virtual
hypothetical
person
who
is
the
fit
and
finish
developer,
and
it's
one
extra
headcount
just
think
about
it.
That
way,
it's
like
this
person
who
is
doing
12
as
more
UI,
fixes
her
release.
That's
like
having
an
extra
developer
and
we
have
60
people
in
our
department,
so
I
think
that's
something
that
it's
very
feasible
but
anyways.
That's
what
I
wanted
to
share
today.
That's
the
freedom,
Finnish
developer!