Scott & Mark Learn To...Pilot Coding - Vibe Coding for Real

What about my M C P for Sys internals thing? Is that a good idea? That is a good idea. Okay. We should do that. Uh it requires more thought though. No, a hundred that's that so the the new stuff that people are talking about with Claude is like a f formality we that could be another thing, by the way. The formally vibe coding. Are you doing a formal plan mode? Like you ever put your Copilot into plan mode.

Yeah. Right. And then you do a plan, write a spec, and then by the way, for the GR you know the GRPC shared memory thing that I started last Spread the one that it was so confident it was done. Yeah. Well, summer. Um early summer. And I've had starts and stops on it. I started with GRPC C and that ended up running into uh concurrency issues that it just couldn't figure out. And I was just like, I don't have the time to go and babysit you through this.

So then I met with uh the GRPC Go maintainer and talked about the shared memory and and he was excited about Um shared memory coming in, but he's like, I'm the GRPC Go maintainer, not the G RPC core maintainer, which is the C version. But then I was thinking, why don't I just switch over to GRPC Go? And there's two reasons to switch over to it. One of them is the whole point of the only reason that I was interested in this is because of Dapr. And Dapper is written in Go.

And Go doesn't support DLLs. And also Dapper uses sidecar. Communication, which is on the same machine. And so if shared memory would do two things, allow Dapper to have loadable modules that are efficient, because you could just do GRPC in proc. And it would also allow provide more efficiency for talking to the Dapper components from the app across the sidecar.

boundary. And so I was like, let me just try Go and do GRPC Go shared memory. So I started that in the fall and I ran into about the same, got about the same distance. and ended up running into the AI couldn't figure it out, the concurrency issues that and that's very complex because you gotta do streaming and cancellation and metadata and So I stopped on working on that and changed and switched my attention to other things. Well, this weekend I'm like, let me try it again. And

So I've tried again, maybe this is a jump in Opus and Yeah, before you were doing it in Sonnet before? Yeah. But not to say that it wasn't that it didn't run into problems. And this is premature because I've not verified it independently. But I think it's done. And you have a good enough test harness that you feel like the test harness can catch the concurrency? It's running GRPC tests themselves. Um now modified to use shared memory instead of right.

And they all pass. And the example programs I can see.

that use shared memory that are equivalent of the the standard TCP examples like, you know, client server hello world and some streaming from the client to the server. Those work. I mean I can see them they appear to work, let me say. Like I need to make sure it's actually using shared memory, that there's no polling which I told it not to use. I need to go do verification. But all the tests are passing and all the examples work.

And so this would truly be a mind blowing moment if that's the case. If so, given the the complexity of the problem and given your you've taken two, you know, multiple runs at the thing. Do you think that it's worth You you and I have talked about when we've coded something and we have felt confident to not enough to not even look at the thing.

Yeah. But this feels like time for code review time. This is time for code review for sure. Something like this, because this is um something that a eventually I want to do a PR into the G RPC Go project and they're not they're gonna not tolerate crap. Yeah. Obviously. Yeah. Because if they accept it, this is gonna end up going broadly and potentially, you know, lots of companies are gonna be depending on it.

for production systems. So I need to actually look at it and review it. So that'll be the next that's the next phase that I'm on. But for zoom it, I think it's kind of good enough that I can see the code is constrained to certain parts of the project. It's not like infecting everything. And it works. You know, UQA'd it, IQ'd. So let's explain the problem again for those to who may have joined. What is uh so Zoom it we know does zooming, we know it does screenshots, it does screen recording.

You know, when you ha you find a bug, you're like, Oh man, I gotta show a recording of this bug to someone, you fire up ClipChamp, you fire up Camtasia. With Zoom it you hit control five, it starts recording immediately. And uh then you hit control five again and it pops up a save dialogue and then you go off and give it to somebody. But very likely you're gonna want to trim that. You're gonna wanna do a little bit of light editing.

So you wanted a editor trimmer to just kind of pull the bumpers off and tidy up. That's right. Yeah. And that way I mean, in so many cases it's like, you know, you're setting up, you press play and then you need to get in position and And then at the end you might, you know, stop the recording uh after you're moving things around. You don't wanna have that part in the video. So I find it very common that the beginning and the end I just wanna clip off.

And so I thought, oh, this is a great vibe coding thing. Um and one of the reasons this I thought it would be ideal for vibe coding. First of all, I was just curious, can these mo do these models know how to program Win32?

classic Windows desktop UX and C plus plus coding and look at a project that's relatively simple but still requires some integration. And then the second one was um it's self-contained. So it's a feature that even if it's poor quality or you know, not as good as my quality standards, it's still isolated to just that part of the zoom it experience.

So I thought, uh good good test case for it. And so I gave it to GitHub Copilot with at the time Sonnet four five four and it produced a working with probably ten interactions. Ten prompts, it produced a working clipper. that looked decent. Now since then that was before the holidays, since then

I've iterated'cause I'm not s you know, I've got higher s high standards for how the thing should look and ha behave. And then you came and threw at me some more things and I had uh Mario from Sys Internals look at it and he's like, Hey, you should add this and this.

And so uh, you know, in the old days it when somebody would say, Hey, you you should add a volume control to this playback, I'd think, Oh crap, uh yeah, you're probably right. And that's probably another few hours of work to go lay out the volume control and figure out how to do the volume and

So last night Mario's like, hey, you should add a volume control. I'm like, oh crap, wait, oh wait a minute. I can just ask the AI to do it. I prompted the AI this morning, and now there's a working volume control, like with one prompt. And I haven't seen this because you sent me the last one yester like late last night.

Uh like version six. Like we've done like a couple of turns on this'cause I've been giving you a hard time about some little tiny Yeah, well you use uh so I run with hundred percent DPI on this monitor and and uh you run at some one fifty. One hundred twenty five. So those are called fractional DPIs and Windows and a lot of a lot of apps f see weird behavior at these kind of like non

even number, you know, DPIs. One hundred, one fifty. They're great. But one seventy five and one twenty five is a great way to mess up somebody's UI. Yeah. And also you're like, hey, where's dark mode?'Cause I'm like, this is just an options dialogue and a one dialogue, like big deal. And then

This is the other thing though. It's th you know how we we talk about how vibe coding might make crappy code. Yeah. I'm actually finding that I'm catching and fixing more and coming up with a more polished thing because I can turn faster. Yeah. So like my stupid edge light application could have just been shipped in 10 minutes.

But the amount of time I've I would take to do it is now the same as if I had written it by myself, but it has more features and more polish because I can turn faster. Oh yeah, for sure. Well th and I'll tell you, you said add dark mode. I s I told AI, go add dark mode.

And probably, you know, it didn't get it a hundred percent right the first time, but it got it ninety percent right. And after a few more turns, I got dark mode. So a few more turns in terms of total elapsed time, it was less than a half an hour and I was doing other things while it was working. Right. So I mean, that alone would have I would I would have been like, oh crap. You know, dark moding this classic Win thirty two UX.

require subclassing all over the place. Like all over the place. And well, that's the definition of toil. Yeah. Right. And the other thing that's worth noting is that with this DPI thing, so I'm at a weird fractional DPI, but I also didn't realize that I was I didn't kind of internalize that I was opening up the display DPI changer and your dialogue at the same time, which is a different edge case. It's one thing to have the DPI ready when the dialogue pops up on WM Create.

But I was sending out a W M DPI changed while it was open and it was messing up the dialogue. Even that conversation is like a lot of people don't know that stuff'cause it's like obscure and old. That's an edge case. And then the question is as an architect, what's like, well, this is a

thing that's not even worth fixing. It's not. I'll just stick with the DPI that I get at the moment that it popped up and not listen to that message. That's the kind of steering that you can give because you could fix the bug or you could just say, works as designed.

And you have to know the uh the underlying stuff to be able to make those decisions. Well, so on the DPI one, because you said, Hey, it needs to work at DPI, that one actually took me about a day of back and forth with it to get it to support DPI changes fully because what it would do is

It needs to work on all the controls in a consistent way to resize to fit the dialogue and the text and you were like, Oh, this text is cut off. Well, you saw that after I was on iteration twenty with it of no, it still doesn't work. No, still doesn't work.

And by the way, being able to give the AI screenshots where it can see that it's not working is incredibly helpful because I didn't have to describe. I could say, look, text is cut off and give it a screenshot. And it would be like, oh, I see that the tech right side text is cut off. I need to go resize it. But one of the th here's one of the things that I ran into too.

is it would sit and go, it's fixed now. It's fixed now. It's fixed now. And I'd be like, no, it's not. No, it's not. And give it screenshots. And then I'm like, add debug output so you can see what's going on. And then it added debug output. It's like, oh, I see what's going on. Even then, it required multiple turns and adding more debug output for it to figure out how to fix it.

But without the debug output I think I would have been stuck in the it's fixed. No, it's not. It's fixed. No, I'm not it's not indefinitely. Yeah. So that just uh that's a a nudge to And I had to do this by the way with Wordlebot. I don't know if you remember that. Yeah, yeah. When it was running into a performance issue where it was loading

all of the games from the very start every time I'm like, go add debug output so you can see what's going on. And then it l added the debug output and goes, Oh, I'm loading all the games from the very start. I only need to load the new games. Okay. So you said

Having it be able to see the screenshot. That's that's cool. That's valid. That's multimodal. Some models and some tools are like they'll O C R it, but in this case it's actually looking at pixels and it's like really being a true multimodal model. But then you use the WordleBot example where it's like, well, it wants to see the console output. Letting it see Letting it C Tightens the The feedback and the seeing isn't necessarily pixels. It's just if you're using an agent and you catch yourself.

copy pasting from somewhere. You gotta stop and think to yourself, how can I let the agent see this so that the turns can be automated? And that's where things get interesting. It could be Setting up an MCP server for debug output to Windows. It could be doing regular screenshots. It could be hooking up clawed code or GitHub CLI to an MCP server like Playwright. Um, I was finding myself regularly copy pasting debug output.

from like got here debugging, you know. Mm-hmm. Got here, got here, got here with the WPF app. And I was thinking, you know, Mark should make it so I could take debug view from Sys Internals. I absolutely that is that is absolutely going to happen. Yeah. Right. So that that seeing doesn't necessarily have to be pixels. It can just be debug output. And giving the access, you know, having an MCP server for a debugger means that it can slam on that thing while you're off doing other stuff. And

That was a revelation, of course, as well that I came up with, you know, in my brain, like it not came up with. Um, it clicked for me because I was like, I think I've copied pasted like three times too many. Yeah. And and uh I mean I run into this too. There's cases like in the Wordleblot one, I couldn't get it to automate with Playwright because of the authentication issue with Yeah. Plus it's an extension rather than a web page.

So I'm I'm the one I'm, you know, the the tool for the AI, you know. It's like it's like I've I I I made the changes, they should work now, reload it. I'm like, okay, reload. Nope. You know, so Uh, the more you can have AI just do it itself, the faster things are gonna go for sure. And unfortunately there's still cases where I've got to do it myself. Um Or trust but verify. I still I mean the the I'm working on another thing, um, at the same time, which is a

Web UX for Ref checker, the academic paper reference checker, like it'll be more accessible if it's a web UI. You can just drop in the URL and it'll check the references. Well even that it's I'm telling it I'd say use playwright to and test this end to end.

And so it tests it's like everything's working great. And then I go look at it and then no, it's not. And I'm I'm not sure how it decided that things look great when it's so obviously screwed up. So this is just kind of the state we're in. It still needs a lot of babysitting and hand holding. But it's, you know, as we discussed, it's surely 10x for me. Yeah, and now and now just in the last six months we're seeing skills and um uh N S C P servers. Are you using MCP servers for like

documentation or context seven to like say I haven't really. Oh so if you're doing a UI, are you doing it in like React or TypeScript? Okay. So there are best practices skills that are like basically everyone's got together and said, Here are the things you need to pass pass to react. Or we have identified that models tend to use, you know, these instead of those or like events versus focuses or whatever as like the do's and the do not.

Huh. Are packaged up for best practices and you can um rather than you're trying to preamble it's a little bit more than that. I guess this is uh so yeah, let me good tip on that one. And I guess we're still in the phase of the tools are being built, so you've gotta keep on top of what's going on because In a few months, I'm sure that when you go into the GitHub Copilot chat and say, Build me a React UX, it'll enable the the React skill.

Automatic, that's the thing, right? The the the happy path is being yeah is being uh very much paved right now. Yeah. Yeah. I'm kind of blown away by how uh by the way, so this is the chat from this morning. So go ahead and share it again. Hold on. It's gone. Is this gonna be the opening? That's the opening right there, Rob. What the hell? All right, let me share the screen. Control Shift F five, which allows you to clip a a certain part of the screen.

Then I'm gonna move control two to move into drawing mode and start one, type R for red, two, type Y for yellow, three. And then I'm done. And then now I can save to the desktop. Escape and there's my video. And now here it goes. And you see that there was a preamble there that I might want to trim. All right. So that that's the basic trim that has always existed. Now, let's say that I want to do that, but I want to trim part of the video.

Let's go look at the trim dialogue that we've got. So control Shift up. So you can only get into the trim at the moment of save. It's basically a pre-thing before saving. I didn't want to make a video editor. Um I just wanted to make it a quick and dirty

Yeah, I think making a making uh zoom it into a video editor is kind of like turning it into the everything app. Yeah. So here's trim. Okay. Ooh. Wow. So lovely. A few things. So Mario said hey, it should be resizable. Cause they're and there it is resizable. I thought that too, but I was afraid of you. Yeah. So there it is resizable. Do you see that flash? Yeah. Well, okay. You know what? Wait, wait, I'll just ask AI to get rid of it. Uh we can do that while we're we're doing the show.

Okay. Just wanted to make it a quick and can you hear so I don't know if you can hear that. I can't hear it because it's not being re-piped around as a loop pack, but yeah, I see that. So here uh let's just say I want to start I wanna clip it to right here where I start drawing the one. Mm-hmm. and then

And now, okay, so this is worth pointing out. That's that control. How is that implemented? Because this is a big C application, big C application. Yeah. That's not a control, right? Is it owner draw? Is it like this is old style classic Win32 programming? Yep. Old style.

So it's doing mouse down messages, it's capturing that. The buttons are on or draw. This button is brand new. I told it to just uh add it right now, which is the go to beginning. It also added a go to end, even though I told it only I only told it add a go to beginning, but it added both.

Oh it's very enthusiastic. So and I can show you the prompt for that. And then here's the um the volume control. Which is brilliant. So that's the embedded volume control. You're changing the level of the resulting Yeah. Of the video playback. Wow. No, it's just for the playback. Oh, just for the playback. Okay. So and this is one this these two buttons and this volume control is one prompt. Wow. That I can show you in a here in a second. So now that you got the trim, you just say, okay.

And if you open it up again, you can go back and re-edit it. Maintain state. Mm-hmm. And then Yeah, and you had no interest in doing dark mode. I was just giving you a hard time. And you And here's dark mode on Look at that. The dialogue too. This was all people are gonna celebrate that. That made it version ten, by the way. Yeah. It wasn't the trim, it was the dark motor. Exactly. Bumped it up to ten. So, I mean, this would have taken forever. How does it feel? Like d Zoom it has really

the last maybe eighteen months really turbocharged and what it can do. So show us the prompt. So here's the prompt for that I gave it this morning. Okay. Uh-huh. By the way, can you if I zoom? Yeah, I can see that. I'm just kind of interested. I kind of thought Given what I know of you that it would be just like long and incredibly detailed spec, that's a pretty prompt. I'm lazy. And I'm like I think it can probably figure out what I'm asking for just based on this.

Yeah. So this is Opus four five. And it's like, let me look at this for the la dialogue layout. Seek to start button. Yep. Already. Here's the owner draw controls. And you can see all the classic win thirty two isn't. And you had already done dark mode, so these controls are are are th it knows that dark mode is there. Actually, that's a good idea. Let's go check'cause uh I was like, I'm not gonna add a you know, select dark mode or bright mode.

So what are we doing in here? So there's a theme. I had it add a registry key that I could override dark mode. Oh, okay. For testing. For testing, yeah. So zero. Okay. And now when we open this again, oh when we run it again. Oh so okay. On on startup. Yeah. Whoops. Wait, what happened? Hmm. Please stand by. I think we might have it we might have introduced a bug where it's not honoring the registry key anymore.

Well, there's two ways to do it. We could use the rest of the show to fix it and see how it works. Unless there's some error between the chair and the keyboard. You're sure okay, I'm trying to think about this. Why would it why would it not honor that though? Like why would it regress? All right. So I just said it looks like the registry value overwriting dark system dark mode is broken. Investigate and fix. Let's see what it says. Mm-hmm.

Hit control plus a couple times, give us a little font. YOLO mode. I I mean there's no way to operate other than YOLO. Yeah. Otherwise you're baby you're like, yes, yes, yes, yes, yes. But it makes me feel productive. Now I understand the issue. Yeah, but you know what? Do you really do you really it has no idea It says that a lot of times. You're absolutely right. Yeah. By the way, um I was looking at output. So you can put you can use auto mode for like um co pilot agent.

Oh or GoPilot Chat. And I always it a dead a tell for if it's using an anthropic model is what it's now production ready. Yeah. With the little rocket ship. Yeah. Okay, let's see if it's true here,'cause this is where You know, I feel like you're working with an intern. Now I see the issue more clearly. It's always confirming, it's like patting itself on the back.

There's no call to refresh. I often see this where it's like, oh, I gotta understand the issue. Then it's like, no, wait. No, I don't. Actually, look. Now I do. Let me understand the actual issue. Yeah. Yeah. Well this is thinking models, right? This looks correct. The issue is now understanding the bug. Registry keys are loaded. But you know what? It had fixed this bug a few days ago. So I don't know how this crept back in.

Well, so sometimes th right now you told it to fix the bug, which gets gets into whack a mole, you know, p chasing stuff. Sometimes I'll tell it to go and do a get bisect and go and look at what it was before. I did too th I did. Yeah. Yeah. Right. Have you started using work trees? No, I no, I haven't. Uh that I see that a lot of people are talking about it all of a sudden. Yeah, yeah, yeah. We should do a whole thing on work trees. What is it?

So you know how switching, when you when you switch branches, you have to usually stash, switch the branch and then decide what to do with your strat your stash. A work tree is another folder on a totally different branch, but it knows Git knows that it's connected back to the the main. So you can have work trees spread all over your disk like junction points. They're not actual file junction modes. But in the database, uh the Git database, it knows that you're in those work trees.

So if you want to get three, four agents working on three or four different problems at the same time, for example, you could have three different things that are unrelated in totally different parts of the Zoom it source. open up three different versions of zoom in in three different folders and have three different agents running on it and then merge at the end. So you're on different branches in totally different separate physical locations.

That is cool. That is the unlock. That is the unlock. If not just for not having to deal with that stash crap. Yep. Because I always forget what I've stashed. Um Yep. Totally. Yeah, and there's an application there's a little command line app called Work Trunk that's like takes the five or six commands you need to run and then makes it as easy as switching uh switching branches. It's just like WT

And then the name of the bug. So I'll go and take two or three PRs, have them running all simultaneously. Ah, look. So it's figured it it's figured it out like ten times now, but I think this might be it. Apply dark mode only as well. Oh yeah, that that makes sense. But wonder how I wonder how the problem is though, it's like you can get it to fix it, but you still don't understand why it regressed. Well, actually now it's decided that that's not the problem. I feel like it might be in a loop.

Well let's let it go. Anyway, um I've got I've been collecting examples here. Um and some of them I've shared in presentations that people have seen. Of AI doing ridiculous things. Um and I've got a bunch of projects here. Like here's the WordleBot. Mm-hmm. It says everything works and the project doesn't build. This is after I used uh spec kit, by the way.

And it's like going through and saying, I'm I've done with all the tasks and some of the tasks aren't even done. This is worth noting here though, like y y you're keeping notes. You know, I know you've always had a very d extensive one note. Um do you just see a moment and that like this is significant? I'm gonna save this moment so that I can keep track of it later.

Yep. Like here oh speaking of the DPI problems, here's a example of it's fixed. Look, if you can Yep. So I made it work. And I'm like, nope. By the way, do you uh that the gentleman uh Kuta or Kuda that we we we talked about, he has is working on a um a one note tool to be able to extract markdown from your one note.

You have such an extensive OneNote thing. He wanted to be able to grab all of OneNote and then go and ex expand it and turn it into M Markdown files. Yeah. Um so uh he's working on that and he's gonna have a tool to be able to do that. Oh root cause. Root cause in WM user reload system the message handler when I was missing a call to refresh dark one state.

Okay. Uh I don't think that's it because I th I think that don't think so. I think that's saying for dynamic changing, uh Well the the the obvious thing is that there's a there's a zoom it lying around somewhere, but it doesn't make any sense because you're in debug mode and it should have

There it is. Okay. Yep. There it is. Fixed it. That was it. Okay, do me a favor. Well, this is the thing though. You didn't check in the commit, so I wanted to do a diff. Can we see what it actually changed? Yeah. I feel like a hundred and fifty eight lines is excessive. Yeah. Yeah, see that choose font hook proc is probably not related, yeah? I don't know what it's doing there. That's a pretty big change. The init dialogue makes sense though. The WM init dialogue would have existed before.

So this is putting on the hook. Oh this is Oh no, this is the entire change. This is older changes because I had it theme the font dialogue. Right. This is the session coin wipe. Yeah. This is stuff that I'd done before. Uh so when do you decide to commit? I I commit often and then squash later. I thought I'd committed this already. Uh that's why we can't tell the difference. Actually, no, I did commit it.

It's the keep isn't synced with commit is the problem. Yeah, that's true. I find that a little frustrating. Yeah. I mean I really wish if you said commit it would keep. It's kind of like two source controls. Yep. So that's what's going on here. So that's just That's old. Old, old, old. So that actually if I could do a git diff, why don't I do that? Oh that was are you y oh you don't think I don't think you have this folder open? Yeah. Actually I could look at in here.

uh the get menu at the top. Or there. So it's in s uh so it's not I don't know how to look at the sub module here because that's where the channel is. Because you're editing it in PowerTorch now. In VS Code it'll show you the submodules. If you go to Git at the top between view and project. Open and command prompt. I know what I mean. Yeah. Here. Sorry. Yeah, you're in module world now. Yeah. Oh here we go. It's the volume changes. Right. That's volume. Volume. Volume level.

There. There yeah. And then refresh. In the main window proc. Okay. Wonder how it was before. How did it ever work? I don't know. Good question. But that's it. One line. Yeah. But it took a while for it to figure that out. Yeah, that was weird. But let's look at dark mode for um the clipper to make sure. Well first or light mode. So this looks all good. Oh, you want to see a DPI change? Sure, let's do it.

Okay, we'll go to one fifty just to see how capable it is. And here's the options dialogue. Oh too big to even fit. Uhhuh. On this resolution. Yeah, if you go to um go to two hundred, that's too much. One fifty or one seventy five is fractional. Yeah. This is one twenty five. And it looks right.

Yeah. Something cut off. This is okay. This is happens. Yeah. Close it and open this is the thing that I was saying is that you chose to not do this. No, I think it's gonna be very rare that someone has it open. No, that this is this is a new issue. No it's this particular panel. Oh, it's that one page. It's because of these headers. These are headers that I I have that are bolded and it is a good bug. So show the other ones. They're fine. Yeah, that's cut off too. All right, so I got more

Scandalous. DPIs, man. It's painful. Let's take a look at this. Fractional DPIs. 125 is the bug finder. Little bug. Yeah, those are cut off at the bottom. Yeah. And then these are not your buttons are dark dark buttons. Yeah. All right. So we found some bugs. Good. So this that's made this uh recording worth it. But that's how I'm glad that the time spent with me was not wasted.

Yeah, but I've got I like some of the cases where it's just some funny ones. And you came up with some funny ones. So how about this one? Um It tells itself good catch, which I thought was kind of humorous. Patting itself. Yeah, the the the self congratulatory sycophancy is is stressful. Yeah, this is blaming a test. Yeah. I love it when it gives itself not just a pat on the back, yeah, but an entire table of pats on the back.

Well, this is saying stuff has passed, but then it's like It's conclusively proved the the issue is not mine. Basically that's what it's saying here. Even though it is Really? Yeah. Yeah. Not my fault. And here's a checkbox that explains why. And I've got You gotta the the human judgment, it cannot be overstated how important this is. Yeah. I mean but you can see I've just examples all over the place. It's still an un it's still an unlock though. It really is

Um I'm I'm having fun, but we can't overstate. The issue wasn't a hang. It was working too well. This is this is the interviews. Uh you know when you go and you do have a job interview and they say, What's your weakness, Mark Rasinovich? I care too much. I create too many processes. Yes. I'm too good. Yeah. too empathetic

All right. Well that Zoom it stuff was amazing. Um, people are gonna be able to get that soon. Are you gonna release that right right away? Uh it probably before the show is out. Cool. So hopefully Zoom it ten point oh is out. You can check that out. Does sis internals dot com still redirect where people want to go? Yep.

Or you can do winget install sys internals or wing get update sys internals. Or go to the Microsoft store and get it. Oh, I apologize. You don't do wing get sys internals anymore because it's in Power Toys. Which means if you get five versions, you can zoom for free. Or you can get the standalone version in Sys Internals through the Microsoft App Store or Winget or

So many places. Or you can get it through WebDav and just launch it right off the website. Yeah, there's like three people who do that. They're m my people. More than three? They're my people. to have people. in this episode of Mark and Scott, like and subscribe, smash. Mr. Beast about the show. going without the comics there is no show fair