>> Hey friends and young people,
have you ever wondered what it's like to be
an intern at Microsoft?
Well, interns here contribute to production software
and they inspire new ideas.
We're going to meet three interns who are
working on the Azure Container Registry and
contributing to ACR Build and Task capabilities
to the VS Code Docker extension, today on Azure Friday.
[MUSIC]
>> Hey friends, I'm Scott Hanselman,
and it's another episode of Azure Friday.
I'm here with Jackson, and Rutu, and Esteban.
How's it going, interns?
>> It's going really well. How are you?
>> Really well, fantastic.
>> I'm feeling it. You're here on Azure Friday.
This is the most people I've ever had
on one episode of Azure Friday.
So, I'm not quite sure how it's going to work,
but it's pretty fantastic.
So, you are coming out of the end of
what, a 12-week internship, Esteban?
>> Yes, we've got two and a half weeks left,
started June 16th, I think. We end September 7th.
>> Okay. Are you expected to
accomplish something in those 12 weeks
and actually ship something, Rutu?
Are you supposed to hand them code at the end of,
goodbye, and here's the code?
>> Yeah. So, basically, we're part of the Explore program,
which was four weeks program management
and then eight weeks of development.
So, in the first four weeks, we were just tasked to make
a whole spec and just figure out the technology.
Then, the last eight weeks, we do have a project,
which we'll get into little bit later
and we will be delivering code.
In fact, since it's open source,
we've already pushed some of it out.
>> All right, rock on.
>> Yeah.
>> Jackson, what grade are you all in?
So, are you sophomore, juniors in college,
and where did you go to school?
>> Yeah. So, the program that we're actually working in is
primarily geared toward rising juniors and sophomores.
So, I'm a rising sophomore,
they're a little bit older as rising juniors.
>> Okay. Do you all go the same school and how did you get picked?
>> I go to the University of Washington.
>> I go to California Polytechnic State University
in San Luis Obispo.
>> Well, that's like a long name.
>> Yes.
>> I go to Stanford.
>> Did you apply and did you beat out thousands of other people,
or how did becoming an intern happen?
>> Well, that's a great question.
I don't know how many people we beat,
if we beat any. We did do some application.
At least me, personally, at first had a face-to-face interview.
Then, we were flown out to do
a actual technical interview, and then,
from there on, we were actually told whether we got in or not.
>> So, what kind of a process?
It was multiple steps to make this happen?
>> Yes.
>> My process was just a little
bit different because I'm returning intern,
so I just had one interview [inaudible].
>> I see, because you were cleared from the previous time.
>> Yeah.
>> Okay. Did you know each other before
or were you forced into a group?
>> Yeah, we didn't know each other before.
I'm really glad I got to know them though.
>> Yeah.
>> I think we definitely got along really well
and definitely stay friends after this internship.
>> Yeah. A big part of software that people don't really realize,
I think, when they get started is,
it's as much getting along with people
and communicating effectively with people
as opposed to trying to show up
and be the smartest person in the room.
>> Yeah, that's one of the cool things about
the actual teamwork aspect at the Explore program,
is because we're in a pod,
there's a lot of a accountability that we have for each other,
but also support, which is awesome as young interns.
>> That's cool. Did you have any negative experiences,
or did you find that most people were pretty cool?
>> It was pretty nice. In terms of negative experiences,
we brought some gummies in and [inaudible] bought five pounds.
>> So, other than Jackson eating all the candy.
>> Yeah, [inaudible].
>> Yeah. In terms of interacting with people outside
our pod and our team,
I would say the experience has been great.
I'm really grateful that we were able to
contact anyone in the company and
they came for one-on-one lunch with us.
>> Seriously?
>> That's something I didn't expect coming
into such a big company, but I got to meet
with so many people one-on-one. Yeah, it was great.
>> Yeah. We've heard a bit about the intern card
that you can pull and it's actually incredible how much we
can pull it and how much it works because people are just.
>> Okay. What is the intern card,
and can I pull that? Or is it too late?
>> No. Might be a little bit late,
but it's just everybody's just trying to help you.
When you say you're an intern, they're like,
can I connect you to someone,
can I give you new resources,
which is something that nobody has to do,
but it seems like everybody goes
above and beyond to help us, which is awesome.
>> That's cool.
>> Yeah. We can actually schedule the weekly meetings
to actually meet with other employees.
There's also weekly meetings with some of the VPs and stuff.
>> Yeah. There's a program called Lunch and Learn,
and we got to sit down
with a couple executives and people like that.
>> What does that feel like when you are
in your early 20s and you're meeting someone
that has a Wikipedia page or is a VP?
Are you initially thinking,
this is like a big deal, and then, you're like,
oh, well, this is just another human?
>> Yeah. You come in thinking,
wow, and then, you leave like, well, but this guy's cool.
>> Yeah. It's definitely intimidating at first,
but once you go in the room, they're like, hey, what's up?
It's just really casual.
I think this definitely made me
more willing to talk to whoever I want to.
>> Yeah.
>> I would say that one thing that definitely shows
is the humanity of the company,
it definitely keeps things casual.
>> Yeah.
>> Yeah, and that definitely makes it better when
you're talking to people who are higher up.
>> That's cool. So, let's see what you all built.
You brought a demo for me here?
>> Oh, yes. So, we're working
on a VS Code extension called Docker extension.
>> Okay. You look there and I'll look at the TV over there.
>> Perfect. So, the Docker extension that we're working on is
open source extension that Microsoft has been working on just
to facilitate the use of Docker and other technologies.
We've implemented stuff to
improve communication with the Azure Container Registry,
which we usually now do through the Azure CLI.
So, we've added a lot of management features and other such things.
>> Okay.
>> Yeah. So, ACR or Azure Container Registry is just
basically Azure's way of managing and hosting Docker images.
So, like Esteban mentioned,
we made a lot of management tools so that users find
it easier and have a one-stop shop for everything,
right here in the extension.
So, as you can see,
I'm already logged into Azure here.
So, that's why this Azure node is popping up under "Registries",
and if I right-click it,
I can create a new registry.
I'll choose a subscription,
and you can either create
a new resource group or select an existing
one and have a new registry name.
So, demoChannel9yay, and then,
choose a service provider,
a location, and with that,
we've now successfully made a registry.
Once it refreshes, it'll pop up right here.
>> So, in that case, you're doing the stuff that I
would do ordinarily from the command line,
except I didn't have to remember anything complicated.
>> Exactly.
>> What language is this written in?
>> TypeScript.
>> Okay, cool. So, TypeScript.
Were you JavaScript people before?
>> No. So, that's actually one of
the learning curves that at least I faced.
>> Okay.
>> Because especially because I'm younger,
I was unfamiliar with a lot of the both processes,
languages, everything that we're doing here.
But again we were allowed ramp up
which definitely helped to make us
confident with the tools we're using.
>> I understand that the CLI is written in Python,
but you didn't really do much in Python. Is that true?
>> We haven't actually touched Python.
We've had to read a lot Python
to pre-implement some of the features from here,
but we haven't actually written any Python during this internship.
>> Were you familiar with Visual Studio code
before you started this process or we're using different editors?
>> I used VS code just in my last quarter school.
But I wasn't aware of all
like debugging features and does a lot of
little things which I found here and I'm
definitely going to tell everyone in my class to use it now.
>> You're might be young enough
that you don't necessarily remember like
old Microsoft and how we were like so totally evil,
and you're like hated everyone we've
killed, small animals and stuff.
But is there any sense of like new Microsoft,
old Microsoft, Cloud Microsoft and these kind of things?
Or do you all think about big companies in that way
like Google and Facebook and Microsoft and Apple et cetera?
>> So, at least in me in my personal experience,
I was always kind of a Microsoft fan boy
mostly because I was an apple not lover.
But I have seen a huge change.
So, at least in terms of open source,
I mean I'd never expected we'd actually
be working on an open source project.
>> That's a good point. Was this committed into GitHub?
>> Oh yeah. Currently, some of this stuff is in there,
pull request and such stuff.
We're getting a little bit implemented,
but some of our code's already published
and the extension has 4.4 million users at the moment.
>> There's extension that you're working on has 4.4 million users?
>> Yes.
>> So, you're improving an existing extension and adding
even new more functionality and that's
living in a pull request right now and soon to be live?
>> Yes.
>> So, you didn't do anything with any secret APIs
or check into internal repositories?
It was all open-source and type script from the very beginning.
>> Yes.
>> Yeah, that is a different Microsoft, isn't it?
>> Yeah. It's cool and we do hear a lot
about like the new direction that things are being taken
and that was kind of the one of the things explained when they
explained our project is that like if you were here earlier,
basically open sources are thing that's more novel to Microsoft,
but they're really buying and well.
>> Yeah.
>> In a new direction, yeah.
>> I think in the old days, we would call it
closed by default and now it's opened by default.
So, it makes total sense
for interns to be contributing to code and then you're
going to go back to school in a couple of weeks and be able to
say that your code is running on at least 4.4 million machines.
It's pretty amazing. Do you think
you'll spend more time in VS Code and Docker and containers,
if you decided that containers are the future?
>> Oh yes. Containers are actually pretty great.
We hadn't actually heard from it before.
>> Really? They don't teach containers in your university?
>> No.
>> A [inaudible] hopefully back and talked
about Azure and containers and VS Code?
>> Yeah. Well, I mean, once we definitely
gotten involved in the space for learning
a ton more about where they're actually used.
Like even if you visit the Docker website right now,
they advertise a lot of
like buzzwords like AI and stuff like that.
>> Very cool. Where can people
find the code and look at the stuff that you
all did and experiment because I know you
have a lot more functionality that you had.
>> Oh yes. So, a lot of the code we have is already public.
You can already see it by going to
the GitHub repository for the VS Code Docker extension.
Some of it is already in
the actual code base and you can just 4K and download
>> All right.
>> It was a little renaming issue which I think
you actually told us about.
>> That's all good, so much forgotten.
So, your right-clicked on a Docker file right there.
>> Yes, and then it would just select it, just the subscription.
>> I can see down there in the output where it's
going off and trying to get that subscription.
>> Yes after that, we'll just go for the registry.
We actually have when we use a lot.
That's some good naming conventions, Channel Nine.
Let's just test, and so,
this will start a build in the in the Cloud.
>> Okay.
>> Right? Then we'd actually be able to see the build.
This is also something we've been working
on that had some good accessibility features.
We can see the logs for the builds.
So, we can go here and we can see-.
>> It also brings up some interesting testability features
as I'm noticing you scroll around a lot,
and makes me wonder when someone has that many registries.
If you can collapse it or filter it,.
>> Yes. That is something we have to work on,
but it's not a very common use case as of right now.
>> Yeah, not yet.
>> We're not currently focusing too much on it.
>> Was that one that you just started right there at the top?
>> Yes. That's the one he's running right now.
>> Okay. So, we can actually see
all the builds that have already work.
This is something we had to do.
It has a lot of accessibility things that we had to think about.
For example, all the colors have to pass
a certain threshold of contrast.
If things have to be very intuitive,
apparently this little triangle isn't that intuitive yet.
But we're working on it,
and you can actually see logs of something that it succeeded.
>> You can get color highlighting in the logs as well.
>> Yes. So, that will also facilitate some of the things.
If they actually failed,
there's also some color highlighting for that.
>> Cool.
>> Yeah. So now, you can actually see whether
builds are working succeeding,
what happened all within VS code.
>> So this is a private build but we can go and look at
the code and it'll be probably by the time we published this,
it'll be merged into the ultimate product, right?
>> Yes, it's cool.
>> Very cool, you mention anything else?
>> I mean, there's other management features.
>> I would just say to wrap up our experience in the internship.
For people looking into Microsoft,
I just want to say it's one of
the best intern programs I've experienced so far.
Every week there's something new to do.
We've been to the museum at pop.
We had a whole all hands with their entire organization,
went to the zoo, and this countless activities.
Apart from all the great technology and teaching,
it's just a lot fun.
>> Very Cool. Well, thanks so much for Hanging out with me today.
>> Yeah.
>> Thank you.
>> Thank you very much.
>> I'm here on Azure Friday wishing
that I was an intern at Microsoft.
But I hope you keep watching and I hope you follow
these folks online and in their Git commits,
we'll see you again next week.
[MUSIC]