¶ Welcome to Syntax!
Welcome to Syntax, live from... Where are we? San Francisco, live from New York. We are not live at all. We're recording here at GitHub Universe 2025. We were here last year, which was pretty interesting. And it's nuts to see. Like last year, we were talking about like better co-pilot. like tab completion and stuff like that. And now it's just like agents and all this stuff. CJ hates. We're going to, we're going to go through a couple of things here. We're going to kind of.
rattle through all the announcements that they have and talk about that as to like are they catching up to to cursor and all these things and and what what is the interesting stuff and how does it all work together we're gonna talk about our badges which is really cool i think possibly very maybe even more interesting to some of the audience and uh
Yeah, it was good. We had a meetup last night. Thanks to everybody who came out. That was a hoot. Oh, yeah, it was great. Everybody, man, we had a big turnout last year for the meetup. Yeah. And it was just like a great mix of the types of folks from all different companies. and working on different problems, fans of the show, and this year was just even better. We had a massive table of free stuff. We had...
security guards and police officers coming up and being like, can I get some of this stuff? Yeah, we had a San Francisco cop driving around the city with our hat on. Yes, our internet hat. Yeah.
Props to everyone who came out. That was always really fun having meetups and getting to chat with people because you get to hear the type of stuff people are working on, the problems that they're hitting, what they're learning. You don't necessarily hear that stuff every single day. We try to solicit it as much as we can. but just talking one-on-one with people and also like... All night long, talking one-on-one. There's a lot of devs who came from...
companies that are not allowed to talk about stuff that they work on. And they gave us the scoop on some of that stuff. And it's always really interesting getting to hear from these huge companies that use this tech. But they're not allowed to talk about it. Huge companies that we cannot name. Yeah. Yeah. Just fruit companies and stuff like that. Oh, man.
Yes. It was great. So shout out to everybody who showed up to that. And then we also had a big syntax team meeting. We've got the whole team here from all over the globe. We are a global team now. It's a Canadian podcast with a global team. You always see the stuff like Made in America with international components. This is a Canadian podcast with international help. I think only what?
A very small percentage of the team is in Canada now. I don't know if we can continue to say that. It doesn't matter. You would just declare it if you'd like. It's like a grassroots. It began in Canada mostly. Just as much as the team lives in Colorado. This is a Colorado podcast. I'm here too, by the way. Hello. CJ, what's up? CJ is joining us in the booth at GitHub U. As a resident AI hater. Yeah. And I'm going into this blind, so I did not watch the keynote.
I'm just going to be live reacting to what these guys tell me, and I'll give you the real... feedback about it, I guess. I don't know. So, yeah, Wes and I will give you the Microsoft shill take and then CJ gives you the real take. Yeah, leave your comments right now. We hear you. We're shills and everything like that. No, we're not. This is not an ad.
paid for any of this. It was simply just checking it out and reporting what's going on because we know a lot of you guys use these tools. Speaking of shilling.
¶ This year's GitHub Universe badges were next-level
These GitHub badges are really sick. Yeah, it's the coolest part of this conference. Last year, the badge had an e-ink screen, and you could hack it to put whatever you want. Yeah. This year... It's a different level. I'll have to post pictures of this. I made a GoldenEye64 logo for Syntax and put it on here. There is a Flappy Bird. There is an Etch-A-Sketch. There is a Tamagotchi. It is a whole ass screen. There's a Tamagotchi? I don't know. So last year it was a...
It was made by Raspberry Pi, but it was technically like an Arduino. And I believe that is the same this year, but it also has a Wi-Fi chip in it. So basically the whole badge is a printed circuit board that has a Wi-Fi chip. Wi-Fi chip in it. It's got a LiPo 3.7 volt battery, USB-C to plug in. And then the whole thing is running MicroPython, which is like you code these apps in Python. You can...
You can run any code you want on it, but the framework for building apps on this thing is preloaded, so you write them with MicroPython. Absolutely wild. That is a printed circuit board. This is a badge. We're not clear. This is a conference badge. You know, the thing that's normally just a little plastic thing hanging. My kids are going to go absolutely nuts.
playing Flappy Bird on this thing. Yeah, I got an Etchiskets running on it. And as soon as I can, I'm going to hook it up to the syntax API. and like pull the latest episode or or something like that because now that it literally has wi-fi on it like previously it was e-ink so you had to hook a battery up and then once the e-ink was set you can unplug it and it will just stay that way for forever
But this is an actual full-color display. Brought in my GitHub contributions and all that stuff. Oh, you got it hooked up. I haven't hooked mine up yet. To connect it to the Wi-Fi, you actually have to connect it to your computer. Is he like modify a config file? Is that what it was? Yeah, you modify a config file. And then I actually was messing with the gallery and I was trying to install some other images. I had this really wonderful photo of Wes.
with his long hair that I was trying to get on my badge, but it kept crashing the memory on it for some reason. I think it's this photo specifically. That's his face. The badge was just like, I can't let you do that. It's good. I actually bricked mine, not crashed it. I bricked it. You had to reflash the firmware? Well, what had happened is that, like,
I uploaded the Wi-Fi credentials and it wasn't working. So I was just like holding down random combinations of buttons. And I like totally bricked the thing to a point where it started running in like a bootloader mode and like a bootloader mode on these. These things is where you can change like the lower level software that it runs on. And I did something. So luckily they took it back and gave me another one. Oh, nice. I goofed it up pretty far. Can we just appreciate that out of all the...
Types of people who would end up breaking their badge, Wes, managed to probably be the first person, which is so endlessly predictable. And I told the folks from GitHub, and they're like, good. It's hacker mentality, you know? Dip into it. We're happy that you bricked your badge. Yeah. We're very happy about that. Yeah. So pretty, pretty fun. Maybe I'll do for another. We did, we did an episode on like, like electronics and microcontrollers, maybe like a year and a half ago, but.
Now that we have this little thing, I think there's an appetite for something else. I had a great time on this last night. In fact, I didn't even like... go to bed because I was up in the Python for this last night. Because you guys got yours early, so you've been able to hack on it a little bit. Oh, yeah. So tonight, CJ will stay up. Exactly. Year-round. That's my night. And be able to do it. Yeah. Cool.
¶ Keynote recap: GitHub Agents, Copilot, and Mission Control
Do we want to get into the keynote now and talk a little bit about some of the announcements? Yeah. Yeah. So the keynote at these things, as you can imagine, is always, you know, we're at GitHub Universe. So at GitHub Universe, you can imagine a keynote's going. to be fancy new features in GitHub. There's also quite a bit about VS Code as there was last year. Like last year during the keynote, it was a lot of like, yeah, okay, VS Code is starting to compete with Cursor.
are we even allowed to talk about cursor kind of situation, right? Like this year, it was definitely like a big message was features that exist already that are now being way more useful. There's a new center, mission control center for agents within GitHub, where basically you are able to control and send agents off working on problems. within GitHub in a more organized manner. So you could assign things even last year or half a year ago, whatever. You could have a PR. You could assign it to...
co-pilot. Co-pilot could go off and work on it. It could do it in the background and then it would come back with answers. But now with this... With this new mission control, it's a lot more integrated where you can send a cloud agent to go and work on it. That cloud agent can start to work on it. If you want to pick it up yourself, you can then have it open directly in your editor, continue working on it. You can use other agents.
In there, you can use Claude Code. You can assign things now to Claude Code. You could assign things to Codex rather than just assigning it to only Copilot. How were we feeling about that? Have you guys used assigning issues? Slightly. I've done it in a GitHub issue. You can say, hey, Copilot, check this out. And then it goes off. And there's a link that will pull up the in-browser editor showing you what it's doing. So I've done that a couple of times.
I think the big thing that they're fixing here is that it just felt clunky previously. So like... If you want to kick off an agent to build a task, you have like a couple options, right? You can use cloud code on your computer. You can throw cloud code like on a VM, but then it doesn't have access to all of your things. You can kick it off.
on github.com but then like i found in that workflow it's like well it didn't really do what i wanted and right now i have to like sit here and wait for it and then go back and type on what I wanted. And it's like, well, now I want to edit some of the code. So like now I got to like check that out. And like now the seems like the flow of this seems to be a lot easier where like the the blur between.
It actually happening on GitHub and happening in your editor is a lot better. So all of these agents run in GitHub Actions and GitHub Actions can run in your own infrastructure, which is... that's huge yeah for for people they want to bring their own infrastructure you don't want to either necessarily pay for that or there's like security concerns you don't you can't run your own code on somebody else's servers for whatever reason
To me, that seems like kind of just like the biggest feature here is now you have a place to run your agents. You don't have to like set up a server. You don't have to like configure things manually. It's kind of just like a nice point and click way of having your agents running in the cloud in the background.
I think the biggest thing here was the fact that you can bring Cloud Code, you can bring Codex, you can bring your own agent. Because I was watching this keynote and I was like, this is awesome, but... What if we don't want to use the GitHub flavor of everything? Is it going to be their only their own thing? GitHub is just like, yeah, you do what you want. GitHub is where we...
we have all of our software, all of our, our actions. It's where we build everything. And if, when it comes to all this agentic stuff and it doesn't, it's either like bolted on the side, you know, via some like plugin, but like, no, this is like first class support.
for all the other ones. And one thing they teased was that you can now, if you have a GitHub... co-pilot subscription you can just log in to codex yes which is open ai's coding agent and like it just comes with your subscription totally to have access to i don't know what the like gotchas are on that yet but
That's pretty sick. And I'm curious about that because I've had a co-pilot subscription because I am a GitHub star. I get access to the co-pilot stuff. Oh, my gosh. There's freaking royalty over here. Yes. I pay for it with my own money. I know. And that is why I got this side of the podcast booth all to myself because I said the star needs. He's a star. Yes. Okay. Hold on. Can we pause a second there? Like quick poll. How many of you got to meet.
Natia Nadella today. CJ? I did not. No, Scott? I did not either. Oh, yeah. Actually, I got to hang out with... We'll put the thing over top of the thing, but... Wow. I got to... Microsoft will like, will email us with these like guests. They have like a PR company and they'll email us with these guests where we're just like, no, we're not having like your like C-suite, whatever. Yeah. Like on here to bullshit about X, Y, and Z. Like that's not.
interesting for the people, the actual developers who write code that are listening to this type of thing. So they're like, who can we get? I was like, how about Satya? And they're like, we're working on it. And I'm like, yeah, right. Yeah, right. And then I got like a weird message last night. Being like, hey, come to 10 a.m., come to this location. Yeah, come to the pier. And Satya comes in and just pops out. And, man.
That was really cool to meet him. I gave him an internet hat, which you can get in our swag store. And that was a cool experience. That's the West mode, though. Anytime they're like, can someone so come on? And it's like, how about Zuck? Can we get Zuck? My goal is I want to get Zuck. But only ask them about coding. I don't give a shit about whatever you're working on right now. What are your actual thoughts about ReactJS? How do you feel about NextJS? Or just like...
So Sadia was talking about how like he used to be a developer and now like he still understands development, but it's like it's. how you develop is much different than Handy did a long time ago. I was like, can we get him on a CSS battle? Oh, wow. He vibe off. Give it a little while. Sadia can vibe with the co-pilot. Me and Scott will do, like, and CJ will do.
No AI, and we'll go head to head. That'd be great. Let's make it happen. Yeah. But anyways, you're a GitHub star. Yes, I am. And because of that... I don't even know what I was talking about. We were talking about the free codex access. So I've been using the co-pilot stuff. You can have access to agents, or not agents. You can have access to any of the models. I could have Claude, Sonnet, whatever, via co-pilot.
not via a Claude subscription. And you could use Copilot CLI instead of Claude Code, right? But I could also, in open code or anywhere else, I'm signing in with... copilot and then having access to the models. But my understanding of that is that the context windows are all shrunk on that via copilot. So that's what I'm curious about with...
Codex. If you're signing in with Codex, is it the same experience? Or is it the Walmart version? Is it the whole hog? Yeah, yeah. That's fair. Yeah, I guess to get the skeptics take here, like I'm looking at their blog posts on... Agent HQ, they're calling it. And there is a box for third-party agents. So it would seem that...
If you have direct third-party integration, third-party access, you would get the full version of Claude or whatever else. I don't know the details, but it would seem like you would need a subscription for each of those to set them up, maybe.
I don't know, skeptics take, like, this is, it's cool. I think, honestly, one of the things that burned me out about AI was I was trying to build an agent dashboard. Yes, I feel that. And, like, I was coding it up, but I kept running into so many issues. And to have...
a nice polished product and that uses your same subscription and supports all the stuff you like, it's decent. I'm not, I mean, I want to see it. I want to try it out, but it looks cool. Yeah. Yeah. You know, for me too, there's... You end up using this stuff and you go so far in one direction of like, okay, now I'm managing context. I'm a context engineer. Okay, now I'm getting into, I've hit these issues with agents. I need to be more deterministic. I'm getting into more deterministic.
workflows and tying in MCP servers with code rather than just like constantly LLM stuff and you just end up going further and further down this road just to get something that plays nice a little bit and one thing that I found to be absolutely fascinating with any of this stuff is when CJ released his AI coding rant, the comments, you can tell.
Where people are in that exact same journey based on the comment they leave. Because it's like, I almost want to be like. Just wait. Just wait like a couple weeks until you hit this specific issue, which you will. And then you're going to. do this to solve it, and then you're gonna go down this path, and then you're gonna go down this path. And it's almost like pulling that one more prompt lever just in a different way of being like, yeah, okay, maybe this next one is gonna...
actually solve all the issues here. But no, these tools are neat. And you know what? As somebody who did like to use the Copilot, assigning it to Copilot, especially for... shit I didn't want to do, like CI stuff. Oh, I want to set up a change sets and release workflow with changelogs. Honestly, I got better stuff to do in my time than just do that.
Telling co-pilot, hey, just go knock that out for me, and having it do that was really nice. But then there's other times when I would say, hey, fix this bug, and it takes a long time. the feedback loop is really long. That's, that's the biggest one for me is like the feedback loop. And then you need to like,
I need to hop it out of the agent into your editor. If it fails, you're just like, well, I suppose I'm just going to close this issue and then just do it myself now. So that's something I'm really curious about because it was an impressive demo to be like, all right, let's hop into our editor now.
Because, again, sometimes you just want the AI to get started. Sometimes you just want to do something and fix a bug or whatever and then move. I can do it. And that's really hard with the previous current flow. And if you want to see all of the errors in your application, you'll want to check out Sentry at sentry.io forward slash syntax. You don't want a production application out there that, well, you have no visibility into in case.
something is blowing up and you might not even know it. So head on over to century.io forward slash syntax. Again, we've been using this tool for a long time and it totally rules. All right. I think that nobody has figured out. the workflow to that yet yeah and like that's what a lot of people are saying this is the this is the new workflow like will this be
The workflow of like you kick it off and like there's also like you can have multiple custom agents like one that's really good at like Kubernetes, one that's really good at test driven development. That to me has been effective. I do have agents. I have a Svelte Pro agent, and that's good for Svelte specifically because the API changes. So having an agent that says validate specifically with Svelte MCP, use this specific instructions or use this, that...
has been way more effective than just yellowing prompts. Do you have a custom agent instead of an MCP server? I have a custom agent that uses the MCP server to do various things. But the agent codes and then it validates the code with the MCP server or it looks up docs. Yeah.
Okay. So it's like specific instructions for how to use the MCP server that doesn't bloat the context because that one agent has it? When to use, yeah, when to use the MCP server, when to, yes. Okay, cool. And that agent is good at doing... certain types of work. Yeah, specifically Svelte UI work. That makes a lot of sense. Especially if you're in an app that has backend and frontend and...
Yeah. And those might need to be different. And then you move it out of custom instructions because then I like I can tell it these are the like maybe not like these are the general things that I'm using, but these are the syntaxes that I would prefer to have or the. do not ever write my CSS. And if you do, just delete yourself from my computer. You are not good at this. What else do we got here? Plan mode. This is something that...
¶ Plan Mode and the future of collaborative coding
Kiro launched. When did you do your video on Kiro? No, plan mode is more like... Like Claude plan mode? Plan mode is more like Claude plan mode, less than Kuro. So it's not specs, it's just plans? Yeah. Okay, it's not spec-driven development. Yes, because when I saw that, the first thing I thought of, and I was going to tweet, oh, this Kuro. Yeah. But it's not, because they actually did add, like, to-dos in VS Code, but...
I found that, no offense to the VS Code team, because I know that that was like a much-wanted feature. I have found that those to be largely just decoration and kind of useless. Where in Kiro, it's more like, here's the specs, here's the steps. Let's dial in on this one thing. we can tackle this as a thing. But this plan mode that they announced is not that. This plan mode is definitely like a going back and forth with the agent.
before you begin any work. Okay. And which can be, in my mind, the most effective way to work because you can get a lot of these issues worked out ahead of time that it might just start going off on the wrong path. Like what kinds of stuff? Like tech choices or what?
Yeah, for instance, when I was working on an analytics thing for us, and I have all the CSV data. And it was like, for me, that's like an interesting way to work with AI. Because I personally, like taking in CSV data, like I can give it the... the CSV data structure and say, just build me like a parse and a database that fits into this structure. And we can, you know, scoop this all up with pop a parse or whatever that CSV is.
I want to use temporal for this. And it came back and said, OK, here's what we're going to do. We're going to use this temporal polyfill. And that's I know I know the temporal polyfills. There's multiple. Yeah, that's the wrong one. So I can go back and forth and be like. you're using the old polyfilm rather than like doing it after the fact and trying to have to rip it out and use like an old version or like
old version of Zod. Like, what are the other ones that happened? Tailwind 3, it always uses instead of 4. For me, it's using NPM instead of PNPM. Bro, you know what I'm using. Do you see an NPM lock file in here? You can see the PNPM. You can see it. Yeah. But I got to the point where I wasn't coding anything without a plan. Even if I was using VS Code that didn't have plan mode, I would prompt it.
to createplan.md. So now that it's integrated, that's pretty sweet, but they are like really late to the game. Really late to the game, yeah. Because Cursors had it, and then, well, I mean, Claude obviously first. And then Cursor added it. They added their to-dos, not the greatest. I've had issues with to-dos inside of Cursor. Like, it forgets that the to-dos are even there. Oh, Cursor has to-dos too? Yeah. Okay. Yeah, I feel like Kira's the only one who's figured it out.
to do's but it's it's like a whole ass thing that you're agreeing to it's not just to do's it's the whole spectrum and that's like that's a different box that you're opening but you are right everybody else and their grandmother had a plan mode before this yeah but that's it I do use it it's one of the things I use constantly in cloud code so yeah here's a question
¶ Cursor's new trick: firing off agents straight from Slack
Cursor rolled this out a couple months ago. Now they have is being able to fire off an agent from Slack. Yeah. I don't get it. Is that useful? Not for me. I don't give a shit about that. That to me is like the lowest totem pole for me. I don't care. Or you're talking back and forth in Slack about a feature and then just you add. co-pilot and say, go, go build this thing. I think that is useful to some people. And I think it's very useful to some people. But for me personally,
I'm never, ever going to. I'm never even going to. It seems like if you're going to fix something or do some sort of feature, there should be like a little barrier. Clicking a button? For me, it's like, yeah, yeah, if I'm going to do that type of flow, I'm going to go to a GitHub issue. Okay, that's a good place to start. Or even like a linear task, even though we don't use linear. But I would go to something like that long before I would ever go to. slack which right yeah
I completely agree. I think like, yeah, so you go where the work is happening. So in GitHub or in your planning tool or Kanban board, because I mean, like Slack, sure, it would have the context of the conversation, but that likely needs to be a little bit more formalized before you send an agent off to start working. So I don't know. It's not useful for me. Yeah. Maybe like I can imagine like something were to roll in in one of your slacks, you know, you're monitoring something. Yeah. Yeah.
And it's auto. I just don't use Slack like that. I use GitHub for a lot of that. And Sentry. I use Sentry at Sentry.io. Coupon code DaisyTree for two months for free. Yes, that comes in. And seriously, I mean, it does, though. And I get my errors in there. Clear logs? i get my logs i click the little buttons and then and it tells me how to fix my problems and i do and that to me seems more like what i what i would use that for like uh you know
where the issue is happening, where the code is. Here's another feature I'm curious, and I think a lot of people are going to hate, is they have a co-pilot metrics dashboard for...
¶ Copilot Metrics Dashboard and agent analytics
So if you have an organization and say you have a thousand developers, there's now a dashboard to see. who's using it and, or maybe who's using it or like how, how many, how they're using it. Yeah. And like, I have heard from so many people in the last three months of like, I have a,
manager that is so heavy-handed AI. I said, like, you should not be writing a line of code. Like, that far pilled. And... now isn't it weird how it's always managers who are pushing that like yeah it's not and as as as much as we love this stuff i don't think that that's the the move but i think people are curious to see like oh we're spending all of this money on
On a subscription. It's more of like a corporate enterprise feature. They want to be able to manage their spend and see how much people are using it. Yeah. I think it's interesting to have. Is it going to snitch on people not using it, though? I think it is. I'm looking at the screenshot here. It's got agent adoption. So the screenshot says 2,400 of 3,000 active users. And so I've talked to people where...
like part of their development plan and part of their promotion plan is how much AI are you using? Like they have a quota for like, they have to be using like 90% of their code pushed with AI or like... So, yes, they're definitely going to use it to call people out. CJ, I'm getting a little concerned. I've noticed that your AI usage is hovering around 5% for this month. Are you all right? I'm going to write an agent to pretend to use all my AI. It's like a mouse jiggler for you.
And I have built multiple mouse jigglers, like work.js. Fire it off, it just spins the mouse, and then, yeah, so. That is very funny. Yeah, you could just have a trash repo that is just. constantly pushing. Spinning, yeah. CJ, your AI score has improved by 95% this quarter. Yeah, I'm loving it. I'm just, so much AI. AI is so great. You could build like an MCP that just like retypes all of the code that you did by hand. He's like a
Constant feedback loop. Yeah. All right, that's going to be a thing in no time. Jiggler.js or something. Yeah, like a paid service to keep your AI usage up, for sure. Syntax, we patent that. That's ours. Don't touch it. Don't take it. Don't take it.
¶ Effortless MCP integration and custom agent workflows
You know, another thing they announced was effortless MCP integration. This is actually something that had been inside of VS Code already. So this is a VS Code feature, being able to install MCP servers from the extensions market. It's cool. One of the issues... I also had with trying to work with AI is finding decent MCP servers and like all the directory websites so many times the MCP servers listed were just like spam so if this is like
officially sanctioned, or you can see the number of downloads. They also potentially, like with VS Code extensions, there's like a publisher name. So you could be more sure that the MCP server you're installing is more legit. I like that. I think it has to happen that somebody...
needs to be able to like as much as we hate like a like a governing hand is that like if one of these mcp servers goes rogue that somebody needs to be able to pull the plug on it and like chrome does that for extensions right VS Code does a good job of that with their VS Code. In fact, I met a guy at the meetup yesterday who forked my Cobalt 2 theme and he called it Cobalt 3. And he said he got, he's like, I got like 3 million downloads. Like it got really popular.
And then he got an email the other day that they pulled it. Oh. Because they said it was too close to my theme. I didn't complain or anything like that. Well, you got f***ed. And they pulled it. And it's so funny because I was like, yeah, I kind of was cheesed when I see like people would like.
fork it and make Cobalt 2 better. Yeah. Because you can, you don't need to fork a theme to change it. You just, you put your own personal changes on top of it. But then I realized like it's called Cobalt 2 because I've, I forked Cobalt 1. Yeah.
The original one. So I can't get mad. Yeah, the original one. No. Yeah. That's allowed. So I think that that is fine. Hopefully they add integrations for more stuff. Right now it's just like... it's just VS code, but like, I want to be able to click it and it's installed in like cloud chat or obviously cursor, but I don't know if they'll ever.
Yeah, you know what? MCP servers were one of those things that I felt like a little bit of, okay, now I got to install it these ways or do all this stuff. And for some, you just get used to it and then it's fine. So I don't know. I used to want a UI for this, and now I maybe don't care as much. I would love if they were to add my CSS MCP to this because that's a, yeah. No, I think discoverability is a...
Oh, it's a discoverability. Yeah, absolutely. I'm talking more about like the install management process. The Century MCP server in here, top tier MCP server right there. Yeah. Century mentioned on stage a couple of times. That was pretty sick. Yeah, this entry stuff was up right front with all of it, which is really cool to see. Yeah, it's so funny working for a company now and feeling pride in that. Man, yeah. That's my boy!
Hell yeah! Yeah. Like three years ago, I would have been like, oh, okay, cool. That's my seer. Yeah. Fixing the bugs. Yeah. So, all in all, announcements, you know, I feel like these are all good things. They're all... I didn't feel personally, like, blown away by anything. But I do appreciate everything they added. I would say that. I think we're past the place in AI now where there's, like, this...
like jaw dropping model or this amazing tool that does that. And it's, it's all just about like, how do we fit this into our workflow? How is it getting faster? The DX is really good. And then of course, like all the, the enterprise tools of like, I have 5,000 developers. How do we roll this out? so that everyone can use it efficiently. How do we make sure that they're using AI as much as we would like them to? Exactly. Yeah, so a lot of interesting stuff, but I think we...
¶ Wrapping up GitHub Universe 2025
Kind of hinted at it. It's honestly just, it feels boring. It feels like, it's like, it's nothing new. It's stuff that other people have already done. Not that innovative. So, AI skeptic take. It's fine. It's getting better. And if you're already using VS Code, great, because you have a lot more features now than we have in all these other tools. But otherwise, it's fine. That's the AI skeptic take. It's fine. And now it's time for the AI skeptic take. I'm pretty...
excited about it because as much as I love, and I'll say this as a primarily cursor user in the last probably eight months, the software dev still happens on GitHub. And I'm cheering for GitHub because I want... GitHub is an awesome place. Because you want Satya on the podcast. I will kiss no asses except for Satya. But the fact that the software dev happens on GitHub.
And these tools are going to need to be integrated into GitHub at some point. And the fact that this is happening and we're working on workflows, I think is overall good. Stoked about it. So, yeah, I would say my thoughts are somewhat... similar to both of yours, even though your thoughts were opposing. I do feel like... Right in the middle. Yeah. He's playing both sides. It's the sunny meme right now. No, exactly. No, I agree with you, Wes, and GitHub is where the stuff happens, and GitHub...
is still just always innovating, right? GitHub could have easily become Bitbucket and just like been someplace, you stash your code. And GitHub has never been that. They've always... been pushing it. Bitbucket. I wonder if they've even added labels yet. Do you remember? There was like an issue on Bitbucket for like 10 years. Like, can you add labels? Like, it could have easily turned into something like that. Yeah. Instead they've always been...
bringing new stuff. And so for me, I like you, Wes. I am rooting for it because I have such a fondness for GitHub overall and GitHub proper. I think the stuff that they are adding are things that needed to be here. There was nothing in this announcement that shot my socks across the room, but in the same regard, I'm going to use all this stuff. Yeah. So, yeah, I'm happy. Simultaneously, nothing crazy.
Happy that it's here. I hope that what GitHub did for software development over the last 15 years is also... what they do for ai development yeah i don't know if that is true now that they're a mega corporation owned by microsoft but I hope. Yeah, and it's like an institution, and they've done so much good stuff, and man, I love the improvements that GitHub brings all the time. Yeah, and they just hired...
Jared Palmer, who we've had him on the podcast in the past. He was a guy who created Formic, and then he created... Turbo Repo. And then he created V0 at Vercel, if you heard of it. And then he recently just joined Microsoft. And he's just been like, just been on Twitter being like, hey, what can we fix about GitHub? Yes.
whining about laggy diffs and like performance issues on GitHub and all of these things. And it's gotten even worse as I'm sure a lot of their eng has been pulled off to work on AI stuff. And he's like... He seems to be fixing a lot of it, and he gives a shit about performance, obviously. Yeah, yeah. No, no. I love it when a talented hire gets brought in anywhere. Shake it up.
What's the ETA between when you think GitHub's going to add the what will you build today search box on there? When will GitHub.com be a vibe coding input? tool yeah yeah yeah what will you build today no i'm stoked to give a lot of this stuff a try so uh shout out to github team for constantly shipping and uh yeah all right thanks everybody for tuning in thanks everybody who came out to the meetup Peace.