►
Description
In this installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen and Waldek Mastykarz (Microsoft) | @waldekm, are joined by US-based Principal PM Lead, DevDiv, VS extensions - Pierce Boggan (Microsoft) | @pierceboggan. Discussion covered career journey and advice, people management, developer experiences - blending pro code and low code, why create apps with Teams Toolkit and announcement of 3 Preview features in Teams Toolkit that will be announced at Microsoft Build 2022. Microsoft and PnP Community delivered 13 articles/videos in the last week! This session was recorded on Monday, May 16, 2022.
References
• See the full blog post for this episode in the Microsoft 365 Platform Community blog at https://aka.ms/m365pnp/blog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365pnp
A
A
Yeah
that
the
age
doesn't
come
alone,
like
they
say
now,
the
16th
of
may
2022
and
in
the
pmp
weekly.
I
always
talk
about
the
latest
on
microsoft,
365,
the
latest
news,
the
the
articles
from
microsoft,
some
of
the
latest
articles
from
microsoft
and
community,
and
we
typically
have
a
visitor
as
well
hi.
My
name
is
a
product
manager
still
transgender
this
product
manager.
B
A
But
let's
jump
on
the
on
the
interview
with
pierce
and
we'll
start
by
him,
introducing
him
him
introducing
himself
and
what
he
actually
does.
So,
let's
jump
over
there
welcome
pierce.
We,
I
guess
in
the
intro
which
we
recorded
earlier,
I
already
called
you
appears
personal.
So
hopefully
you
don't
mind.
A
C
Oh,
my
god,
so
this
question
like
it's
always
like
a
scary
question
like
in
an
interview.
You
know
it's
coming
right
like
who
are
you?
What
do
you
do,
but
I
never
quite
know
how
to
answer
it
so
I'll
give
an
attempt.
So
I'm
pierce,
I'm
a
principal
pm,
lead
working
in
developer,
division,
I'll,
explain
what
that
is
in
a
second
and
our
team
focuses
we
call
our
team,
like
the
client,
app
innovation
team
and
really
like
what
we
think
about
is
like.
C
What's
that
next
generation
of
client
apps
going
to
be,
and
what
I
mean
by
that
is
like
both
in
terms
of
the
properties
of
the
app.
Are
they
going
to
be
more
collaborative
asynchronous
chat
based?
What
does
that
mean
and
then
like?
How
do
I
actually
build
these
apps?
So
it
could
be
pro
code,
it
could
be
low
code,
it
could
be
some
like
in
between
state
and
so
we
partner
with
a
lot
of
teams
inside
of
microsoft.
A
A
C
First
of
all,
like
our
team
partners
with
all
of
the
m365
team
on
developer
experience,
so
I
work
in
developer.
Division
which
delivers
dev
tools
like
bs,
ds,
code
languages
like
net
and
typescript,
and
a
whole
bunch
of
azure
services
as
well,
such
as
azure
functions,
api
management,
logic,
apps,
etc,
and
so
like
we
love
to
work
with
other
teams
inside
of
microsoft
on
their
developer
experience,
so
we
just
partner
together
we're
developers,
I'm
a
developer.
C
I
write
code
and
we
just
want
it
to
be
an
awesome
experience
for
developers
to
build
our
platform.
So,
first
and
foremost,
like
we
partner
with
other
teams,
we
give
feedback.
We
give
suggestions,
we
work
with
other
teams
on
what
exactly
it
means
to
have
a
good
developer
experience
more
concretely
for
m365.
We
built
something
called
the
teams
toolkit,
which
really
is
just
developer
tools
for
building
teams.
Apps.
You
know
if
you're,
building
a
mobile,
app
or
you're
building
a
web
app,
you
have
dev
tools.
C
If
you're
using
vs
code,
you
just
go
to
the
extensions
gallery
and
search
for
teams
toolkit
and
then
we
also
have
a
cli
based
experience,
because
we
know
that
some
people
love
using
cli
and
care
less
a
little
bit
about
some
of
the
interactions
in
the
dev
tools
themselves.
So
those
are
the
three
concrete
things
that
we
deliver
for
m365.
C
I
also
work
with
the
azure
communication
services
team
on
their
developer
experience.
So
if
you
kind
of
think
we'll
get
into
this
a
bit
more
later,
if
you
think
about
teams
as
a
teams
in
m365
platform
as
you're
bringing
your
app
into
a
collaborative
surface
right
where
people
are
already
working,
azure
communication
services
is
almost
the
opposite.
I
can
embed
these
really
collaborative
capabilities
into
my
application,
even
if
it
doesn't
live
inside
of
microsoft
365..
So
we
work
with
the
azure
communication
services
team
on
developer
experience
and
then
something
that
I
do.
C
That
is
a
little
bit
like
newer.
Is
I
work
partner
with
the
power
platform
team
on
something
called
fusion
development,
and
so
basically,
what
this
is
is
we
think:
hey,
there's
low
code,
there's
pro
code,
there's
citizen
developers,
there's
professional
developers
like
we're
better
together
right,
and
so
I
honestly
believe
that,
like
the
overwhelming
majority
of
internal
applications
that
are
built
inside
of
organizations
could
have
some
low
code
components
and
that
can
really
make
developers
more
productive
right
and
so
what
our
team
does
is
we
say?
C
How
can
we
blend
the
best
parts
of
low
code
with
the
best
parts
of
pro
code
right,
and
so
we've
been
working
with
the
power
platform
team
to
really
make
their
platform
really
extensible
for
professional
developers,
so
that
I
can
build
85
90
95
of
my
apple
code,
and
then
I
can
extend
that
last
5
or
10
percent.
I
need
with
either
custom
ui
or
apis
or
custom
logic,
so
working
with
a
lot
of
different
teams
inside
of
microsoft.
C
But
it's
all
kind
of
around
the
central
hypothesis
of
like
the
way
we
build
apps
is
changing
and
like
we
need
to
set
up
developers
for
success
in
in
the
in
the
future,
because
it's
because
everything
is
changing
like
it's
crazy,
because
I
I
entered
developer
space
about
10
years
ago,
I
worked
on
mobile
development
actually
and
a
company
called
xamarin.
Are
you
all
familiar
with
xamarin?
Yes
yep?
I
didn't
in.
C
Yeah
so
so
yeah
like
I
started
working
at
xamarin
before
it
was
acquired
by
microsoft,
xamarin
for
those
that
don't
know,
I
know
you
already
all
know,
but
I'm
going
to
explain.
Anyways
was
cross-platform
mobile
development
in
c
sharp
for
ios
and
android,
and
so
that
was
kind
of
like
my
first
foray
into
building
things
for
developers,
and
so
I
worked
on
mobile
dev
for
quite
some
time
and
now,
I'm
kind
of
like
two
or
three
years
ago.
C
I
moved
over
to
focus
on
what
I
focus
on
now
and
it's
crazy
just
seeing
all
the
changes
that
have
happened
just
in
the
last
couple
years,
honestly
a
lot
of
it
accelerated
by
covid,
but
just
the
requirements
that
developers
have.
You
know
I
spend
so
much
of
my
time
talking
to
developers
like
y'all
on
the
phone
every
single
week
and
just
listening
about
the
scenarios
you
have
they're
vastly
different
than
the
scenarios
we
had.
Even
you
know,
four
or
five
years
ago
for
client
developers.
A
Yeah,
it's
that
the
speed
of
innovation
is
going
significantly
faster
and
faster.
Now,
one
thing
what
I
wanted
to
actually
clarify
is
still
because
we
started
you.
You
explained
that
you're
in
the
azure
side
of
the
house,
and
that
might
be
a
confusing
for
people
who
are
watching
the
listening
broadcaster
watching
the
the
video.
So
it
works
in
the
microsoft
in
a
way
that
the
dev
div,
meaning
the
developer.
Division,
which
is
creating
resource
to
their
code,
is
part
of
the
azure
which,
by
the
way,
makes.
A
I'm
a
minority,
oh
wow,
I'm
the
exception
of
the
this
wow
and
then
then
the
azure,
because
we
of
course
it's
microsoft
cloud.
Everything
in
microsoft
cloud
is
based
on
azure
the
identity,
data
authentication,
everything
else
and
then,
of
course,
the
microsoft
trees.
Sd5
is
using
azure
behind
the
scenes
as
a
sas
service.
C
Yeah-
and
I
mean
I
think,
one
of
the
like
things
I
joined
microsoft
in
2016
and,
of
course,
microsoft
had
a
reputation
before
that
of
not
being
the
most
collaborative
but
like
ever
since
I've
joined
microsoft,
which
has
all
been
under
satya
like
it's
been
very
collaborative,
and
I
think
one
of
the
cool
things
that
I
really
enjoy
is
like.
We
all
get
to
use.
I
believe,
like
every
single
person
has
a
superpower
and
that's
true
for
organizations
as
well
like
they're.
C
C
What
is
it
like
building
like
something
that
what
200
something
million
people
use
every
single
day,
like
that's,
even
crazy
to
think
about
in
terms
of
skill
right,
and
so
you
get
to
learn
things
and
take
things
from
everybody
else,
and
then
they
get
to
use
my
expertise
as
well.
So
I
think,
like
that's
kind
of
like
almost
like
a
hidden
benefit
of
working
at
microsoft,
is
you
get
to
tap
the
brain
of
all
the
really
smart
people
all
over
the
company.
A
A
Yeah,
it's
almost
like
a
series
of
individual
startups
which
are
then
collaborating
and
connecting
and-
and
it's
actually
it's-
it's
I've
been
here
now
15
and
a
half
years,
or
something
like
that
started
in
2006
in
a
bit
different
role.
First,
but
it's
it's
been
amazing
to
see
the
the
chains
in
the
company
because
I
joined
when
steve.
Well,
no
bill
gates-
I
don't
know,
but
anyway,
steve
ballmer
was
different.
Bill
gates
was
different.
A
I
can't
remember
anymore,
you
know
age,
but
but
it's
it's
good
to
see
that
we're
heading
to
a
direction
where
we
are
seriously
one
microsoft,
we're
building
stuff
together.
The
mental
mindset
is
completely
different
and
it's
it's
it's
actually
the
fact
that
we
target
all
of
the
devices
all
of
the
platform
we
do
not
discriminate.
A
So
so
peter
something
like
we
talked
about
before
we
before
you
actually
started
explaining.
What
are
you
doing
and
where
you
come
from
you,
you
actually
pretty
like
well
time
flies
when
you're
having
fun
right,
but
you
moved
from
a
role
to
a
different
role
inside
of
microsoft,
so
you
moved
to
a
manager
role
and
I
started
actually
having
a
really
great
discussion
on.
A
C
Oh
yeah
yeah,
I
mean,
I
think,
like
intellectually,
you
know
before
you
step
into
that
role.
What
does
a
manager
do
what's
their
job?
What
does
their
schedule
look
like?
They
have
a
lot
of
meetings.
You
know
you
have
some
intellectual
understanding
of
what
that
role
is,
and
I
wrote
there
was
two
really
really
great
books.
I'll
have
to
tell
you.
One
of
them
was
making
of
a
manager
and
there's
another
one.
That's
a
little
bit
more
tactical,
and
I
read
both
of
those
before
I
got
started,
which
you
know.
A
C
That's
kind
of
what
it
was
like
that
first
year,
as
a
lead,
you
know
I'll
be
honest.
Like
I
had
you
know,
I
had
really
bad
anxiety,
a
panic
attack
things
like
that
that
first
year,
because
there's
a
whole
nother
class
of
issues.
You
know
when
you're
an
individual
contributor
you're
focusing
on
okay.
How
do
I
move
the
product
forward,
basically
every
single
day
right
and
then,
when
you
become
a
lead,
there's
this
whole
other
like
surface
level
like
of
issues
right?
How
do
I
build
an
awesome
team?
C
How
do
we
have
an
awesome
team
culture?
What
values
are
important
to
us?
How
do
I
help
all
the
people
on
this
team
achieve
their
career
goals?
So
there's
like
a
whole
bunch
of
you
know,
team
and
people
related
issues
is
not
really
the
right
thing
to
say,
but
concerns
to
think
about.
When
you
become
a
lead-
and
I
think
like
perhaps
the
thing
that
really
makes
sense
when
you
say
it
out
loud
but
like
you
didn't
really,
I
didn't
really
think
about.
C
When
I
became
a
lead,
is
you
have
much
less
time
for
some
of
the
things
you
used
to
love
about
being
an
individual
contributor
right,
like
I
just
have
way
less
time
for
writing
code,
and
I
had
to
make
a
ton
of
time
for
that
it
very
intentionally
like
before
I,
I
would
always
have
time
to
write
code
right.
I
didn't
have
to
say
you
know.
Pierce
is
going
to
make
a
calendar
of
it
for
writing
code
from
2
to
3
p.m.
Right.
C
Not
always
perfect,
because
usually
something
does
almost
always
come
up,
but
almost
every
single
friday
I
spend
from
noon
until
I
leave
work
writing
code
and
you
know,
especially
when
you're
working
in
a
technical
field.
I
think
you
know.
Certainly
I
don't
have
to
be
like
the
most
like
you
know.
I
don't
have
to
be
the
architect
who
understands
how
everything
works
and
everything
like
that,
but
I
do
think
it's
really
hard
to
have
an
empathy
for
your
end
users.
Yes,
I
talk
to
customers
all
the
time.
C
Yes
I'll,
look
at
the
data
but
like
using
the
product
yourself
and
feeling
all
the
same
pain
and
delight
that
your
customers
feel
that's
an
entirely
different
experience,
and
so
there's
things
like
writing
code
that
when
you
become
a
lead,
you
really
have
to
be
intentional
about
making
time
for
yeah.
But
I'll
say,
like
you
know,
it
was
a
rough
experience
at
first
because,
like
yeah,
there
was
just
so
much
and
there's
so
many
problems
that
come
up
constantly.
You
know,
like
you,
had
all
your
problems
and
now
it's
like
times.
C
C
I
had
some
great
mentors
here
at
microsoft,
who
really
helped
me
through
that
phase
and
kind
of
set
my
expectation
hey
it's
going
to
be
a
little
bit
of
a
rough
time,
your
first
three
six
months
as
a
lead,
but
you'll
settle
in,
and
they
help
me
coach
me
through
some
of
the
challenges
that
I
was
having
and
obviously
having
a
really
good
manager.
Yourself
also
helps
with
that.
So
yeah.
C
C
So,
prior
to
joining
microsoft,
I
had
a
software
engineering
title.
I
did
have
a
software
engineering
degree
which,
at
my
university
basically
was
a
computer
science
degree
with
more
math,
and
you
know
physics
and
things
like
that.
That
wasn't
required
for
the
cs
program
said
to
take
a
ton
of
math
classes,
which
of
course
I
never
used,
and
I
had
to
take
like
engineering
like
statics
and
dynamics
and
stuff
like
that,
which
you
know
was
neat
but,
like
I
don't
know
how
applicable
that
is
to
my
day
to
day,
but
I'll
laugh.
B
C
Story
for
a
lot
of
a
lot
of
us
in
this
field.
I
was
really
interested
in
world
of
warcraft
when
I
was
growing
up
and
so
like
not
kosher
but
like.
I
was
really
into
like
private
servers
and
things
like
that.
So
I'd
like
set
those
up-
and
you
know
you'd-
have
to
set
up
a
database
and
compile
this
private
server
and,
like
all
this,
I
didn't
know
what
I
was
doing
but,
like
I
learned
some
of
the
because
it
worked
and
that's
what
it
did
work.
I
didn't
know.
C
C
It
was
in
that
startup
phase.
So
one
thing
I
really
appreciated
about
that
was
I
got
to
like
wear
all
the
hats
like.
Yes,
I
had
a
software
engineer
title,
but
if
someone
needed
to
go
to
a
conference,
I
go
to
the
conference.
If
someone
needs
to
jump
on
a
sales
call,
I
jump
on
the
sales
call.
Someone
needs
to
write
a
doc,
I'd
write
a
doc
and
then,
when
I
joined
microsoft,
I
became
a
pm
and
I
will
say
that
that
exclusion,
so
I
was
never.
I
was
never
like.
C
You
know
the
best
stock
writer,
the
best
sales
person,
the
best
software
engineer,
but
like
the
fact
that
I
had,
I
really
understood
what
each
of
those
roles
was
and
how
they
functioned.
When
I
became
a
pm.
Okay,
part
of
my
job
is
to
get
the
best
out
of
all
the
people
around
me
right,
and
so
I
understood
all
of
the
purposes
of
all
those
roles
which
a
lot
of
people
get
very.
They
stick
to
what
they
know
right
like
they
don't
lean
into
that
discomfort
of.
I
don't
know
like
how
sales
works.
C
I
don't
know
how
marketing
works.
I
don't
know
how
to
write
code,
and
if
you
lean
into
that
discomfort,
I
find
that
there's
a
lot
of
growth
there,
because
a
lot
of
people
just
hide
in
what
they
know
and
that's
really
not
where
most
of
the
growth
is
going
to
come
from.
Certainly
I
have
superpowers
and
I
need
to
lean
into
my
strengths,
but
like
also
having
awareness
of
all
these
other
business
functions
really
served
me
well.
C
So
then,
after
I
joined
microsoft,
I
was
a
pm
on
xamarin,
then
all
of
our
mobile
developer
tools,
which
included,
react
native
and
a
partnership
with
the
team
over
at
facebook
and
also
apache
cordova,
and
so
I
worked
on
that
for
several
years
and
then
in
2020
you
know.
Sometimes
you
just
need
a
change
like
there's.
No
there's
nothing
like
wrong
right,
but
you're
like
I've,
been
doing
mobile
development
for
10
years.
C
C
I
guess,
like
the
platform
itself
was
growing
a
lot
and
we
needed
more
people
working
on
it,
and
so
I
moved
over
to
focus
on
specifically
teams
and
teams,
developer
experience
and
then,
over
the
last
few
years,
that's
grown
to
encompass
all
of
them,
365.
so
yeah.
That
was
a
little
bit
of
a
scary
thing.
C
C
C
There's
awesome
people
all
over
the
place
and,
like
I
started
to
forge
like
lots
of
new
bonds
like
with
y'all,
obviously
with
the
new
team
that
I'm
on
all
throughout
devdiv
cnai
microsoft.
So,
like
you
know
I,
I
was
really
scared
of
the
people
aspect,
but
I
think
it
ended
up
being
a
great
moment
of
growth
for
me,
because
I
got
to
meet
all
these
new
people
that
I
would
have
like
never
met.
If
I
just
stayed
with
my
comfort
existing
this
is
my
social
circle
bubble
right,
yeah.
A
Yeah
yeah,
that's
always
good.
It's
almost
like,
oh
in
a
different,
maybe
a
decade,
but
it's
almost
like
the
same
as
in
in
people
were
at
some
point
in
sharepoint,
because
we
come
from
a
sharepoint
background.
Well
like
it
doesn't
do
that.
We
do
that.
That
often
nowadays,
because
it's
a
bit
different.
A
So
but
it
used
to
be
the
on-premises
people
banging
our
head
against
the
wall
during
the
weekends,
you're,
doing
server,
search
to
server
upgrades
and
all
of
that
stuff,
and
you
have
that
connection
between
the
community
and
ecosystem
and
of
course,
all
of
that
is
now
changed
and
evolved
to
be
microsoft,
racist
divine.
But
if
you're
against
the
chains,
then
that
might
be
much
more
difficult
to
do.
A
B
Yes,
yeah
and
it's
and
it's
also
an
interesting
space.
You
pick
right
because,
like
you,
you
picked
another
space
to
meet
new
folks
and
you
picked
m365,
which
is
a
big
place,
because
there
is
teams,
there
is
grav,
there
is
sharepoint,
there
is
viva,
there
are
apis.
There
are
experiences,
there
is
graph
like
there's,
that's
actually
good
did.
C
But
like
I
definitely
didn't
realize
like
just
how
much
there
was
in
the
platform
when
I
joined.
That
was
definitely
like
a
a
learning
experience
for
me
and
I
think
it's
been
great
actually
because
I've
been
able
to.
You
know
going
back
to
the
super
power
thing
and
I
think
everyone
has
their
own
perspective
and
you
can
learn
from
it
like
a
lot
of
people
have
been
in
the
in
365
world
for
a
long
time,
and
so
when
I
have
questions
about
why
things
are
the
way
they
are.
C
C
I've
never
even
used
the
microsoft
graph
before
I
joined
this
team
and
so
like
that
whole
world
was
kind
of
like
a
black
box
to
me,
and
so
I
actually
think
I
also
brought
a
new
perspective
to
all
of
you,
because
it's
like
hey,
I'm,
not
part
of
your
community
before
I
never.
I
didn't
know
about
all
these
products.
C
C
But
you
also
become
very
shielded
to
the
newcomer
perspective
because
you
don't
think
like
they
do
anymore
right
and
so,
when
you're
joining
a
new
team,
that's
one
of
the
most
powerful
things
you
can
do
is
provide
that
perspective
and
so
really
lean
into
that.
I
would
also
say,
like
my
other
thing,
that
I
still
do
with
vesta
and
you
wall
back
all
the
time
is
I'm
like
I'm
I'm
new.
I
don't
know
how
this
works,
like
lean
into
that
I'm
new
thing.
B
What's
happening,
that
is
a
very
interesting
point
right
because,
like
you
would
almost
think
like,
why
don't
we
have
a
thing
where
you
know
like?
Let's
switch
people
across
team,
let's,
let's
like
and
circle
internship
like
for
a
month,
I
would
go
to
a
different
team,
be
there
and
ask
all
these
things
just
to
make
them
aware
like
like.
B
Oh
damn
like
we
didn't
know
that
that's
a
thing
because
exactly
it
is
the
blind
spots,
you'd
develop
or
you
actually
work
around
in
a
way,
because
you
know
your
way
around
things
like
you
know
the
right
words
to
use
places
to
go
to,
and
people
who
are
new,
don't
like
they
don't
have
that
the
muscle
built
yet
right.
So
I
think
that
that
would
be
as
a
concept
invaluable
right
like
for
semester
or
unknown
like
they'll,
be
probably
too
long
but
like
a
month
or
two
like
just
to
have
somebody.
C
Which
is
a
great
idea
right,
like
you,
can
do
an
informal
version
of
this
and
I'll.
Do
this
all
the
time
like
sometimes
on
those
friday
days,
like
yeah,
of
course,
I'm
building
teams
apps,
I'm
building
in
365
apps,
I'm
using
graph,
I'm
using
sharepoint,
but
occasionally
I'll
just
use
something
random
like
from
another
team.
I'm
like
hey
I've
been
really
interested
in.
C
You
know
azure
container
apps,
I
don't
know
anything
about
containers,
okay,
let's
dive
in
and
like
I'll,
spend
a
friday
doing
that
and
I'll
type
up
that
same
report
that
I
just
mentioned
that
I
asked
people
who
joined
my
team
to
do
and
send
it
over
them.
And
you
know
what
you
do
you
make
a
new
friend
they're
like
wow.
This
is
really
great
onboarding
feedback.
I
really
appreciate
it
now.
C
I
have
a
friend
on
the
container
app
scene
because
I've
just
done
that
and
so,
like
I've
discovered
a
new
technology,
I've
learned
something
new
and
I've
made
new
friends.
So
it's
something
you
have
to
be
intentional
about,
but
you
can
definitely
do
informally,
even
if
your
company
doesn't
have
like
a
more
formal
rotation
program.
C
A
But
you
can
actually
find
a
new
career,
new
jobs
and
new
opportunities,
just
by
providing
structural
feedback
and
constructive
feedback
and
all
of
a
sudden
people
are
like.
Would
you
like
to
be
involved
so
and
employed
in
our
company,
because
again
people
can
prove
their
value
in
open
source
as
well?
So
for
sure
this.
C
Is
this
is
like
the
concept
yeah?
I
believe
that
in
life,
like
luck,
plays
a
big
percentage
for
sure.
However,
I
also
believe
you
can
create
your
own
luck
and
I
think
that's
a
great
example
of
you
know.
What
we
just
talked
about
is
an
example
of
that
like
if
I
expand
my
network
and
I
make
new
connections,
and
I
try
new
things
yeah.
C
Maybe
it
will
amount
to
nothing
but
yeah,
like
you
said,
maybe
you
know
that
new
team
is
hiring
a
needs,
a
new
pm
manager
and
then,
like
I'm,
gonna,
go
over
there
because
they
know
me
already
and
they
know
my
work
and
like
so
you
can
create
your
luck
to
some
extent.
By
just
being
curious,
I
think
that's
a
great
attribute
and
something
I
really
look
for
when
I
hire
people
for
our
team
is
like.
Are
you
just
curious?
Are
you
really
like
excitable?
C
A
Absolutely
absolutely
and
of
course,
to
be
fair,
we
always
need
multiple
kind
of
people.
So
it's
okay
not
to
be
always
the
the
first
in
line
on
doing
everything
and
jumping
on
things,
because
we
need
different
kind
of
people
having
that
diversity
across
the
world
yeah.
But,
as
I
said
that
the
good
will
typically
comes
back,
it's
the
karma
is
is
a
real
thing.
It
might
come
back
in
in
one
and
a
half
years.
Somebody
says
and
says
your
name
you're
applying
now
and
says:
hey.
So
oh
this
one
was
the
guy
who
are.
B
C
Well-
and
that's
actually
a
great
point
like
that's,
why,
like
like
it's
always
important
like
because
people
do
remember
those
things
and
like
it's,
why
it's
always
good
to
treat
people
with
kindness
and
respect
and
all
of
those
things,
because
you
could
have
a
hundred
great
moments.
But
if
you
have
one
bad,
one
people
remember
the
bad
one,
and
so
I
think
like
if
you're
just
a
decent
human
towards
others,
then
like
people
will
remember
that.
A
A
About
it
exactly
so,
what's
the
the
three
top
call
things
in
the
team's
toolkit
which
is
about
to
get
released
pretty
soon,
I
guess
so.
It's
just
a
data
already
available.
This
previous
stuff
is
available.
It's
all
open
source,
which
is
by
the
way
like
awesome,
it's
all
available
already
so,
which
is
great,
but
once
they're
like
the
three
or
five,
the
top
called
coolest
thing
in
the
team's
toolkit.
Why
would
why
would
a
developer
should
be
interested?
Why
would
they
be
interested
in
looking
into
that.
C
For
sure
yeah,
so
I'll
talk
about
some
of
the
things
that,
like
we
already
hear
great
feedback
on
both
from
the
open
source
community
and
some
of
our
customer
conversations
we
have
so.
The
first
is
like
I
think:
if
you're
haven't
taken
a
stab
into
building
teams,
apps
yet
or
m365
apps
just
go.
Try
the
toolkit
create
a
new
app.
You
can
start
from
a
sample.
C
So
if
you're
like
more
of
a
samples
person-
sometimes
I
am,
it
depends
on
what
I'm
approaching
or
you
can
start
from
a
new
code
scaffold
and
you
can
just
start
there.
So
the
feedback
that
we
get
is.
This
is
the
easiest
way
to
get
started
with
developing
for
the
platform.
So,
if
you
haven't
already
taken
a
dive
into
building,
apps
go
try
it.
So
that's
for
a
lot
of
reasons.
I
think
like
what
you
said
earlier.
You
know
the
strength
of
our
platform
is
just.
C
We
have
so
much
breadth
and
depth,
but
it
also
can
be
a
little
overwhelming
if
you're
new
right,
it's
just
a
lot
of
concepts
to
learn,
and
so
I
think
the
team
toolkit
does
a
really
good
job
of
exposing
you
to
those
concepts
at
the
right
time
without
showing
you
it
all
at
once
right.
So
that's
one
thing.
I
think
the
second
thing
is
our
dev
loop.
So
like
something
what
I
mean
by
that
is
like
most
of
our
days,
software
developers
is.
I
write
some
code.
C
C
So
that's
the
thing
we
get
really
good
feedback
on
as
well
with
team
toolkit,
and
then
we
also
have
a
related
way
to
do
cloud
development
so
essentially,
when
you're
building
teams
apps
almost
always
these
are
going
to
have
some
cloud
or
back-end
component
right
and
so
something
you
can
do
is
you
can
add
both
m365
and
azure
cloud
resources
to
that
project.
We
will
manage
those
resources
via
something
called
biceps,
so
you
have
this
transparent
infrastructure
as
code
all
they're,
all
scripts
they're,
all
right.
C
There
we'll
manage
this
for
you,
as
you
add,
and
remove
resources
from
your
project,
such
as
like
an
azure
function
or
an
azure
sql
database,
and
then,
basically
with
one
click,
you
can
provision
and
deploy
those
resources
or,
if
you're,
in
a
company
where
you
know
as
a
developer,
you
have
a
more
locked
down
production
environment.
You
can't
do
that.
Well,
the
great
thing
about
infrastructure
is
code.
Is
you
can
take
those
scripts
give
them
to
your?
You
know,
deployment
engineer
and
your
deployment
engineer
can
just
deploy
them
for
you.
C
So
that's
the
really
nice
thing
about
the
way
we've
done.
It.
We've
simplified
cloud
development
by
not
having
you
to
think
about
all
this
configuration
how
these
things
all
tie
together,
but
at
the
same
time
we
still
give
you
all
the
flexibility
of
like
this
thing
is
in
a
black
box.
You
can
take
these
scripts
and
you
can
hand
them
off
to
someone
and
they
can
deploy.
So
that's
what
team
toolkit
does
today
what's
coming
up,
so
I'm
gonna,
let
everybody
in
the
pmp
audience
up
on
some
secrets
that
are
coming
out
soon.
C
So
what
are
we
releasing
at
build
I'll,
go
ahead
and
tell
you
the
build
is
on
github,
you
can
go
download
it
nothing's
private
and
I'm
an
open
book.
So
we'll
talk
about
it.
The
big
thing
is
scenario
driven
development.
So
what
I
mean
by
this
you
know
if
I'm
building
a
teams
app,
I
have
a
tab.
I
have
a
bot,
I
have
a
message
extension,
these
are
extensibility
services,
but
those
are
just
what
the
platform
offers
in
terms
of
me
as
a
developer,
to
go.
C
Do
things:
what
do
I
do
with
those
things?
So
we've
created
a
whole
bunch
of
scenario-driven
templates,
namely
around
notifications,
and
what
we'll
call
command
and
response
style
box.
So
notifications
are
something
happens
in
my
business
post
to
a
team's
channel
right,
and
maybe
I
can
act
on
it.
We
find
these
scenarios
are
really
popular
command
and
response
is
like
flash
commands
like
a
lot
of
chat
up
style
applications
follow
this
pattern.
Of
course
you
did
already
build
these
things
with
with
our
platform
today,
but
using
the
scenario
templates.
C
We
have
we've
really
simplified
it
a
lot.
You
don't
have
to
be
a
bot
expert
to
build
these
sorts
of
apps,
it's
very
minimal
code.
You
basically
hit
your
api.
You
present
some
data
and
an
adaptive
card
and
we
handle
the
rest.
So
it's
it's
actually
quite
simple
to
get
started
and
this
is
all
available
on
github.
The
other
thing
that
we've
been
working
on
quite
a
bit
is
our
integration
with
other
m365
services.
A
C
So
you
know
that's
a
good
process
and
a
lot
of
customers
are
really
comfortable
using
that
some
can't
use
it
for
ip
reasons
and
the
configuration
also
if
you're
new
is
a
little
non-intuitive.
So
essentially,
what
we'll
offer
is
like
if
you're
building
something
that
would
require
a
tunneling
integration
when
you
have
five,
it
just
works
and
that's
pretty
cool.
So
this
is
going
to
be
using
a
lot
of
the
same
tech
that
we
used
when
we
built
github
code
spaces
and
the
debugging
experience
for
that.
C
We've
integrated
that
into
the
toolkit
so
that
you
can
f5
and
you
won't
even
have
to
think
about
tunneling.
It
just
works
which
is
really
really
awesome.
That's
part
of
our
integrated
f5
experience,
so
that
will
be
available
as
a
preview
at
build.
I
don't
know
if
it's
in
the
github
builds
exactly
worse
manager
ever
worst
product
lead
ever
don't
know
if
it's
in
the
actual
build
today,
but.
C
A
A
A
Microsoft
viva
involved
there
as
well,
because
we
do
have
tooling
on
it
and
all
of
that
so
so,
but
again
naming
naming
changes
are
always
hard.
I
know
a
lot
of
mvps
who
had
their
their
feelings
so
immediately
like
bad
feelings
and
another
renaming,
because
it's
always
so
hard
anyway,
but
maybe
maybe
we'll
see
maybe
yeah.
I
have.
A
Yeah
exactly
and
we
need
to
keep
on
evolving
evolving.
This
is
a
evolution,
so
one
step
at
a
time
to
what
it's
in
I've.
I
love
this
word,
which
is
not
an
actual
word
in
english,
which
is
being
improvingist
so
rather
than
trying
to
be
a
perfectionist,
be
an
improvementist
which
is
basically
don't
even
try
to
be
perfect
because
nobody's
perfect.
Nothing
is
perfect,
but
and
one
stupid
time
improving,
improving,
improving
I
head
into
the
right
direction.
A
B
We
talked
about
it
already,
and
I
mean
we
could.
We
could
stay
here
for
probably
for
another
hour
or
two
yeah.
I
think
that
gives
us
more.
The
reason
like
once
things
settled
you
know,
does
settle
for
a
part
and
we
are
after
build
like
let's
get
back.
Let's
talk
more,
you
know
like
when
you're
doing
next
rev
on
what
you've
learned,
what
you've
heard
new
plans.
B
C
Of
course,
yeah
and
community
members
like,
if
you
have
feedback
like,
of
course,
you
can
always
leave
feedback
on
github.
You
can
also
I'll
give
my
email
you
can
reach
out
to
me
directly
pierce.bogan
at
microsoft.com.
Send
me
an
email
with
your
feedback,
good
bad
neutral.
Whatever
I
really
like
you
said
earlier,
like
you
know
it's
hard
to
do
what
we
do
without
your
feedback
that
this
this
toolkit
is
driven
by
your
input
and
so
to
make
a
really
awesome
product.
A
Awesome
awesome
awesome
and
I
and
I
love
the
energy
by
the
way
I
have
to
say,
because
we're
doing
the
right
thing,
we're
heading
to
the
right
direction
and
there's
a
lot
of
positive
energy.
It's
always
good,
so
really
really
cool,
but
thanks
peers
for
joining
and
from
here
we'll
jump
in
the
podcast
and
in
the
video
looking
good
the
weekly
articles.
But
thank
you
pierce
awesome
to
have
you
on
the
call.
A
B
A
B
B
A
B
Exactly
so
there
there
is
a
new
article
from
aicha
who
is
a
colleague
of
mine
and
in
this
article
she
talks
about
the
concept
of
collaborative
apps,
so
real
time
or
apps,
in
which
you
can
work
with
others
real
time
in
real
time.
You
can
see
changes.
You
can
see
what
everybody
does,
which
gives
really
this
dynamic
experience
and
you
get
up-to-date
all
the
time
as
opposed
to
you
having
to
do
something
refresh
wait
to
realize.
No,
no,
you
get
to
see
changes
real
time.
B
So
it's
really
cool
technology
and
scenario
because,
as
we
collaborate
more
and
more
remotely
where
everybody
is
behind
the
screen
and
that
technology
gives
you
this
ability
to
have
more
or
a
richer
experience
and
have
the
feeling
that
we're
collaborating
it's
a
real-time
thing,
as
opposed
to
asynchronously
doing
things.
So
definitely.
A
B
A
A
How
do
you
publish
so
much
of
themselves
to
the
stores
or
what
are
the
steps
on
how
to
make
that
happen,
and
how
do
you
sign
up
for
the
partner
center
and
all
that
stuff,
so
really
really
cool
video
as
well,
which
is
getting
a
lot
of
use
in
the
microsoft
365
developer
channel,
so
really
really
good
and,
of
course,
references
on
all
of
the
different
articles
and
then
the
the
third
one
in
here
was
from
office
team.
Yes,.
B
Exactly
so,
we
announced
a
change
in
office
add-ins
how
you
execute
functions
in
function,
add-ins
right.
So
if
you've
built
an
add-in
that
calls
function,
there's
a
change
in
how
we
go
about
it,
how
you
register
that
and
build
that.
So,
if
you
are
in
this
space
check
this
announcement
out
to
ensure
that
your
add-ins
will
work
and
these
changes
must
be
made
before
october
30
2022.,
so
you
still
have
some
time,
but
before
you
go
on
holiday,
you
might
want
to
add
yourself
a
reminder
that
you
keep
that
that
in
mind.
A
Yep
really
really
good
good
reminder
for
sure,
and
then
there
was
an
update
on
the
office,
a
javascript
api
for
power,
query
read-only
data
now
available
for
excel,
and
this
is
basically
querying,
for
example,
the
items
and
then
manipulating
with
the
items
in
the
script.
So
that's
now
available
in
the
excel
site,
so
really
cool
to
see
more
and
more
features
across
the
stack
in
the
office
and
inside
as
well,
and
then
we
had
something
related
on
modernization
exactly
so.
B
Talking
more
about
office
in
the
past,
you
might
have
built
an
app
with
access
nowadays
has
been
move
to
power
platform,
powerapps
dataverse.
You
might
want
to
use
this
or
have
the
same
app
available
on
the
cloud
for
everybody.
So
there
is
now
a
way
for
you
to
migrate
your
access
app
to
power
platform
dataverse
and
to
have
to
use
more
the
power
of
the
cloud
for
your
line
of
business
apps.
So
if
you're
in
this
space,
if
you
have
access
apps
that
you
would
like
to
migrate
to
the
cloud
check
this
out.
A
And
that's
actually
really
cool
that
there's
even
an
export
to
dataverse
option
available
directly
in
access.
That's
actually
really
really
cool
super
clean
setup
to
get
started.
Now
we
we
did
have
a
new
blog
post,
also
related
on
a
new
maintainers
in
the
microsoft
trees
is
the
cli
for
microsoft,
365
team.
You
can
actually
talk
about
this
one.
Yes,.
B
Definitely
so
cli
has
been
around
for
a
few
years
and
as
we
grow,
you
know
we
get
more
users
more
folks
who
contribute
and
that's
really
awesome,
because
it's
cool
to
see
that,
on
the
one
hand,
it's
a
tool
that
thousands
of
folks
use
every
day
in
their
work.
But
it's
also
cool
to
see
that
there's
also
this
other
side
to
it,
where
we
created
a
space
for
folks
to
get
experience
with
open
source,
engage
with
that
community
that
way
to
contribute.
But
all
of
that
requires
you
know,
time
and
time
and
attention.
B
Really
they're
going
to
work
with
us
to
review
prs,
respond
to
issues
basically
take
care
of
the
project
so
that
we
can
help
more
folks
and
bring
also
more
folks
on.
So
this
is
a
really
exciting
news
that
is
just
a
part
of
you
know
the
way
how
we
evolve
over
time
and
try
to
grow
and
create
a
stable,
sustainable,
open
source
project.
Yep.
Absolutely.
B
A
Good
to
see
that
the
growth
of
the
team
and
getting
more
people
involved
and
and
with
us
and
great
to
have
adam
and
martin
involved
in
this
overall
open
source
initiative.
So
thank
you
for
that.
Now,
then,
later
on,
open
source,
stephan
power
had
a
some
great
news
related
on
h2o,
where
version
1.0
is
out,
and
I
think
his
his
personal
twitter
account
was
saying
that
he
overcame
the
anxiety
of
releasing
1.0
so
which
is
osu
and
say
if
you
build
something
by
yourself.
A
A
A
B
Really,
really:
cool,
really
cool,
so
exciting
news
and
congrats
right,
because
it's
it's
a
huge
thing
and
it's
also
a
commitment
thing
right,
like
you
basically
say
we're,
we
are.
We
are
at
the
place
where
we
are
not
going
to
change
anything
big
because
we're
in
a
v1
right.
So
whatever
is
there
is
solid,
it's
ready
to
use
and
you
can
expect
for
that
to
stay
stable
for
time.
A
B
Yes
exactly
so,
he
built
build
an
extension
that
if
you
write
a
script
using
cli
from
or
script
that
uses
cli
from
microsoft,
365
in
vs
code,
with
this
extension,
you
will
get
intellisense.
You
will
get
kind
of
this
hints
about
hey.
I
want
to
run
this
command
and
you
will
get
examples
or
the
whole
blueprint
like
what
commands
or
what
arguments
is
expect,
what
options
and
so
forth
and
so
on.
So
if
you
build
scripts
that
use
cli
for
microsoft,
365,
this
extension
is
really
invaluable.
B
It's
going
to
save
you
so
so
much
time
because
you
would
not
need
to
have
you
know
this
other
browser
window
next
to
it.
Looking
up
docs
all
the
time.
No,
you
will
get
intelligence
directly
in
vs
code,
where
you
build
your
script.
So,
if
you're
in
this
space,
if
you
use
you
like
to
build
script,
check
it
out,
yep.
A
A
A
That's
like
that's
like
dinosaur
h
in
the
yes
in
it.
It's
it's
been
84
years.
Yes,
exactly,
but
anyway,
on
this
article,
robert
talks
about
if
you're
looking
into
doing
a
development
of
additional
commands
for
cli
for
microsoft
traces
device,
how
would
you
actually
do
debugging
and
testing
out
those
commands,
as
you
do
development
in
in
typescript?
Is
it
the
type
script?
How
do
you
do
a
development.
B
So
it's
all
in
typescript,
it's
all
strongly
typed.
You
know
you
get
design
time
type
safety
features
intellisense
for
types.
All
of
that,
but
then
again
like
when
you
write
the
code
you
want
to
be
able
to.
You
know,
set
debugger
and
step
through
the
code
and
robert
also
in
an
awesome
way
explains
with
screenshots,
with
images
explains
all
that,
like
hey.
How
do
you?
Where
do
you
go?
What
do
you
need
to
set?
What
do
you
need
to
change
where
arrows
point
to
like
every
single
place?
B
A
B
Yes,
it's
like
I've
been
reading,
chris's
blog
for
years,
really,
like,
I
think,
since
2007,
and
he
has
this
really
awesome
way
that
when
he
writes
you
know,
he
really
takes
his
time
to
take
a
topic
really
dive
through.
It.
Explain
everything
with
nice
images
so
that
you
don't
just
have
like
a
paragraph
of
text
like
hey,
there's
a
new
thing,
but
why
what's
the
reasoning
behind
it?
How
would
you
use
it
all
the
thinking
so
so
that
you
can
truly
understand
the
idea
behind
it
and
then
apply
it
to
your
work?
Yep.
A
Absolutely
absolutely
and
sharepoint
syntax
is
really
really
cool,
so
we
just
need
to
get
it.
To
be
honest,
we
need
to
get
it
into
developer
tenants
so
that
the
developers
start
can
start
using
that
as
well
more
easily.
Right
now,
that's
unfortunately
not
the
case,
but
it's
surprisingly
powerful.
You
can
do
so
much
with
the
machine.
Imagine
intelligence
which
we
are
under
the
machine
learning
and
and
the
intelligence
what
we
have
with
the
sharepoint
syntax,
so
really
really
cool
stuff.
A
A
Does
it
actually
work,
and,
and
how
do
you
make
that
to
be
used
within
the
spfx
components
and
so
really
really
cool
summary
again
on
on
showing
how
to
make
things
happen,
and
it
is
actually
quite
easy.
It's
a
really
really
cool
control
as
well,
and
then
the
final
and
the
last
video
was
from
april
dunham
related
on.
A
Yes,
yes,
that
is
correct.
It's
about
adjusting
what
are
those
buttons
which
we
see
over
there
and
now
that
we
actually
support
of
removing
them,
which
is
actually
really
really
cool.
So
you
can
use
the
json
definitions
to
define
and
target,
for
example,
the
individual
buttons
and
then
say
it
goes
through
and
both
it
is
gone.
B
You
can,
for
example,
change
a
label,
and
you
say
you
don't
add
an
item,
but
you
add
new.
What
does
it
say
you
just
scrolled
nope
scroll
back
yeah,
you
add
your
request
and
that
already
you
know
that
little
difference
in
wording
for
end
user.
Like
that's
a
huge
change,
I
feel
like
now
they're
inside
an
app
like
to
them.
It's
abstracted
away
that!
Well,
it's
just
a
list
with
adapter
yeah
like
this
is
an
app.
So
at
the
end
of
the
day,
it's
a
really.
B
A
Now
it's
actually
when
I
think
about
it,
and
then
you
I'm
going
to
stop
this
and
this
good
philosophical
discussion
as
well.
When
I
think
about
it,
it's
not
that
the
end
user
needs
to
understand
that
they're
in
an
app
because
they
don't
they
are
in
microsoft.
365.
if
the
best
apps
and
best
experiences
are
those
which
look
like
and
feel
like
they're
part
of
the
native
experiences
and
they're
almost
seamlessly
adapt
across
the
whole
other
functionalities.
A
B
Well,
I
see
it
a
bit
differently
to
the
point
that
I'm
on
my
phone-
and
I
know
I'm
on
I'm
on
a
phone,
but
I'm
doing
things
in
an
app
and
I
think
that
people
are
familiar
with
the
concept
of
being
in
an
app
like
you
go,
you
open
an
app
to
accomplish
x
and
I
think
it's
the
same
thing
on
internet
like.
I,
don't
genuinely
think
that
anybody
thinks
I
am
on
m365.
B
B
B
Web
app,
you
know
with
real-time
collaborative
features
like
that
is
achieving
the
end,
call
exactly
and
gives
you
the
experience.
That
is
sufficient
for
your
needs
to
accomplish
that
so
also,
in
other
words
like
if
I'm
requesting
a
day
off,
I
don't
need
collaborative
features,
because
I
don't
expect
my
manager
to
approve
it
in
real
time
and
I
will
not
sit
there
and
wait.
Is
it
done
you're,
not
you're,
not
what
I
might
be
missing.
Something.
B
B
Absolutely
absolutely
so,
at
the
end
of
the
day
like
when
you
start
with
what
is
it
that
I'm
trying
to
accomplish?
What
is
the
best
way
to
facilitate
that?
Is
it
an
online
app?
Is
it
maybe
in
person
meeting
assuming
you
can
do
that
right?
So
it's
really
cool
to
at
the
end
of
the
day,
acknowledge
that
we
have
a
spectrum
of
technology
choices
available
to
us,
and
then
we
basically
pick
and
choose
like
what
is
how
we
can
support
this
thing
that
we're
trying
to
do
in
the
best
way
and
and.
A
As
we're
heading
more
and
more
and
and
seeing
a
lot
of
investments
and
abstraction
abstraction
getting
lower
higher
anyway,
I
can't
abstraction
getting
higher.
So
what
I
mean
at
that
one
is
that
the
end
users
can
actually
create
more
powerful
experiences
without
the
need
of
actually
writing
real
code.
So
that's
the
low
code,
no
code
movement,
which
is
all
about
empowering
end
users
and
and
you
can
click
a
button.
A
B
In
office,
so
yes,
I
mean
like
it's
just
more
tooling
like
like
we
get
more
because
the
cool
thing
is.
If
you
look
for
example,
at
things
like
flow,
it
allows
me
to
automate
without
my
computer
having
to
be
on.
I
don't
need
to
turn
it
on
now.
I
can
run
something
you
know
like.
Let's
say
I
start
my
day
at
8
am,
and
I
want
to
have
aggregate
of
relevant.
I
don't
know
news.
B
B
Right
because
there
was,
there
was
an
interesting
thing
right.
There
was
the
other
day.
There
was
a
interview
with
your
your
her
manager,
ed
on
the
m365
developer,
podcast,
where
he
said
that
at
microsoft
we
offer
choices
for
different
things
and
the
trick,
or
the
thing
to
realize
is
that
at
times
they
overlap
yep,
and
that
is.
That
is
what
makes
it
hard,
because
it's
at
times
it's
hard
to
say
for
this.
B
You
should
do
x
well,
because
kind
of
the
x
and
and
the
why
fit
it
a
little
and
then
you
really
need
to
understand,
and
maybe
you
need
to
go
about
it-
two
ways
like
one:
it's
given
by
your
experience.
Do
you
have
more
skills
in
this
space
or
in
that
space?
And
then
you
can
choose
two
like
that
or
you
will
say
like
well,
they
might
be
more
fitting
but
or
they
might
fit
both.
B
But
I
know
that
down
the
road.
I
will
not
be
able
to
do
x,
and
that
is
also
part
of
the
plan
not
now,
but
maybe
for
some
time
and
being
aware
of
that,
that
isn't
always
obvious.
There
might
be
also
the
the
other
way
you
go
about
it
and
trying
to
choose
whatever
makes
sense
technology
to
to
build
your
solution.
A
Exactly
it's
always
in
what
context
from
which
perspective
and
how
do
you?
What
are
you?
How
do
you
define
a
best
practice,
but
that
comes
with
a
experience
as
well.
So
you
understand
that
it's
not
about
the
best
thing,
the
skills,
what
you
have
it
doesn't
necessarily
define
that.
That
is
the
best
thing
for
everybody
else.
So
yeah,
it's
the
classic
nail,
if
you,
if
you're,
if
you're,
holding
a
hammer,
everything
looks
like
a
nail
so
but
that's
not
necessarily
how
it
works.
No,
it
doesn't.
B
B
So
this
is
a
really
cool
thing,
because
you
will,
you
will
learn
something
practical,
something
that
you
can
use
in
your
workplace
directly
and
like
at
some
point.
We
will
also
share
the
code,
so
it
will
be
a
really
cool
way
for
you
to
see
how
we
think
about
it,
how
we
think
about
building
apps
and
also
bringing
these
apps
to
where
users
are
to
their
fingertips
as
opposed
to
them
having
to
go
somewhere,
especially
when
they
are
on
the
go.
B
So
if
you're
interested
in
that
join
us
on
the
call,
I
guess
so
that
is
one
two.
It's
just
you
know
the
rhythm
of
work,
we're
proceeding
with
cli
from
iso
365,
building
new
features,
releasing
new
versions,
accepting
pr's
and
now
that
there's
more
of
us.
Well,
hopefully,
we
can,
let's
see
even
more
stuff
exactly
because
it
wasn't
enough
already
right,
so
we're
doing
that
other
than
that
other
than
that
other
than
that.
No,
no,
really,
not
the
top
of
my
head.
What
about
you.
A
Good
question
still
trying
to
catch
myself
around
this
week.
Community
calls
community
calls
coordination.
I
guess
spfx
1.15
new
new
preview
version
is
coming
out
again,
so
adjustments
and
updates
so
we're
getting
closer
to
ga.
This
might
be
actually
already
released
candidate,
but
we'll
see
are
pretty
close.
Actually
so
now
we're
trying
to
focus
on
the
list
customizer
component,
nothing
else
on
this
release
so
well,
of
course,
there's
going
to
be
a
lot
of
other
stuff
as
well,
but
still
so,
and
I'm
watching
my
calendar
trying
to
scan
anything.
A
That's
super
traumatic,
which
I
need
to
jump
into.
Luckily,
nuts,
I
can
just
means
that
I
can
probably
catch
up
on
things.
There's
a
lot
of
one
thing
which
is
actually
taking
a
lot
of
time,
which
we
can't
yet
talk
about
too
much,
but
we're
looking
into
deprecating
some
of
the
older
pieces
within
the
within
the
sharepoint
site
and
those
things
are
always
really
really
really
really
really
painful,
because
you
need
to
which.
B
Like
as
tough
as
it
is
for
you
and
everybody
on
the
team,
the
way
I
say
it's
good
to
hear
is
that
you,
you
acknowledge
importance
of.
You
know
the
right
calms,
the
fact
that
it's
being
used
and
it's
being
used
a
lot,
and
you
cannot
just
you
know
like
pull
the
rug
from
underneath
folks,
but
because
things
will
break
and
that's
not
the
way.
A
To
absolutely
that's
not
how
you
do
that
exactly
we
don't
we
can't
say
what
it
is
right
now,
but
there's
actually
a
few
things
and
all
the
things
which
are
looking
into
shutting
down
and
and
one
of
these
things
one
of
the
big
challenges
of
shutting
down.
Something
is
that,
first
of
all,
you
need
to
understand
what
is
the
usage
and
is
to
use
it.
It's
not
just
the
absolute
number
on
the
moment
of
a
time.
It's
the
is
to
use
it's
growing.
A
Is
it
going
down,
and
is
it
only
a
subset
of
tenants
or
is
it
a
large
set
of
tenants,
because
all
of
that
is
then
impacting
the
strategic
decisions
on?
How
do
we
shut
this
feature
down,
and
then
you
need
to
have
the
data
you
need
to
have
the
directions,
and
then
you
need
to
start
planning
communication
because
you're
not
going
to
shut
certain
centralized
features
down
in
without
giving
12
months
so
24
months,
heads
up
for
the
people,
yeah.
A
It's
surprisingly
interesting,
and
one
of
the
challenges
in
all
of
this
is-
is
that,
of
course,
even
the
the
society
always
focused
on
new
shiny
things,
society
and
the
companies.
Don't
quite
often,
let's
say,
focus
on
hey.
You
did
a
good
job
of
cleaning
this
stuff,
it's
like
yeah,
but
this
is
the
shiny
thing,
shiny
thing,
anything
it's
it's
the
human
mindset
it's
more
on.
Let's
build
something
cool!
No!
No.
We
need
to
do
this.
No,
let's
build
something
cool.
So
it's
an
interesting
dilemma
to
to
balance
so.
B
It
is
it
is,
it
is
it's.
It
is
hard
right
that,
as
you
say,
we
focus
more
and
more
and
more
on
the
you
know
the
new
things
and
you
get
more
more
upgrades
for
that.
But,
on
the
other
hand
like
keeping
the
lights
on
is
important
too,
because
we
have
a
lot
of
customers
who
work
with
us
every
single
day
and
absolutely
their
business
depends
on
us
and
that
needs
to
work
and
a
part
of
that
is
well.
B
A
It
is
especially
in
cloud
as
well:
it's
it's
not
just
the
new
stuff,
it's
also
the
yeah
focusing
on
the
sustainability
and
not
the
new
shiny
things,
but
anyway
I
guess
that's
it
for
now.
Thank
you,
pierce
one
more
time,
really
good
discussion
and
good
to
catch
up
and
thank
you,
wildeck
and
we'll
be
back
with
the
new
bmp
weekly
within
a
week.