text
stringlengths
0
2.68k
I think maybe one of the things that might happen is that there's a difference between solutions that are more sitting at that SaaS, level versus services that are more at that systems level. I think that that SaaS level is going to start to be something that is more easily extended. Today, when we think about somethin...
But I think that what this is now kind of enabling is for you to start to build other systems, other automation on top of other systems much more easily... Even without the API, to be frank, because now it can just traverse the DOM, or whatever it needs to do... And I think that means that a lot more software becomes a...
The other thing that I think is super-interesting is we also spend a huge amount of time right now on the view, creating the view.
**Jerod Santo:** Sure.
**Amanda Silver:** Like an MVC kind of model...
**Jerod Santo:** Yeah, totally.
**Amanda Silver:** I think in the future, it might just be that you focus on the model, and the view you actually go and specify with a design system.
**Adam Stacoviak:** Well, I saw a T-shirt downstairs, it had a bunch of things crossed off. I think developer was one of them, and something else, and then it just said "Builder".
**Amanda Silver:** Yeah.
**Adam Stacoviak:** And so I feel like y'all have been ahead of the times, basically, with I think people becoming builders, rather than just developer, or just designer, and the word 'just' not pejoratively, if that's even a way to say it... But more so builder. Everybody's a builder, and everybody can contribute.
**Amanda Silver:** Yeah. Love it.
**Jerod Santo:** I have a question that I think maybe would have been way better back in the VS Code part, but as we wrap up --
**Amanda Silver:** Spicy?
**Jerod Santo:** I don't know if it's spicy or not, but I'm curious... We were kind of debating VS Code's foothold, and is it a strategic advantage, and this and that... And the open sourcing of that, and that it's been a good thing for Microsoft... What we've seen recently in the vibe coding space is VS Code forks.
**Amanda Silver:** Uh-huh.
**Jerod Santo:** And these forks come up fast and furious, and they're getting huge valuations...
**Adam Stacoviak:** They sell for billions.
**Jerod Santo:** Right, they sell for billions. They're getting large user bases very quickly, or at least it seems like they are... And in a sense, that's a little bit of a backfire, because now you're providing VS Code, this platform, which is just forkable, and now you're giving competitors an opportunity to just ca...
**Amanda Silver:** \[01:04:01.02\] No, I mean I --
**Adam Stacoviak:** You Kelsey Hightowered that one. \[laughter\] I love you, Kelsey...
**Amanda Silver:** I think that there's real real innovation that's happening in the industry, and a level of competition that we haven't seen for a long time. So I have a tremendous amount of respect for you know the competition that we're seeing right now in the code editing space.
I will say, like - yes, I think that there is a lot that has been built on top of the open source codebase of VS Code, and I think that is creating a foothold that allows others to kind of go and create additional, you know, features or differentiation on top of it... But that's I think one of the reasons why we've dec...
And we certainly believe in, you know, whether it's VS Code, or TypeScript, or anything that we do in like the Azure SDKs, or .NET - all of that's open source. Half of what my team works on is done in the open and open source. You know, we certainly see that especially when you're trying to build a community around a t...
And I think what we hope to see now is - there's a tremendous amount of innovation that's been happening in AI-based coding. What we hope to see is more of the community contributing back to the VS Code codebase to really advance the state of the art for everybody.
**Jerod Santo:** Yeah.
**Adam Stacoviak:** I'm not sure I would call them competitors, though...
**Jerod Santo:** You don't think Windsurf is a competitor of Copilot?
**Adam Stacoviak:** I would say --
**Jerod Santo:** I'm going to use one or the other, aren't I?
**Adam Stacoviak:** I guess so... But is that your customer, for a lack of better terms?
**Jerod Santo:** Oh... They want all the customers? Don't you?
**Adam Stacoviak:** I don't think so. I think --
**Jerod Santo:** Let her answer... \[laughs\]
**Adam Stacoviak:** Well, this is what I assumed you were thinking. And you said a lot of things, but you didn't say this. But if I read between the lines and I think - if I were you, I wouldn't see it as competitors, because you are focused on developers using VS Code, and I don't think they're not not developers, but...
**Amanda Silver:** Yeah. Right --
**Adam Stacoviak:** A developer writes code and cares about the code, whereas the other way is -- it's not so much less about the code, it's a different way to get there. That's how I look at it.
**Amanda Silver:** So I think I think there's kind of two pivots to that. First of all, I think that code editors, generally, if your primary task is to write code, then I would say any of the popular code editors are competitors, in a sense. But to the point earlier that we were talking about, we believe that we live ...
I think to your point around vibe coding and how does that relate - I see vibe coding as a really interesting evolution. It's not quite --
**Adam Stacoviak:** I'm throwing zero stones at that. I'm a agnostic when it comes to all innovation. Whatever gets us to the next place, we're gonna love it. That's what I'm for.
**Amanda Silver:** Totally.
**Adam Stacoviak:** And if vibe coding is one of the ways we get there, or it invites more people in to build software - cool.
**Amanda Silver:** \[01:07:59.15\] I think vibe coding invites a lot of people in to go build more software. I think that it's not your typical pro dev software developer, but I think that what vibe coding has kind of started to create is more of this pattern of what I would call like natural language-driven developmen...
**Adam Stacoviak:** Something \[unintelligible 01:08:24.07\]
**Amanda Silver:** ...a full spec. And the spec is still written in natural language, it's not written in C\#, or TypeScript, or JavaScript, or anything like that. It's written in a natural language; English in my case, but it could be written in whatever. But then you take that spec, and then you use that spec as the ...
From there, then it's like, okay, well, now that PM can contribute even a spec for a feature, or they can contribute a spec for the initial product... The active testing could also be, in some senses, a large prompt. The designer could contribute a design system into the codebase... And so I think what we start to see ...
**Jerod Santo:** It's all the metadata.
**Amanda Silver:** ...for all of the systems, and all of the different, you know, phases that you go through of the software development lifecycle.
**Jerod Santo:** Yeah. I think that's really insightful, and one of the things that I've noticed as an experienced developer trying to adapt and adopt the tools is that software isn't built in like a chat scenario. Like, you don't chat your way to a software system, because there's just like so much chatting that goes ...
A spec that gets created through - whether it's a vibe session, or just a peer programming session... Now I have this written document that evolves. And it would be so cool to be able to take that spec and be like "Alright, here's a different model." You know, start fresh. We don't need to use the code. We have the spe...
**Amanda Silver:** Yeah, it is. I mean, we now are starting to do more spec-driven development. We have .prd files that, you know, would be the description of the spec. And those kinds of things are starting to get checked into the codebases. But I think also there was a nugget in what you were talking about in terms o...