►
From YouTube: VS Code Tips and Tricks - Sana Ajani, Microsoft
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
Hey
everyone.
Thank
you
for
joining
me
today
here
at
open,
Jas,
I
hope
all
of
you
and
your
loved
ones
are
staying
safe
and
healthy
during
these
difficult
times
that
we're
in
my
name,
is
sana.
Ajani
and
I'm,
a
program
manager
at
Microsoft
on
the
Visual
Studio
code
team
I'm
really
excited
to
be
here
today,
I'm
coming
to
you
from
New
Jersey
from
my
high
school
bedroom.
So
today,
I'm
going
to
be
showing
you
some
really
awesome
tips
and
tricks
on
how
to
be
productive
inside
vs
code.
A
A
All
right,
let's
get
started
today,
we're
going
to
spend
most
of
the
time
inside
the
tool
itself.
This
is
going
to
be
jam-packed
with
lots
of
v/s
code,
goodness
I'll
start
with
showing
some
small
quality-of-life
tips
and
tricks,
and
then
I'll
go
into
showing
a
demo
of
some
of
the
latest
github
integration
that
we've
added
and
then
finally,
I'll
do
an
overview
of
what
remote
development
is
and
I'll
show
a
demo
of
one
of
the
extensions.
A
A
This
is
the
one
our
team
uses
to
actually
work
on
vs
code,
so
it's
straight
from
master
you're
going
to
be
using
the
hottest
bits.
If
you
use
insiders,
you
get
a
lot
of
the
latest
features
that
are
still
in
preview
or
things
that
we're
experimenting
with
that.
We
would
like
feedback
on
and
if
you
find
a
bug
or
an
issue,
and
you
report
it,
we
can
typically
get
that
fix
within
a
day
or
two.
So
it's
a
really
fast
turnaround.
You
can
have
both
installed
side
by
side,
the
stable
version
and
insiders.
A
They
are
isolated
from
each
other
and
you
can
go
to
code.
Visual,
Studio
comm,
slash
insiders
to
install
it.
Now,
let's
go
on
to
the
next
part
of
customizing.
The
editor
I
think
the
best
part
of
vs
code
is
that
it
is
extensible
and
flexible
to.
However,
you
like
to
code
or
whatever
your
productivity,
workflow
or
style,
is
with
extensions
and
settings
even
the
layout.
There
is
just
so
much
ways
to
customize
vs
code,
so
my
vs
code
will
look
different
from
your
vs
code
and
that's
totally
fine
right.
A
We
want
vs
code
to
work
the
way
that
all
developers
work
so
some
of
the
most
important
shortcuts
and
things
you
remember,
the
first
one
is
the
command
palette.
So
every
action
that
you
do
in
vs
code
can
basically
be
mapped
to
a
command.
If
you
are
on
Windows,
it's
ctrl
shift
P
or
if
you're
in
a
Mac,
its
command
shift
P
or
you
can
use
f1.
So
if
I
do
this,
this
opens
up
the
command
palette.
A
So
if
you're
ever
wondering,
hey,
I
wonder
how
to
open
this
part
or
I,
wonder
if
vs
code
can
do
this,
you
can
search
for
something
that
you
want
to
do,
and
they'll
typically
show
up
in
here.
Extensions
can
also
contribute
command
to
this.
So,
for
instance,
you
see
I
have
a
bunch
that
are
from
like
this
github
issues.
Extension
or
I
can
just
type
things
in.
So
if
I
want
to
see
all
the
git
related
things,
I
can
do.
There's
a
whole
bunch
of
commands
that
you
can
access
from
the
command
palette.
A
The
next
pro
tip
is
the
settings,
so
this
is
going
to
be
control,
comma
or
command
comma.
So,
if
I
do
this,
this
will
open
up
my
settings
editor.
There
are
two
settings
editors
in
vs
code,
both
a
UI
which
you're
seeing
right
now
and
a
JSON.
So
if
you
prefer
one
or
the
other,
you
can
change
this
shortcut.
So
if
I
search
for
settings
you
can
see
here
the
setting
for
settings
editor
so
I
have
it
set
to
the
UI.
But
if
you
prefer
JSON,
you
can
do
this.
A
Autosave
has
literally
saved
lives,
no
joke.
This
is
going
to
see
your
workflow.
If
you
don't
already
have
this
turned
on
there's
different
options
that
you
can
turn
on
I.
Have
it
on
focus
change.
So
if
I
switch
editors
or
switch
my
window,
this
is
what
I
prefer,
but
also,
if
you're,
a
JavaScript
editor
a
developer.
A
Sorry,
another
thing
that
might
be
useful
for
you,
instead
of
for
my
autosave,
is
format
on
save,
so
you
can
have
one
or
the
other
typically
set,
and
this
is
if
you're,
you
know
using
something
like
prettier
or
some
kind
of
formatter,
and
you
prefer
to
use
this
every
time
you
see
if
it
will
just
format
everything
with
your
prettier
config.
So
this
is
really
convenient
for
a
lot
of
JavaScript
developers.
A
Let's
go
into
some
other
quick
keyboard
shortcuts
that
are
really
going
to
help
you,
when
you're
coding
inside
the
editor,
so
I'm
open
up
the
markdown
file
of
this
copying
line
up
and
down.
So
this
is
a
really
good
tip
that
I
really
like.
So
if
you
are
using
a
Mac,
it's
gonna
be
shift
option
up
or
down.
So
if
I
do
this,
I
can
actually
take
each
line
and
just
really
easily
move
it
to
the
right
place.
A
So
this
is
a
really
easy
and
important
tip
that
saved
me
a
lot
of
time
instead
of
copying
pasting,
another
one
is
multiple
cursors.
This
is
awesome.
This
is
going
to
save
you
so
much
time,
so,
there's
different
ways
to
do
this.
The
one
that's
easy
to
do
a
few,
if
you
prefer
using
a
mouse,
is
option.
Click,
so
I
can
actually
place
where
I
want
the
cursors
to
be
in
this
one
or
you
can
use
shift
command
L,
and
this
will
actually
highlight
the
same
word
every
time
it's
found.
A
A
And
now
it's
going
to
showing
you
how
to
customize
your
vs
codes
layout,
so
first
thing
you
can
do
is
actually
move
around
things
in
the
activity
bar
inside
bar
a
lot
of
people.
Don't
you
can
do
this?
You
can
move
icons
around
that
you
get
from
different
extensions.
You
can
right-click
and
also
hide
different.
You
know
extensions
icon,
so
you
can
make
your
activity
bar
a
little
bit
cleaner.
If
you
want
same
with
the
status
bar,
you
can
choose
to
hide
things
or
show
things.
A
However,
you
want,
but
one
of
the
latest
things
that
we've
done
inside
vs
code
is
actually
help.
You
customize
your
layout
a
little
bit
more.
So
if
you
do
ctrl
or
command
tilde
or
sorry
backtick,
this
is
going
to
open
up
a
terminal.
So
we
want
to
give
you
more
freedom
to
be
able
to
move
things
between
the
terminal
and
this
sidebar
over
here.
So
when
you
have
all
this
open,
it
can
be
a
little
bit
much,
and
maybe
you
want
to
move
different
views
to
different
places
based
on
your
preferred
workflow.
A
So,
for
instance,
if
I
wanted
to
maybe
take
the
search
panel
over
here
and
move
it
into
my
bottom
view,
I
can
do
that
now
and
now
I
get
the
same
search.
Functionality
still
works
still
does
the
same
thing.
It
would
if
it
was
in
the
other
place
and
I
can
also
do
the
vice
versa.
So
if
I
want
to
maybe
take
the
debug
console
here
and
maybe
move
it
inside
my
debug
view,
I
can
do
that
too.
It's
really
sweet.
A
It's
really
easy
helps
you
really
totally
customize
and
take
control
of
your
editor
and
say.
Maybe
you
are
moving
things
around
experimenting,
and
maybe
you
maybe
set
something
to
a
different
location.
You
can
just
right-click
on
the
view
and
reset
the
location
or
you
can
search
for
the
command
reset
view,
and
it
does
the
same
thing
so
now,
everything's
back
to
where
it
was
another
pro
tip
is
I've
heard
from
a
lot
of
users
that
they
actually
prefer
this
sidebar
to
be
on
the
right
side
and
not
on
the
left
side.
A
So
you
can
go
to
view
appearance
and
you
can
move
the
sidebar
to
the
right
and
some
people
prefer
this,
because
when
they
actually
toggle
this,
it
will
not
actually
move
their
code
or
their
editor.
But
if
it's
on
the
right,
if
it's
on
the
left
side,
it
will
so
I
can
move
a
bar
it
back
to
the
left,
and
this
actually
moves
your
code,
which
it
can
be
a
little
bit
jarring.
A
All
right,
let's
talk
github
so
on
the
vs
Co
team.
We
want
to
make
you
as
productive
as
possible.
When
we
talk
to
developers,
we
often
hear
things
like
there's
so
much
context.
Switching
so,
for
instance,
when
I
move
from
all
my
tabs,
I
have
open
on
github
and
back
to
my
code,
I
lose
track
of
a
lot
of
things.
I
lose
time,
I
lose
focus,
so
we
want
to
make
the
stuff
that
you
do
on
github
closer
to
you
inside
your
editor.
We
want
to
bring
the
outer
loop
a
lot
of
the
collaboration.
A
So
one
of
the
extensions
that
you
definitely
need
to
have
installed
if
you're
working
with
github
and
any
capacity
is
the
github
pull
requests
and
issues
extension,
so
I
can
search
for
it
inside
the
extension
marketplace.
It's
the
one
that's
published
by
github.
So
this
lets
you
create
and
manage
comment
on
and
merge
pull
requests
from
inside
vs
code
and,
most
recently
we
also
added
support
to
let
you
work
with
issues
as
well.
A
So
once
you
have
this
installed,
it's
going
to
contribute
this
icon
to
the
activity
bar,
and
it's
going
to
ask
you
to
sign
in
so
you
have
to
do
that
once
so
now,
I'm
going
to
open
up
a
new
window,
so
we
wanted
to
make
it
really
easy
for
anyone
to
get
started
with
github
as
well.
So
this
is
a
totally
empty
project.
It's
an
empty
window,
I'm
going
to
clone
a
repository
so
because
I've
in
with
the
github
pull
request.
Extension,
it's
going
to
leverage
that
and
let
me
clone
from
github.
A
So
you
can
see
here
this
populated
a
list
of
all
the
repos
that
are
actually
associated
with
me
on
my
github
profile.
This
is
really
neat
really
convenient
for
me
to
be
able
to
just
clone
a
repository,
but
I
can
also
search
for
any
anything
on
github.
So,
for
instance,
if
I
wanted
to
maybe
work
on
a
react
project,
I
could
do
that.
I
could
just
search
for
create
react
tap.
A
Alright,
let's
clone
that
to
my
local
machine.
You
can
see
here.
Vs
code
is
doing
that
real,
quick,
let's
open
in
a
new
window
and
I.
Have
it
installed
right.
That
was
really
easy.
Normally
with
cloning,
something
you
have
to
go
to
github,
no
get
the
link,
bring
it
in
your
terminal.
Do
all
that,
so
we
want
to
make
it
super
super
easy
for
you
to
get
started.
A
So,
if
I
open
up
my
terminal,
let's
just
check
if
everything
worked
out
all
right,
so
Villa's
code
cloned
it
and
set
up
my
remotes
for
me
over
HTTP.
This
is
really
easy
great
to
get
started
with
the
great
to
just.
Do
it
from
inside
your
editor.
If
you
want
to
alright
I,
want
to
show
some
more
really
cool
things.
The
github
extension
lets
you
do
inside
vs
code,
so
I've
opened
up
a
folder
with
a
project.
I
have
called
task
runner,
and
this
is
a
vs
code
extension
that
lets
you
view
and
p.m.
A
you
know.
Whatever
tasks
you
have
inside
your
project,
so
let's
work
on
this
and
show
off
how
to
use
the
pull
request
and
issues
view.
So
I
can
go
to
this
github
view
over
here
and
you
can
see.
I
have
two
sections
for
my
pull
requests
and
issues.
So
I
can
click
on
this
and
they'll
actually
just
show
me
all
of
the
open,
PRS
I
have
and
I
can
also
have
them
in
these
specific
categories.
A
With
these
specific
filters,
so
we
have
one
that
I
can
open
it
up
and
view
the
description
of
this,
and
this
view
should
look
really
similar
to
what
it
is
on
github.
You
can
check
out
the
branch
we
heard
that
this
was
something
that
a
lot
of
developers
didn't
do
as
often
as
they
wanted
to,
because
there's
just
so
many
commands
with
git
fetch
and
get
add
this
just
lets.
You
check
out
the
PR
branch
and
tested
out
yourself.
You
can
go
into
and
view
the
actual
dif.
A
So
this
is
really
neat
lets
you
view
the
dif.
If
I
want
to
change
how
I
view
the
DIF
I
can
toggle
the
view
from
this
split
one
to
an
inline,
whatever
you
prefer,
if
I
want
to
I
can
add
a
comment,
looks
good
to
me
and
just
leave
that
and
start
a
review
or
just
add
a
single
comment,
and
then
I
can
also
use
different
ways
to
merge
the
pr,
so
you
can
create
a
merge
commit
or
you
can
use
squash
or
rebase,
whatever
you
prefer
to
do
so.
A
I
can
also
get
a
really
good
integration
with
issues.
So,
if
you're
working
in
a
repository
where
you
maybe
track
feature,
requests
or
bug
fixes
on
issues,
you
can
do
that
from
inside
the
editor.
So
by
default
there
will
be
two
categories
here
listed
my
issues
that
have
been
assigned
to
me
and
then
issues
that
I've
created.
So
if
you
want
to
customize
this
a
bit
further
and
actually
keep
track
of
more
specific,
maybe
labels
or
more
specific
things
that
you've
been
like
assigned
with
keywords
you
can.
A
You
can
do
that
so
I'm,
going
to
click
on
this
pencil
here
and
it's
going
to
open
up
the
settings
for
this
extension,
and
you
can
see
here
all
the
queries
I'm
using
to
populate
this
list.
So,
for
instance,
if
you
prefer
to
keep
track
of
issues
with
a
certain
keyword
or
the
certain
label,
we
can
do
that.
So,
let's
add
one.
Maybe
let's
call
it
feature
requests
and
we
can
add
the
query.
A
The
query
syntax
is
the
same
as
the
one
as
you
would
use
on
github
and
we've
also
added
in
a
couple
of
these
variables,
because
we
can
do
that.
Now
in
vs
code,
so
let's
do
the
current
repository
that
I
own.
This
is
my
repository
and
I'm
gonna.
Do
the
label
feature
request,
because
that's
what
I
use
for
incoming
issues
like
that
and
now
I
get
that
as
well?
A
So
this
is
really
all
about
making
it
really
easy
for
you
to
see
and
keep
track
of
and
not
lose
all
the
different
issues
or
things
that
have
been
assigned
to
you.
So
we
can
also
just
create
issues
and
not
just
manage
them
from
this
extension.
So
if
I
go
back
to
my
readme,
this
is
where
I
sort
of
keep
track
of
all
the
upcoming.
A
Let's
add
a
to
do
to
get
user
test
running
because
I've
been
wanting
to
do
that
for
a
while.
So
the
cool
thing
you
see
here
is
there
was
a
light
bulb
that
popped
up
when
I
did
that
to
do
comment,
so
this
will
give
me
a
suggestion
to
create
an
issue
based
on
this.
To
do
comment
trigger,
but
better
yet
I
can
actually
create
the
issue
and
also
assign
it
to
someone.
A
So
if
I
click
on
at
I
get
a
list
of
all
the
people
that
have
worked
on
my
project
with
me
that
are
on
this
repo
and
I
can
assign
it
to
someone.
So,
let's
assign
it
to
me.
This
is
something
I've
been
wanting
to
do,
and
then
you,
let's
create
the
issue,
get
user
test
running
perfect
all
right
and
that's
what
I
did
it
created
an
issue
over
here?
So
if
I
hover
over
this,
it
gave
me
the
issue.
A
Number
I
can
click
on
it,
go
back
to
it
on
github
and
I
can
also
view
it
now
from
the
same
view
I
saw
earlier.
So
my
issue
is
this:
is
the
new
one
assigned
to
me?
It's
ready
for
me
to
work
on
really
convenient,
really
easy.
I
can
click
on
this
arrow
and
start
working
on
it.
So
now
you
see
I
have
switched
over
to
a
new
branch
for
me
to
work
on
this
issue
and
you
can
change
these
settings
again
from
your
settings
so
JSON.
A
If
you
don't
want
to
open
up
a
new
branch,
you
can
do
that
you
can
choose
whatever
you
want
say:
I
made
a
quick
change.
Let's
make
the
fix.
I
can
go
over
to
my
source
control
view
and
it'll
actually
autofill
the
commit
message
for
me
and
it
will
close
the
issue
when
I
check
it
in
so
this
is
organic,
really
sort
of
closing
the
loop.
A
You
can
open
up
an
issue
search
through
issues
and
then
start
working
on
them
and
just
close
them
from
inside
vs
code,
no
need
for
context,
switching
making
it
really
easier
to
bring
that
outer
developer
loop
closer
to
where
you
are.
Writing
your
code
so
install
this
extension
today.
It's
really
awesome,
really
convenient
and
now
I'm
going
to
go
into
a
demo
of
the
remote
containers
extension.
A
Let's
talk
remote
development,
so
we
started
working
on
remote
development,
extensions
inside
vs
code
about
a
year
and
a
half
ago,
so
well
before
the
impacts
of
coronavirus
and
the
work
from
home
situation.
That
many
of
us
are
in
right
now
back
then
we
were
talking
to
lots
of
developers
and
seeing
more
and
more
of
them
developing
remotely.
A
We
talked
to
companies
that
had
like
huge
mono
repos
that
maybe
didn't
even
fit
on
a
laptop
and
so
developers
would
just
connect
to
a
really
huge
dev
VM
and
nothing
was
really
on
their
local
box
and
they
were
able
to
just
deploy
changes
and
fixes
with
the
VM.
In
a
couple
minutes,
we've
also
seen
more
and
more
that
data
scientists
are
leveraging
really
specialized
VMs
that
have
lots
of
GPU
and
so
that
they
can,
you
know,
run
sessions
on
all
their
huge
data
sets
and
train
all
their
data.
A
So
we
see
that
remote
development
is
now
like
the
norm
for
many
developers
and
especially
given
our
remote
work
environments
we're
doing
a
lot
of
that
now.
So
we
saw
that
existing
remote
experiences
for
development
or
ain't
that
great.
Maybe
you
are
using
remote
desktop,
which
can
be
a
bit
laggy
or
you
were
SSH
into
a
VM
and
using
the
terminal
and
vim.
So
we
wanted
to
bring
a
better
development
experience
to
the
remote
environment
that
you
were
working
in.
A
So
we
created
four
key
remote
extensions
to
be
able
to
work
for
different
scenarios,
remote
development
inside
a
virtual
machine
inside
a
container
inside
WSL
and
most
recently
inside
the
browser.
We
wanted
you
to
be
able
to
develop
in
the
context
of
the
remote
host,
but
still
have
the
richness
of
your
vs
code
experience.
So
what
we
did
was
split
the
vs
code
into
two
components
into
a
UI
component,
which
would
run
on
your
local
machine
and
a
server
component,
which
would
let
you
edit
and
run
and
debug
your
code
on
the
remote
machine.
A
Basically,
the
vs
code
server
can
be
run
anywhere
else
and
the
remote
extensions
would
let
you
communicate
between
vs
code
and
the
server
so
I'm
going
to
show
you
the
remote
containers
extension
and
this
lets
you
develop
in
docker
containers
which,
if
you
really
just
think
about,
is
kind
of
like
another
via
the
power
really
comes
from
the
ability
to
create
an
isolated,
reusable
dev
sandbox
that
you
can
reuse
and
share
with
others.
All
the
remote
extensions
work
in
a
similar
way.
A
A
So
if
you
search
for
this,
you
can
see
this
extension
pack,
which
comes
with
all
three,
the
remote
wsl
containers
and
SSH,
and
then
you
can
separately
search
for
the
extension
that
lets
you
work
inside
the
browser,
so
this
is
called
Visual
Studio
code
spaces
I'm,
going
to
show
off
containers.
So
when
you
have
installed
the
extension
pack,
it's
going
to
contribute
an
icon
to
the
very
bottom
of
your
window
here
and
we're
going
to
try
a
sample
so
before
I.
Do
this.
Let's
talk
a
little
bit
more
about
what
is
going
to
happen.
A
I
have
no
idea
how
to
install
any
of
that
and,
to
be
honest,
I,
don't
know
if
I
want
to,
because
I
feel
like
I'm,
going
to
mess
up
my
machine
or
maybe
installed
the
wrong
compiler
or
install
the
wrong
package
manager.
This
happens
to
a
lot
of
us,
so
we
wanted
to
make
that
easier
to
work
with
the
remote
containers
extension.
You
need
to
have
docker
installed
and
you
see
I
already
have
it
running.
A
So,
let's
open
up
my
local
terminal
to
see
what
I
have
on
my
machine
right
now
open
up
my
terminal,
let's
type
in
to
see
what
version
of
node
we
have
I
have
an
older
version
of
node.
So,
let's
use
the
remote
containers
extension
to
help
us
basically
create
a
sandbox
where
I
can
use
a
specific
version
of
my
tools
and
not
actually
have
to
worry
about
messing
anything
up
on
my
local
machine.
A
So
I'm
going
to
try
a
sample,
remote
containers
and
I'm
going
to
try
the
node
sample,
so
this
is
going.
This
is
a
set
of
repositories
that
we've
already
built
for
you
just
to
try
out
what
it's
like
to
use
this
it's
going
to
build
an
image,
but
I
already
built
it
once
so.
It's
just
going
to
connect
to
the
container
now.
A
All
right,
so
you
see
here
the
vs
code
pretty
quickly
connected
to
this
container.
You
see
on
the
bottom
left
here
that
I'm
inside
this
dev
container.
So
let's
see
what
that
really
means.
This
terminal
looks
a
little
different.
All
right,
it
looks
like
I'm
on
a
Linux
terminal.
I
am
inside
of
a
new
environment.
This
is
different
from
my
local
environment
I'm
on
a
Mac
right
now,
let's
see
what
version
of
node
I
have
all
right:
I
have
any
updated
version
of
node
for
me
to
use.
So
what
happened?
A
Instead
of
running
on
my
local
machine
I'm,
now
running
inside
this
container
I'm
running
vias
code
inside
this
docker
container,
if
you're
not
familiar
with
docker,
it's
a
way
for
you
to
encapsulate
environments
from
the
OS
down
and
then
lets
you
build
more
specific
things
and
layers
on
top
of
it.
So
the
magic
here
is
really
inside
this
dev
container,
so
I
have
this
docker
file.
This
is
a
really
standard.
Docker
file,
I'm
not
really
doing
anything.
Fancy
here,
vs
code
also
doesn't
really
interfere
and
get
get
involved
here.
A
It's
just
telling
docker
hey,
go,
build
this
and
run
the
container,
so
once
the
container
is
building,
then
we're
going
to
inject
a
version
of
the
vs
code
server
in
the
container,
not
the
UI,
just
the
vs
code
server,
just
the
things
that
give
you
language
support,
debugging,
support
things
like
that,
and
now
there's
a
connection
between
my
local
client.
That's
running
my
UI,
so
you
see
here:
I
I
still
have
the
same.
Vs
code
theme
I
had
on
my
local
machine,
so
I'm
running
my
UI
locally,
but
I've
connected
to
this
container.
A
So
now
the
magic
is
in
this
dev
container
does
JSON.
This
tells
vs
code
how
to
setup
my
container
for
me
to
be
able
to
develop
like
I
do
locally.
So
it's
gonna
tell
it's
gonna
point
it
to
the
the
docker
file.
I
want
and
it's
going
to
set
settings
so
I
can
choose
that.
I
want
a
bash
terminal
inside
this
environment
that
I
want
these
specific
extensions.
I
have
the
es
lint
extension
installed.
A
So
you
can
see
here
there's
a
difference
between
the
extensions
I
have
inside
my
container
and
inside
my
local
computer,
and
they
can
also
list
ports
to
forward
so
that
I
can
connect
to
them
locally.
So,
let's
try
running
this.
Let's
just
see
what
happens
where
this
is
a
standard,
Express
app
I'm,
going
to
open
up
the
main
file.
This
is
just
an
Express
app.
You
see,
I
still
get
a
lot
of
the
colorization.
If
I
wanted
to
I
get.
You
know
the
the
autocomplete
things
like
this,
that
I'm
used
to
I
can
get
linting.
A
I
can
get
errors.
This
is
all
things
that
I
can
do.
I
can
set
breakpoints.
So,
let's
just
run
it
f5
see
what
happens
or
it's
running
on
this
local
address
and
I'm
able
to
connect
to
it
like
how
can
I
actually
connect
to
this
address?
From
my
you
know,
local
edge
browser
like
this
is
the
magic
of
remote
development.
You
saw
in
the
dev
container
that
I
set
up
the
ports
I
wanted
to
forward.
You
know.
A
Containers
are
isolated
so
if
I
wanted
to
access
anything
from
inside
the
container
I
needed
to
forward
it,
so
I
can
access
it
from
my
local
host,
so
I
didn't
have
to
set
up
anything
for
this
to
work
right.
We
are
now
in
a
specific
environment
for
me,
with
a
specific
version
of
my
tools.
I
didn't
have
to
set
anything
up
besides
installing
the
containers
extension
and
having
docker
installed.
So
this
is
really
really
cool.
A
All
right,
like
think
about
all
the
cases
of
this,
could
be
used
for
it's
really
great
for
onboarding
people
that
are
new
to
your
team.
So
you
know
we
all
know.
Adding
a
new
engineer
to
our
team
is
expensive.
They
spend
two
weeks
trying
to
figure
out
how
to
set
up
their
computer.
You
have
to
teach
them
how
to
run.
You
know
the
build
tools,
show
them
really
specific
things
to
your
team's
environment,
but
instead
you
can
encode
this
all
in
a
docker
file.
A
No,
you
don't
have
to
spend
weeks
reading
through
all
the
giant
steps
in
your
readme
and
you
don't
have
to
pollute
your
machine
or
install
the
wrong
version
of
something
you
just
pull
any
project
that
has
a
dev
container,
so
vs
code
knows
how
to
connect
to
it
and
you
can
just
build
and
connect
to
the
container.
You
can
also
specify
the
vs
code
set
up
inside
a
dev
container.
This
is
also
really
awesome,
for
maybe
the
education
scenario
think
about
students
learning
to
code
in
their
first
computer
science
class.
A
So
many
of
them
get
discouraged
because
they
don't
know
how
to
you
know,
install
Java
and
the
JDK
and
their
IDE
at
home.
But
if
you
encapsulate
all
the
dependencies
and
setup
inside
just
a
docker
container,
that's
all
they
need
to
know
so.
I
really
want
to
thank
everyone
for
joining
us.
This
was
an
awesome,
awesome
event,
I'm
glad
you
were
all
here
at
open,
j/s,
so
install
the
containers
extension
installed.