TRANSKRYPCJA 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 06/19/2026 14:50:00
Duration: 2228.036
Channels: 1
1
00:00:06.960 --> 00:00:09.599
So, again, it's it's great to meet you
2
00:00:10.480 --> 00:00:16.445
for the first time. Thank you very much for doing this. Yeah. I'm I'm happy to be here. Nice to meet you as well.
3
00:00:17.324 --> 00:00:17.884
So
4
00:00:18.445 --> 00:00:20.204
I looked you up, of course,
5
00:00:21.085 --> 00:00:23.965
and I see that your title is principal
6
00:00:24.044 --> 00:00:25.324
product manager.
7
00:00:26.445 --> 00:00:29.789
What what is that? Can you explain what that is? I have no idea.
8
00:00:31.710 --> 00:00:45.845
Well, I think that yeah. And I understand why you have no idea because I think it's different for every company. Like, the term product manager means different things to different people. We were used to call be called program managers, but the industry kinda adopted product manager.
9
00:00:46.405 --> 00:00:48.885
So what it is is, like, it's a technical role
10
00:00:49.605 --> 00:00:56.085
in the engineering org. So whether it's, you know, as you work on the Windows team or Office or as I do on the Visual Studio team,
11
00:00:56.965 --> 00:01:02.460
you work with the engineers, but you're the PM. And so the responsibility of the PM,
12
00:01:02.780 --> 00:01:05.420
again, it varies from team to team and and
13
00:01:05.900 --> 00:01:09.740
Yeah. All even from PM to PM. But it's basically the person that, you know,
14
00:01:10.380 --> 00:01:11.900
understand the users,
15
00:01:12.300 --> 00:01:18.215
sets the road map, works with the engineering to build the features that they want, the help they design the features
16
00:01:19.174 --> 00:01:20.935
often with the users.
17
00:01:21.735 --> 00:01:24.935
And so it's a it's a very kinda user focused role,
18
00:01:26.420 --> 00:01:26.979
and
19
00:01:27.460 --> 00:01:31.140
it's also some there's some project management in it as well.
20
00:01:31.540 --> 00:01:40.580
Right? Because you wanna make sure you have the release notes that go out at the right time when you when you release the features that you've helped build them. And all that stuff, the go to market stuff.
21
00:01:41.935 --> 00:01:46.335
So there's a bunch of of project management. But as a PM, you can kind of
22
00:01:46.815 --> 00:01:59.240
you know, as you find out where your passions lie and where your interests are over time, you can you can put yourself on the spectrum where you might have project management on one end of the spectrum and, like, highly technical
23
00:01:59.720 --> 00:02:01.400
stuff on the other side,
24
00:02:01.640 --> 00:02:04.760
like, built maybe, like, to the point where you built the features yourself
25
00:02:04.920 --> 00:02:06.440
to an extent. Yeah.
26
00:02:06.760 --> 00:02:11.160
And you find yourself where where are you the most happy and most effective on that spectrum?
27
00:02:12.025 --> 00:02:22.825
And so I think that's why the when
Load full transcript
you ask that question, and I say, oh, well, it depends. I think it depends on where you are. And there might be other pivots as well. It might not be just the project management versus technical.
28
00:02:22.985 --> 00:02:30.080
There might be others, you know, things as well you can you can put yourself on. So I I I'd look at myself as somewhat
29
00:02:30.400 --> 00:02:32.080
closer to the technical
30
00:02:32.640 --> 00:02:34.560
and less on the project management.
31
00:02:34.720 --> 00:02:38.480
So I'm very involved with the users, very much out there, conferences
32
00:02:38.480 --> 00:02:42.335
and social media and stuff, and listening and understanding and
33
00:02:43.455 --> 00:02:50.335
being the internal advocate of the users. So I take all that feedback into the teams and help build Visual Studio
34
00:02:50.735 --> 00:02:52.895
in accordance to what the users need,
35
00:02:53.520 --> 00:02:59.040
both what they tell me they need today, but what I can understand they probably will need in the future as well, which is
36
00:02:59.760 --> 00:03:01.840
it it becomes an art form at that point.
37
00:03:02.720 --> 00:03:06.080
Yeah. And and how long have you been doing that for Visual Studio?
38
00:03:07.120 --> 00:03:08.160
For
39
00:03:07.985 --> 00:03:10.705
fifth over fifteen years now. Wow.
40
00:03:10.865 --> 00:03:19.025
Yeah. That's very cool. And I was an engineer before, so I came from the world of like, I was a Visual Studio user for ten years before I joined Microsoft,
41
00:03:19.185 --> 00:03:21.905
you know, in startup companies and all that. So I I used to be
42
00:03:22.850 --> 00:03:24.210
the people I'm
43
00:03:25.170 --> 00:03:28.210
building, which would for today. Right? Yeah.
44
00:03:28.290 --> 00:03:34.450
That's very cool. And I noticed that you build still a lot because when I look for an extension,
45
00:03:34.690 --> 00:03:36.210
your name shows up a lot
46
00:03:36.610 --> 00:03:37.970
with all sorts of extensions.
47
00:03:38.845 --> 00:03:41.085
Yeah. I cannot because it's,
48
00:03:41.645 --> 00:03:48.045
you know, this it's the shortest if I have an idea and I don't know if it's a good idea or not or I don't know if my
49
00:03:48.525 --> 00:03:52.125
vision of how it should work or be implemented
50
00:03:53.165 --> 00:03:56.680
is right or wrong, then the fastest way is to, like,
51
00:03:57.080 --> 00:04:08.200
create it and then give it to the user and say, hey. What do you think? Mhmm. Yep. Then figure out how do they use it, what are the patterns, what don't they like, and then accept pull requests and comments and,
52
00:04:08.520 --> 00:04:18.355
you know, issues on GitHub so that it becomes like a fast feedback loop. And then very quickly, I can go back to the team and say, hey. Look. I made an experiment.
53
00:04:19.235 --> 00:04:22.675
We iterated on it. These were the issues. Here were the fixes.
54
00:04:22.755 --> 00:04:28.700
Here's where we still have some opportunity for improvement, blah blah blah. And so that kind of replaces a spec.
55
00:04:29.420 --> 00:04:34.220
Yeah. Or it or it helps the spec because it's like it literally shows the screens,
56
00:04:34.460 --> 00:04:41.775
the the click stops, everything like that. Right? It's like a highly advanced mock up that you would normally maybe give to an engineering team.
57
00:04:42.255 --> 00:04:53.455
Oh, I never thought of it that way, but that that makes so much sense. It's like a proof of concept of something that you think people want, and then you actually make it and people can directly use it without actually baking it into the product.
58
00:04:54.319 --> 00:05:01.600
Yeah. And sometimes we do bake it into the product. It starts its life like that. It might have been something that's been on a feature request for a long time,
59
00:05:02.720 --> 00:05:27.000
and then I'm like, okay. I now I have a need for it or I have a vision for how we can do it the right way, and so I go ahead and build it. And that can be the beginning of a way to build something in, or it can just be a way to say, hey. There's a bunch of people that want it. Let me just provide them that right now. And it could be years down the line before it reaches a per a priority level that we wanna build it in. Yeah. Because of other reasons.
60
00:05:27.720 --> 00:05:32.280
So it's there's not always a one to one, like, in the here and now. Sometimes it takes years
61
00:05:32.520 --> 00:05:40.600
for it to be relevant to the team to bring in, but then we already have years of, like, refinement and iteration that makes it super high quality.
62
00:05:41.695 --> 00:05:46.735
Yeah. And people actually using it. That that's perfect. Yeah. Yeah. Oh, that is so cool.
63
00:05:47.055 --> 00:05:50.015
And then so you come up with everything,
64
00:05:50.495 --> 00:05:52.655
maybe with colleagues as well, colleague
65
00:05:52.895 --> 00:05:57.020
product managers? Are you the only one? Yeah. No. Of Visual Studio?
66
00:05:57.580 --> 00:05:59.100
No. No. No. There's a bunch.
67
00:05:59.420 --> 00:06:00.060
Mhmm.
68
00:06:01.020 --> 00:06:05.420
We have a lot more engineers than we have PMs for you know? And that's a good thing.
69
00:06:06.380 --> 00:06:09.660
Yeah. You there's definitely a thing is too many PMs. So
70
00:06:10.095 --> 00:06:13.935
I think we've already have a had a a kind of a lean
71
00:06:14.015 --> 00:06:16.815
PM team, but it's I think it's leaner now,
72
00:06:17.295 --> 00:06:17.775
which
73
00:06:18.815 --> 00:06:19.615
is kinda
74
00:06:19.935 --> 00:06:21.615
it works out pretty well. So,
75
00:06:22.415 --> 00:06:23.455
yeah, we're we're, like,
76
00:06:25.380 --> 00:06:28.660
on the PM side, on the core Visual Studio team.
77
00:06:29.300 --> 00:06:34.580
I think we're about I don't even know. I'm just get I'm just gonna give you a number. 12 PMs.
78
00:06:34.980 --> 00:06:53.190
Wow. But that includes, like, PM managers as well. Yeah. Okay. Of which we don't have that many,
like, two or something, two or three. But then you have all the other other team that also contribute into Visual Studio that are not part of the core team. So for instance, the dot net team and the c plus plus team. Okay. Now they build the runtimes. Right? And they build all the
79
00:06:53.590 --> 00:06:58.550
CLI stuff, and they build Versus Codex, and and they do all sorts of other things, but they have dedicated
80
00:06:59.270 --> 00:07:05.695
engineers and PMs that work on Visual Studio tooling for dot net and for c plus plus and so on. Okay.
81
00:07:05.695 --> 00:07:13.375
Yeah. So they're they're PM for Visual Studio as well. They're just not part of the core team. So if you if you, like, kind of combine it all, I'm I'm sure we're about, like,
82
00:07:14.655 --> 00:07:16.495
I don't know, 25
83
00:07:17.135 --> 00:07:17.775
PMs.
84
00:07:18.439 --> 00:07:25.400
And and that goes up and down depending on where people are needed in the moment. Sometimes you move and do something else. You come back and do other
85
00:07:25.800 --> 00:07:31.560
features and so on. Or you have teams that come in and say, hey. I'm gonna we're gonna build an Azure feature into Visual Studio.
86
00:07:32.025 --> 00:07:48.740
But then when we're done, we're not we're gonna move on and do something else. Yeah. Right. Yeah. So they're only part of the team for, like, let's say, two months, and then they're elsewhere. Okay. So it's a it's a huge organization just for Visual Studio alone. I didn't realize that. No. It's not well,
87
00:07:48.820 --> 00:07:50.740
depends on what you Sounds good. Yeah.
88
00:07:51.700 --> 00:07:54.660
Yeah. But it depends what you mean by huge. I don't see it as such. You
89
00:07:56.980 --> 00:07:59.460
know, I we used to say we're over 250
90
00:07:59.460 --> 00:08:04.935
people, but it, you know, but it comes in waves because, you know, as I wasn't what I what I was just mentioning.
91
00:08:05.415 --> 00:08:08.215
But I don't know if we're more than a 150
92
00:08:08.295 --> 00:08:09.095
today,
93
00:08:09.975 --> 00:08:12.055
which is big for one product.
94
00:08:12.295 --> 00:08:17.320
But when you consider that Visual Studio is one of the largest software products in the world
95
00:08:17.800 --> 00:08:21.080
Yeah. By far the biggest WPF app, right,
96
00:08:21.240 --> 00:08:28.840
and maybe dot net app as well. Yeah. But just in in general, like, we don't we don't even know how many lines of code we got, but it's it's
97
00:08:30.014 --> 00:08:33.695
in the millions and millions and millions. So Yeah.
98
00:08:34.654 --> 00:08:39.615
Okay. So very important. And and and, I guess, a huge install base.
99
00:08:40.015 --> 00:08:43.775
Like, do you have kind of a a guesstimate of how many people use this?
100
00:08:45.350 --> 00:08:47.590
Oh, yeah. We're in the double digit millions.
101
00:08:47.910 --> 00:08:49.510
Really? Wow. Amazing.
102
00:08:50.950 --> 00:08:55.990
And and the number is not you know, you would think maybe that, oh, nowadays, everyone is just using,
103
00:08:56.550 --> 00:08:59.350
you know, Claude code or, you know, CLI
104
00:08:59.205 --> 00:09:04.565
or Copilot CLI or Versus Code or, you know, Cursor or because those
105
00:09:04.885 --> 00:09:09.445
products and the users of them are very loud and dominant on social media,
106
00:09:10.405 --> 00:09:14.085
you would think that Visual Studio numbers are going down, but they're not. They're they're going up.
107
00:09:14.760 --> 00:09:19.720
They're going up. Oh, that's good. Yep. Visual Studio is actually very, very healthy
108
00:09:21.160 --> 00:09:27.640
even though you don't hear as much about it. It's not as visible maybe as it used to be because it drowns out a little bit in all this
109
00:09:29.045 --> 00:09:33.125
especially nowadays with all the AI, like, in all the hysteria of of that.
110
00:09:33.605 --> 00:09:34.405
And so
111
00:09:35.125 --> 00:09:41.525
but but, no, Visual Studio is is doing quite phenomenally, and I think has found a really sweet spot in
112
00:09:42.450 --> 00:09:49.090
the world of, you know, AI versus, like, people who either don't want to use it or just use it occasionally
113
00:09:49.090 --> 00:09:55.170
or who are not allowed to use it because of, you know, security or whatever concerns their organization might have. Right?
114
00:09:56.155 --> 00:10:01.275
Yeah. So so Visual Studio is somewhere in between where, like, it it's getting really good at AI.
115
00:10:02.075 --> 00:10:07.275
The way Visual Studio does it is a little bit different than the others, and that's on purpose because we we have a different
116
00:10:07.950 --> 00:10:15.310
cohort of users than others. Like, Versus Code, for instance, has to be pretty broad. Like, they you know, whether you're a student or
117
00:10:15.550 --> 00:10:16.830
data scientist,
118
00:10:16.830 --> 00:10:23.550
beginner, advanced, web developer, back end developer, game developer, like, they they target pretty much everybody very generally.
119
00:10:24.565 --> 00:10:26.485
Visual Studio is very
120
00:10:27.045 --> 00:10:38.885
narrow. It's like professional developers, c sharp and c plus plus. That's what we go for. Enterprise often because it's the pro developer segment. And so the concerns and the the habits and the
121
00:10:40.150 --> 00:10:41.190
priorities
122
00:10:41.350 --> 00:10:44.150
of that cohort is just different. And so
123
00:10:44.710 --> 00:10:48.870
the way we lean into that has been kind of unique, I think, in the industry and and
124
00:10:49.350 --> 00:11:01.625
it being pretty successful because we're really good at both doing the AI stuff, and we have to be loud about that. And so some people are like, oh, it's every everything is about AI in Visual Studio. It's like, no. It's not. We're actually really good at
125
00:11:02.265 --> 00:11:05.545
doing a bunch of features that has nothing to do with AI.
126
00:11:05.945 --> 00:11:06.985
And so we do both,
127
00:11:08.130
--> 00:11:11.250
and and we do that with with quite the success. So
128
00:11:12.050 --> 00:11:18.930
it's not doesn't mean that we're perfect or that we don't have any room to improve, of course, but it means that we I think we found finally a sweet spot
129
00:11:19.170 --> 00:11:23.170
where we can cater to both the people who use AI
130
00:11:23.425 --> 00:11:30.705
every day, all day long, and the people who don't use it at all and anywhere in between as long as they're Pro, C Sharp, and C plus plus Yeah.
131
00:11:31.665 --> 00:11:47.790
That that makes me very happy to hear that it is still going strong and even going up because I am a Visual Studio user from back in the day. You know, always did Visual Studio and then Versus Code came out and I was like, I need to do so much myself. Extensions,
132
00:11:48.190 --> 00:11:49.950
CLI stuff, terminal.
133
00:11:50.110 --> 00:11:50.430
Okay.
134
00:11:51.095 --> 00:12:18.770
It's not not my thing. I like visual visual studio, so I like to see things and click on it and do things in a simple way. Debugging is a very strong thing for instance in Visual Studio. It's easy to make things run. You just click the button and it starts to run. That's what I like. I I liked it a lot. And like you said, AI, I use that a lot as well. I get the Copilot for instance. But it's also right in there, so you can just use that.
135
00:12:19.490 --> 00:12:25.214
It's slightly different from Visual Studio CodePilot and Versus Code, but not that much, I think.
136
00:12:25.774 --> 00:12:31.214
No. And and it's the gap is also closing. I think the if you're on the insiders
137
00:12:32.014 --> 00:12:34.815
Yeah. Which is our kind of our preview release
138
00:12:35.855 --> 00:12:40.230
for you to get early access to the bits Visual Studio, you'll see that it's
139
00:12:40.230 --> 00:12:43.030
it's getting better so much faster now.
140
00:12:43.350 --> 00:12:47.590
And so I'm on internal builds, and I'm having an absolute fantastic time.
141
00:12:49.905 --> 00:13:05.185
I I just think that the quality has gone up so much and the speed and the execution. Everything is just better. So I'm very, very happy about that. And so you're gonna see that gap closing, but it's not gonna close completely. It never will because we are targeting other things. So you were mentioning the debugger.
142
00:13:05.750 --> 00:13:07.670
We have probably arguably
143
00:13:07.750 --> 00:13:10.630
the best debugger in the industry, and there
144
00:13:11.190 --> 00:13:13.990
are things we can do that no one else can do
145
00:13:14.390 --> 00:13:17.990
because we have that debugger. And and if we we there are ways we can tie
146
00:13:19.045 --> 00:13:22.964
AI into the debugger that makes you even better at debugging.
147
00:13:23.125 --> 00:13:25.685
Yeah. It's about returning power to you
148
00:13:26.884 --> 00:13:30.964
because how do you how do you make sense of, like, some issue you're having
149
00:13:32.230 --> 00:13:47.510
in some sort of async call where you don't know exactly what the issue is? You maybe you run stuff in parallel on background threads, and it can be really hard sometimes to debug really complicated things. So how do we use AI to solve that problem? We haven't been able to solve it before.
150
00:13:48.015 --> 00:13:50.175
There are certain problems that you can't
151
00:13:50.655 --> 00:13:52.735
solve in a deterministic way.
152
00:13:53.055 --> 00:13:55.135
Yeah. And everyone's app is different.
153
00:13:55.535 --> 00:13:57.775
So debugger scenario is very
154
00:13:59.215 --> 00:14:04.890
is is an is an obvious thing that we can add special value through AI. Now other
155
00:14:05.050 --> 00:14:06.810
IDs and and and
156
00:14:07.530 --> 00:14:12.090
editors out there cannot do that because they don't have a tight integration to a a really powerful debugger.
157
00:14:12.250 --> 00:14:17.130
So we have an edge there, and we're leaning into that because that actually is something that's a very pro
158
00:14:18.455 --> 00:14:19.335
use case.
159
00:14:19.815 --> 00:14:24.215
There are other things about unit testing, for instance, that that lends itself very well to that.
160
00:14:25.815 --> 00:14:27.975
Creating new projects from scratch,
161
00:14:29.575 --> 00:14:37.660
again, is something that you can't do in a deterministic way. You have to have some sort of AI because everybody's project is different. So there are certain things
162
00:14:38.300 --> 00:14:40.700
that we're looking into. Like, if you wanna create a new
163
00:14:41.500 --> 00:14:42.380
website
164
00:14:42.460 --> 00:14:50.705
I'm just making making this up. Right? Let's say you wanna build a new website. You wanna build one you have a customer that wants a bakery website for their new bakery.
165
00:14:51.345 --> 00:14:54.785
And so you can go in and say, file new project, and you can choose
166
00:14:55.265 --> 00:14:56.945
asp.net web application.
167
00:14:57.825 --> 00:15:05.680
And that gets you kind of to, like, a hello world type of situation, and then you have to do the whole bakery thing. But what happens if you go and say, hey. I want a bakery website.
168
00:15:06.320 --> 00:15:10.959
Right? And and you can then be asked for clarification. Hey. Do you want, you know,
169
00:15:11.600 --> 00:15:19.764
an app to go with that for, like, return customers so there's a loyalty program? Do you want it can start to ask you all those questions. Right? And so your
170
00:15:19.925 --> 00:15:22.245
starting point when you're done scaffolding
171
00:15:22.404 --> 00:15:26.964
and have to go to work is, like, much closer to the end result than it was in the past.
172
00:15:27.524 --> 00:15:29.444
And Visual Studio has this rich templating
173
00:15:30.149 --> 00:15:31.029
mechanism.
174
00:15:31.029 --> 00:15:38.470
Right? We've always had that. Yeah. Text editors don't have that, so they can't lean into it in the same way we can. So it's about leaning into some of those
175
00:15:39.110 --> 00:15:41.990
things that makes Visual Studio Visual Studio.
176
00:15:42.470 --> 00:15:50.875
It's not just about, like, the chat and, you know it's also about that, but it's not only about that. It's also about the special things in Visual Studio.
177
00:15:51.115 --> 00:16:08.760
Yeah. And I like that. That's why I still use Visual Studio and also with AI because there, when I hit an exception and the debugger pops up, then I can click my Copilot thing and I say help me with this exception and then it can actually read the variables and all the things around there and use that as context,
178
00:16:08.920 --> 00:16:16.845
which I cannot do yet maybe in Visas code and I don't know if that will ever happen because there's not a strong link there with with debugger.
179
00:16:17.165 --> 00:16:17.805
Yeah.
180
00:16:18.605 --> 00:16:20.524
It is something we're looking at, but the
181
00:16:21.084 --> 00:16:27.084
but that's exactly right. So I I think Visual Studio is the is the tool and will remain the tool
182
00:16:27.800 --> 00:16:30.600
for developers who really value
183
00:16:30.680 --> 00:16:32.519
code as an asset.
184
00:16:33.399 --> 00:16:38.440
Like, there are there are certain code that is that's not an asset. That's just an artifact.
185
00:16:38.600 --> 00:16:42.155
Yeah. Like, if you write proof of concept prototypes,
186
00:16:42.715 --> 00:16:52.155
it could be side projects, small things, throwaway things, internal tools, or whatever. You don't really care about code. Like, you don't have to maintain the code for years to come
187
00:16:52.649 --> 00:16:54.730
as a team of engineers.
188
00:16:56.329 --> 00:17:04.090
If all your interaction with the code is that it just generates and you just ask the AI to fix it if there's an issue and you don't actually look at the code and you don't really care,
189
00:17:05.275 --> 00:17:12.235
you know, you can use whatever tool you want. You can use Visual Studio. You can also use the CLI. You can you can use whatever, and you're gonna have a great time.
190
00:17:12.635 --> 00:17:22.900
But if code is an asset to you, if it matters how it's formatted, if you're gonna review it, if there's pull request and peer reviews and all those type of things where it really matters
191
00:17:23.060 --> 00:17:27.620
that it's high quality and has a high maintainability score and all that type of stuff,
192
00:17:28.180 --> 00:17:42.235
Visual Studio is for you. Like, that is, like, hands down. That does not change because AI comes into the picture. In fact, we're gonna double down on a bunch of these things so that even if you're using AI, we're gonna make sure that you're gonna have kind of that enterprise grade
193
00:17:42.475 --> 00:17:43.595
code quality
194
00:17:43.755 --> 00:17:50.770
that you had when you wrote everything out by hand. And so you might still write a bunch of stuff by hand, but it it you might also have some things written
195
00:17:50.930 --> 00:17:53.330
by
Copilot, let's say. Right? And so
196
00:17:54.450 --> 00:18:01.615
have all that done in a way that's, like, exactly how you or your team wanted to look and act and all the tough stuff. And so
197
00:18:01.855 --> 00:18:04.095
it's, again, it's about quality. It's about
198
00:18:04.895 --> 00:18:08.655
seeing your code as an asset. That's really what Visual Studio is about.
199
00:18:09.295 --> 00:18:13.455
And and how do you do that yourself? Like, when you write extensions,
200
00:18:13.455 --> 00:18:19.570
for instance, do you still write code by hand, or do you just tell the AI to do it?
201
00:18:20.290 --> 00:18:22.130
I tell the AI to do it mostly.
202
00:18:22.530 --> 00:18:23.490
I have.
203
00:18:24.690 --> 00:18:43.519
You know? But the thing about but that's but hang on. It's because that none of my code goes into Visual Studio. It never did, even when I wrote it by hand. Right? The engineering team, they have their quality gates. They have a bunch of things that they do that I don't have to do when I write an extension. I don't fall under those same quality
204
00:18:44.160 --> 00:18:53.040
concerns or whatever. Right? And I don't have to maintain it over time to the same extent. Like, I don't have to have a whole team to being able to, you know, maintain it for years down the line.
205
00:18:53.955 --> 00:18:54.994
It's just me.
206
00:18:55.475 --> 00:19:02.914
Yeah. Yeah. But yeah. Yeah. Well, I don't care. I don't I I for me for me, some of a bunch of my code is just an artifact.
207
00:19:03.395 --> 00:19:14.179
Yeah. I get that. And and there's no shame in generating codes. That's kinda what the AI does. You know, it's funny because, first of all, I I that's I agree, but I will I will say
208
00:19:14.500 --> 00:19:32.135
I would not the way I do it, the way I code with just the AI, I would not consider an asset. Like, I would not be someone that'd be proud of it or present it to my team and say, hey. Look at can you do a code review here? Like, I was like, no. Don't don't review this code. I know I can go through and be like,
209
00:19:32.695 --> 00:19:33.255
no.
210
00:19:33.575 --> 00:19:48.090
You know? I I don't I don't like it, but I but I don't feel like I need to. So in this case, I don't need to. Yeah. But every project is different. Right? You're everything is different. What I really like about Visual Studio is I stay in there, and when I debug, I have to debug it.
211
00:19:48.730 --> 00:19:49.050
Like,
212
00:19:49.665 --> 00:19:59.265
I'm still the best debugger between me and the AI, hands down. Yeah. No matter who wrote the code, I can debug. And I'm not even a great debug person at all. I'm not very low level,
213
00:20:00.945 --> 00:20:09.649
but I'm still better than the AI. So having it all happen in Visual Studio I'm not using the CLI. I use it sometimes for some other things, but not for writing code.
214
00:20:09.890 --> 00:20:23.695
I use Visual Studio. I wanna see what happens. I want I still wanna understand what's going on because I still need to steer it because I know what some of the caveats are for the in the Visual Studio extensibility model. I know some of these things. And and using
215
00:20:24.255 --> 00:20:25.455
my expertise,
216
00:20:25.775 --> 00:20:27.695
I'm the domain expert here over
217
00:20:28.340 --> 00:20:35.059
AI even though it has it knows stuff I don't know sometimes. You know? I'm very impressed by it. But I'm
218
00:20:35.140 --> 00:20:38.580
I'm kinda still looking at what it's doing while it's doing it
219
00:20:38.900 --> 00:20:41.940
and correcting it when I see that it goes down a wrong path.
220
00:20:42.525 --> 00:20:49.804
And if I didn't do that, I wouldn't be as fast. I wouldn't be as effective. I wouldn't be able to ship as many extensions that I've done. I think I've done
221
00:20:50.525 --> 00:21:04.249
12 extensions in the past, like, four months. Wow. Yeah. Productivity booster. Absolutely. Oh, my my main two. But but, again, the only reason I'm, like, 10 x in my productivity or five x or something right now is
222
00:21:04.649 --> 00:21:07.130
because I don't have that code maintainability
223
00:21:07.130 --> 00:21:08.489
issue. Yeah.
224
00:21:08.889 --> 00:21:14.345
Or not issue. Right? It's like I don't the code is not an asset for me in this particular case.
225
00:21:14.745 --> 00:21:17.945
Yeah. Exactly. Yeah. Yeah. I got it.
226
00:21:18.265 --> 00:21:18.905
So
227
00:21:20.185 --> 00:21:23.785
I wanted to ask you this. What is your favorite feature of Visual Studio?
228
00:21:24.985 --> 00:21:25.625
Oh, man.
229
00:21:26.640 --> 00:21:28.240
Don't make me choose
230
00:21:28.480 --> 00:21:30.880
between my children here. Okay. Or
231
00:21:35.040 --> 00:21:36.080
a favorite.
232
00:21:37.360 --> 00:21:38.240
Yeah. Yeah. Yeah.
233
00:21:40.815 --> 00:21:43.774
I'm very big on the small things, the quality of life,
234
00:21:44.495 --> 00:21:45.374
delighters.
235
00:21:46.414 --> 00:21:55.615
So something as simple as holding down shift while scrolling the mouse to do horizontal scrolling in the editor. Do I use it all the time? No. But I love that it's there.
236
00:21:57.350 --> 00:22:07.990
The fact that I can hover over any reference to an image, like, it's a HTML file that have an image tag and then it has, like, some sort of path, I can just hover over that and see what the image looks like
237
00:22:09.350 --> 00:22:13.415
and the size of it. Like Yeah. Small things that
238
00:22:13.575 --> 00:22:19.255
help me answer questions that otherwise would have taken me not necessarily a long time, but a little bit of effort to find out.
239
00:22:20.535 --> 00:22:22.535
I I'm very big into that type of stuff.
240
00:22:22.855 --> 00:22:24.455
I think Visual Studio is so good.
241
00:22:25.399 --> 00:22:29.159
All those the the big things for me has been kinda taken care of.
242
00:22:29.720 --> 00:22:40.865
Like, I can do those big thing. I can create WPF applications, right, that do
amazing things on the desk desktop or APIs for, you know, or or web web files sorry, websites and so on.
243
00:22:42.065 --> 00:22:50.545
So so for me, it's the quality of life. Like, do I wanna stay in Visual Studio all day long, seven days a week, or five days a week. Right? Mhmm. Eight hours to ten hours?
244
00:22:51.809 --> 00:22:54.529
And what are the things that make me go
245
00:22:55.250 --> 00:22:56.369
get angry
246
00:22:57.090 --> 00:23:00.690
or annoyed? What are the paper cuts? What are the things that
247
00:23:00.850 --> 00:23:10.085
you know, it's like it's like your own house. Like, if if you if your home office you're in or whatever has, like, a a color wall you don't like,
248
00:23:10.325 --> 00:23:15.365
you wanna change it. You're gonna feel better sitting there all day long. You're gonna be more excited to go to work.
249
00:23:15.685 --> 00:23:18.085
So I I wanna find and
250
00:23:19.205 --> 00:23:34.805
it it it and it there's a correlation between that and then, I think, other users. So the reason I wake up in the morning, the reason I work on Visual Studio is because I wanna make Visual Studio, like, a thing that makes people excited to start their workday in the morning.
251
00:23:35.605 --> 00:23:38.565
And I think a lot of it is those little things. Now
252
00:23:38.725 --> 00:23:39.845
those little things,
253
00:23:40.565 --> 00:23:41.365
they have to
254
00:23:42.085 --> 00:23:51.320
you have to have the fundamentals right, like no bugs, no issues that are, like, annoying or sorry, not annoying, but blocking you. Like, those fundamentals have to be in place first.
255
00:23:51.880 --> 00:24:08.534
You have to be able to actually perform the task you wanna do, and then you can add the delighter layer layer you know, that can come later. Now we work on all of those things in parallel. Like, think everybody does. Right? Yeah. But but those are the things that stick out to me because those are the things that make me smile.
256
00:24:09.735 --> 00:24:15.254
That's yeah. That's lovely. Things that delight you. I like that. Mhmm. And and and maybe
257
00:24:15.495 --> 00:24:20.600
what are what is one thing that you think almost nobody knows about that's in Visual Studio?
258
00:24:23.240 --> 00:24:31.000
I think there's a lot of things people don't know about Visual Studio. I I give a I give a talk called forgotten things you didn't know you needed in Visual Studio. Oh, cool.
259
00:24:32.914 --> 00:24:35.154
Because there there's just so many features.
260
00:24:36.755 --> 00:24:38.754
If you're a web developer or something,
261
00:24:39.075 --> 00:24:40.595
a feature called DevTunnels
262
00:24:40.595 --> 00:24:46.434
is probably not one you've used. We don't see a lot of usage of it, but it's absolutely phenomenal. You're, like, you're nodding. I can say you know what it is.
263
00:24:47.260 --> 00:24:48.779
But the fact that you can
264
00:24:49.180 --> 00:24:50.779
it solves that ancient
265
00:24:51.660 -->
00:24:54.059
in in today's world, that ancient issue
266
00:24:54.300 --> 00:25:02.845
where you're sitting inside your corporate firewall and you build a website and you wanna see what it looks like on a phone, on an iPad, all that, see how it renders correctly.
267
00:25:03.245 --> 00:25:09.245
And how do you do that without deploying it to, a public endpoint that you can type the URL into your device? Right?
268
00:25:10.045 --> 00:25:15.245
DevTunnel solves that. Microsoft's foot we foot the bill so that we open a a channel
269
00:25:15.730 --> 00:25:20.450
between your local host, basically, and the outside world, and you can just
270
00:25:21.009 --> 00:25:23.969
in any in any on any device, can access
271
00:25:24.130 --> 00:25:30.049
your local machine's website running right there. So that's that's a huge one for for web development,
272
00:25:30.835 --> 00:25:32.274
one that I really like.
273
00:25:34.115 --> 00:25:35.634
General
274
00:25:35.634 --> 00:25:36.434
stuff
275
00:25:36.434 --> 00:25:43.715
that people don't use because probably they don't don't know about our saved window layouts is one that I'm very happy about.
276
00:25:44.610 --> 00:25:50.370
I don't use that. I don't know. Yeah. A lot of people don't use it. It's funny because I use it all the time.
277
00:25:51.650 --> 00:25:52.210
But
278
00:25:52.770 --> 00:26:03.174
because I, you know, I have to move from, like, a laptop to then into a docking station where I have bigger monitors and so on. So being able to move with one one click,
279
00:26:03.415 --> 00:26:08.054
change your layout of where your solution explorer and your output window and,
280
00:26:08.135 --> 00:26:11.975
you know, your Copilot chat window and all those different things are laid out
281
00:26:12.770 --> 00:26:14.210
is super important.
282
00:26:14.450 --> 00:26:16.929
I because I can go from one perfect
283
00:26:16.929 --> 00:26:25.169
setup to the next perfect setup within the constraints I have with the monitor size and how many monitors I have and all those type of things. Okay. So so that's huge.
284
00:26:25.804 --> 00:26:34.284
And in that same vein, I wrote a blog post recently. You know, Fancy Zones is a is a feature out of what's called Microsoft PowerToys.
285
00:26:34.445 --> 00:26:39.164
It allows you to take any window and, like, snap into, like, certain positions around the screen.
286
00:26:39.860 --> 00:26:46.420
Windows have some of it built in. You can, like, snap to the right or to the left, but this one allows you to do completely customized zones.
287
00:26:47.300 --> 00:26:49.540
And there's a setting inside
288
00:26:50.260 --> 00:26:52.179
Visual Studio that can
289
00:26:52.740 --> 00:26:53.460
make all
290
00:26:54.015 --> 00:26:55.294
tool windows
291
00:26:55.615 --> 00:26:59.294
have their own be like their own window. They show up in the taskbar,
292
00:26:59.295 --> 00:27:02.815
but you can snap them to a fancy zone. So if you have multiple monitors,
293
00:27:03.135 --> 00:27:05.455
you can you can, like, just detach
294
00:27:06.030 --> 00:27:11.710
like, solution explorer, test explorer is a very common one because people wanna expand that, have it out large.
295
00:27:12.030 --> 00:27:19.870
Just put that over on a separate monitor, and you can, like, snap it into place. You can maybe have it side by side with something else that you wanna look at on that secondary monitor.
296
00:27:20.585 --> 00:27:23.545
And so people don't know you can do that. It's
297
00:27:23.545 --> 00:27:25.304
not enabled by default because
298
00:27:25.705 --> 00:27:34.105
I think that most people don't have that setup or that need. Mhmm. And a lot of people do, and so finding that setting is really nice. Just search for the word float
299
00:27:34.420 --> 00:27:35.700
in the settings.
300
00:27:36.260 --> 00:27:38.580
I'm gonna try that one. That's cool. Okay.
301
00:27:40.100 --> 00:27:45.460
Cool. So that's that's already a lot of stuff. Maybe a last topic that we can go into.
302
00:27:46.420 --> 00:27:49.700
I really like that we now have Visual Studio 2026
303
00:27:49.815 --> 00:27:53.734
because it's beautiful, it's snappy. Finally, it's just lovely.
304
00:27:54.134 --> 00:27:54.695
I
305
00:27:55.014 --> 00:28:01.174
create Pluralsight courses, and I'm just about to create a Pluralsight course about debugging and testing for 2026.
306
00:28:01.654 --> 00:28:04.720
And then I heard there's a Visual Studio 2027
307
00:28:04.720 --> 00:28:05.520
coming.
308
00:28:06.080 --> 00:28:06.720
So
309
00:28:07.280 --> 00:28:08.559
is is that true,
310
00:28:09.040 --> 00:28:10.480
and and what's in it?
311
00:28:11.200 --> 00:28:12.080
Yeah.
312
00:28:13.280 --> 00:28:18.125
That is true. And there's Visual Studio 2028 and 2029
313
00:28:18.125 --> 00:28:20.445
and so on. So every year,
314
00:28:21.085 --> 00:28:24.725
starting with the 2026 release in November
315
00:28:24.725 --> 00:28:25.725
2025,
316
00:28:26.205 --> 00:28:27.405
every November,
317
00:28:27.565 --> 00:28:29.645
we're gonna rev the the
318
00:28:30.220 --> 00:28:31.419
version number
319
00:28:31.659 --> 00:28:32.460
to
320
00:28:32.700 --> 00:28:36.299
be the next year's version. So Visual Studio 2027 will
321
00:28:36.779 --> 00:28:41.019
we will release that in November 2026 and so on and so forth.
322
00:28:41.580 --> 00:28:47.755
Okay. But it's not gonna be a side by side install. You know? Right now, you can have 2022 and 2026
323
00:28:47.755 --> 00:28:54.394
installed side by side. Yeah. That's not what this is. This is think of this as now Visual Studio's evergreen.
324
00:28:55.034 --> 00:29:09.700
Mhmm. K. It's an in place update. You just take the next so when you when you reach November and you have Visual Studio 2026 and it says, hey. There's an update just like you have today. It says, hey. There's an update. Do you wanna click update? You do that, and then all of sudden, it's just called 2027,
325
00:29:09.700 --> 00:29:11.060
but it's just an update.
326
00:29:12.595 --> 00:29:15.475
K? Now there could be something under the hood that's different.
327
00:29:16.035 --> 00:29:16.995
Like extensibility
328
00:29:16.995 --> 00:29:19.554
models, API versions, and so on could
329
00:29:19.715 --> 00:29:20.434
change,
330
00:29:20.914 --> 00:29:24.754
but it wouldn't affect you. It would would affect other things, but
331
00:29:25.475 --> 00:29:26.434
but that's happening.
332
00:29:28.100 --> 00:29:36.820
This this is how we're doing it these days. So Good. Yes. So it it means that at some point, you can just refer to it as as Visual Studio.
333
00:29:36.980 --> 00:29:38.180
Yeah. Right? And
334
00:29:38.500 --> 00:29:44.795
and the year is just a way of saying, hey. I got the April update of Visual Studio 2026.
335
00:29:45.035 --> 00:29:47.835
Like, otherwise, how would you reason about what version it is?
336
00:29:48.395 --> 00:29:52.235
Yeah. Very version. Very easy when you just say, hey. It's the month of 2027.
337
00:29:52.235 --> 00:29:55.860
Right? Like Yeah. April 2027. That's the update I'm on.
338
00:29:56.420 --> 00:29:59.940
And so it makes that version thing so much simpler.
339
00:30:00.660 --> 00:30:05.620
Ah, okay. Yeah. Yeah. Okay. So it's not a huge breaking change. It's an update.
340
00:30:06.820 --> 00:30:07.060
Yes.
341
00:30:08.145 --> 00:30:08.785
Okay.
342
00:30:09.265 --> 00:30:12.065
Gone are the days of of breaking changes, you know,
343
00:30:12.465 --> 00:30:26.270
knock on wood, because we we separated the the runtimes and the build tools, the tool sets, and all that for c plus plus and .net or whatever to run independently of how we version and and ship updates to Visual Studio, the IDE.
344
00:30:26.350 --> 00:30:31.150
And so they're not detached, which means you can update the IDE without updating your build tools.
345
00:30:31.790 --> 00:30:34.590
And so you can you can always be in the latest feature set,
346
00:30:35.164 --> 00:30:40.364
but then whenever you're ready, your team is ready, you can update your your tool sets.
347
00:30:40.684 --> 00:30:45.164
And that's important because, you know, when you when we ship Visual Studio on a monthly basis,
348
00:30:46.365 --> 00:30:49.725
we want you to take those updates. You also probably wanna take those updates,
349
00:30:50.350 --> 00:30:59.229
But you couldn't in the past because you said, no. No. I have to be on this old version because we're only running on, you know, this this version of the c plus plus toolset or whatever.
350
00:30:59.549 --> 00:31:04.429
And so now those are separate, and they update on their own cadence and Visual Studio supports it all.
351
00:31:05.894 --> 00:31:06.934
Very cool.
352
00:31:07.095 --> 00:31:07.734
Okay.
353
00:31:08.054 --> 00:31:08.695
And
354
00:31:08.934 --> 00:31:13.735
are there any very exciting new features coming, like big things that you can talk about?
355
00:31:16.870 --> 00:31:20.149
I think we have we have a lot of stuff cooking right now.
356
00:31:20.710 --> 00:31:22.070
A bunch of
357
00:31:22.549 --> 00:31:25.750
AI tools, a lot of refinements, a lot of delighters coming
358
00:31:26.230 --> 00:31:26.789
Mhmm.
359
00:31:27.030 --> 00:31:31.245
A lot of fixes. We're fixing more bugs now than we ever have before.
360
00:31:32.045 --> 00:31:41.005
It's not because people are reporting more bugs. It's because we're our focus has has been changed a lot over the past two, three years to really focus on what the users
361
00:31:41.085 --> 00:31:45.565
are asking us to do. Right? Right. You could think, oh, why didn't you do that before? Well,
362
00:31:46.530 --> 00:31:47.410
reasons.
363
00:31:48.530 --> 00:31:49.490
Bad ones.
364
00:31:50.770 --> 00:31:57.410
So it's like we're we're that's something we're really keen on. Like, what are the things we can do to put a smile on people's face? How can we
365
00:31:58.144 --> 00:32:02.144
lean into the strengths of Visual Studio? I think you're gonna see more coming in.
366
00:32:02.705 --> 00:32:09.984
Like, we're gonna continue evolving the debugger. Like, it's gonna it's just getting better and better all the time. But there are other things that's gonna be better.
367
00:32:10.945 --> 00:32:13.289
I think you're gonna see test different
368
00:32:13.690 --> 00:32:16.330
ways. You know, unit testing is gonna be improved.
369
00:32:18.570 --> 00:32:22.409
Stuff like reviewing code, PRs, that type of stuff
370
00:32:22.810 --> 00:32:23.929
is gonna be
371
00:32:24.170 --> 00:32:25.450
improved a lot as well.
372
00:32:26.145 --> 00:32:30.225
And the reason for that, of course, is that, you know, when you have AI,
373
00:32:30.305 --> 00:32:37.745
you know, writing parts of your code base, you need to have guardrails in place. Right? So that's why unit testing all of a sudden becomes this very important thing
374
00:32:38.305 --> 00:32:39.025
where
375
00:32:39.265 --> 00:32:45.909
that has to be top notch. So you can have your guardrails ready. Otherwise, you can't really unleash agents to do work if you if
376
00:32:46.309 --> 00:32:49.349
you can't have some sort of trust that it won't break stuff.
377
00:32:49.669 --> 00:32:50.309
Yeah.
378
00:32:52.230 --> 00:33:02.674
But everybody benefits from that. Everybody has a better unit testing. That's that's kind of where that's the that's the kind of the balance I was talking about in the beginning we're trying to look at. How can we make everybody better,
379
00:33:02.835 --> 00:33:06.355
but also, like, by leaning into what Visual Studio is already good at
380
00:33:06.930 --> 00:33:14.530
and the use cases you use Visual Studio for, and then how a can AI then augment that to make it even better for people who opt into that. Right?
381
00:33:15.250 --> 00:33:21.810
Yeah. So PR is like reviewing code, making sure that your code is like it would also be nice if you can
382
00:33:22.054 --> 00:33:25.975
before you commit, you can make sure that your all your coding
styles,
383
00:33:26.054 --> 00:33:26.534
code
384
00:33:27.335 --> 00:33:31.414
standards, all that has been taken care of so that you don't spend time
385
00:33:32.215 --> 00:33:39.469
reviewing code, and they just you just look at code styles. It turns out according to GitHub, they did a cert survey or some sort of stuff
386
00:33:40.110 --> 00:33:45.549
some years ago. I think it was 25% of code reviews are spent on coding standard.
387
00:33:45.789 --> 00:33:59.705
Oh, okay. So it would be really nice if we could just get rid of that, you know, by having it done automatically or having it done while you write the code or whatever it is. And so that benefits both the agent agent work that it will write according to your standards,
388
00:34:00.105 --> 00:34:05.240
but also for your own stuff. So you don't send up you know, waste 25% of code reviews
389
00:34:05.960 --> 00:34:07.720
thinking about that aspect.
390
00:34:08.280 --> 00:34:08.920
Yeah.
391
00:34:09.240 --> 00:34:09.880
Okay.
392
00:34:10.200 --> 00:34:13.480
Well, those are all great features. Quality
393
00:34:13.480 --> 00:34:14.360
of codes
394
00:34:14.520 --> 00:34:17.240
so that you can unleash agents to just write stuff,
395
00:34:17.885 --> 00:34:20.685
and then you can review it properly. You can test it properly.
396
00:34:20.925 --> 00:34:35.260
All those things are super important and the debugger as well. That I I like that a lot because I use that all day. So that's that's great. And then you'll you're gonna continue to see updates to all sorts of features also. Like, hot reload is getting better and faster.
397
00:34:35.580 --> 00:34:36.460
HTTP
398
00:34:36.460 --> 00:34:37.100
file
399
00:34:38.540 --> 00:34:43.020
features are are getting better and more pretty and and bet you know, all the time.
400
00:34:44.535 --> 00:34:49.335
So so everything everything is gonna be lifted. Like, we're we're gonna make everything better,
401
00:34:50.694 --> 00:34:57.174
but I just mentioned a few kinda key areas that we're very interested in because it it fits that sweet spot
402
00:34:57.450 --> 00:34:58.250
between
403
00:34:58.410 --> 00:34:59.770
people using AI,
404
00:35:00.010 --> 00:35:02.170
people use it occasionally, and people who don't.
405
00:35:02.410 --> 00:35:08.010
Yeah. Everybody wins when we do those balanced things. And so there are some big buckets
406
00:35:08.650 --> 00:35:09.849
that, like, falls,
407
00:35:10.404 --> 00:35:11.685
like, right into that.
408
00:35:12.085 --> 00:35:12.805
Okay.
409
00:35:13.444 --> 00:35:15.685
Cool. Well, I look forward to all that stuff.
410
00:35:16.644 --> 00:35:22.005
It will come. I will just update Visual Studio, and boom, it it will be there at some some point.
411
00:35:22.325 --> 00:35:24.565
Yeah. Get get the in insiders.
412
00:35:26.150 --> 00:35:28.630
You might already be on it, but maybe the listener
413
00:35:28.710 --> 00:35:33.190
out there are just using the Stable channel, which is cool too. But if you really wanna get
414
00:35:34.390 --> 00:35:45.325
early access to all the latest and greatest, you're gonna be a month ahead of the game. We released the insiders a month ahead of of the stable channel, so you you kinda get the heads up there.
415
00:35:46.765 --> 00:35:49.645
And and you'll see that there's so much churn every day.
416
00:35:49.965 --> 00:35:57.540
I get the daily builds inside, and, like, every day, it's getting like, you can you can just tell. It's better every day. It's it's small things, sometimes bigger things, and
417
00:35:57.940 --> 00:36:00.020
so get the insiders. I think
418
00:36:00.579 --> 00:36:01.700
you'll enjoy it.
419
00:36:02.180 --> 00:36:05.540
Alright. I'll put a link to that in the show notes as well.
420
00:36:05.859 --> 00:36:10.019
Is there anything else that you want to share, like, where people can find you personally?
421
00:36:11.825 --> 00:36:14.385
On Twitter. I think that's the or X rather.
422
00:36:14.625 --> 00:36:16.385
I think that's the most direct.
423
00:36:16.865 --> 00:36:19.984
So my Twitter analyst is m Christensen
424
00:36:20.065 --> 00:36:22.465
on on X, and I, you
425
00:36:23.105 --> 00:36:27.330
know, I I keep it to pretty much just Visual Studio stuff. So
426
00:36:28.530 --> 00:36:34.130
so there's a lot of I do a lot of, like, teasing new features, screenshots I just get from
427
00:36:34.690 --> 00:36:43.585
the engineering team. And so if you wanna see what what's right now, what do we have on the internal builds, what's coming, even before it hits the insiders,
428
00:36:44.705 --> 00:36:45.345
yeah,
429
00:36:45.505 --> 00:36:51.105
you wanna you wanna follow me on on on x? I I spill all the secrets there. Okay.
430
00:36:51.670 --> 00:36:58.630
Okay. So everybody go look there and connect there. Alright. Yes. Excellent. Thank you very much for talking with me today.
431
00:36:58.950 --> 00:37:00.230
Yeah. Thanks for having me on.