Vim

Samantha Jarosek also says that Gary helped them learn Unix and set up BSD home network, sometimes by pointing them at man pages with a condescending tone.

Now they're using Vim to write C.

Well, that's fun.

Gary's pretty

I don't know how would you, how do you, how do you call these new sets of tools that like sit between you and your, and your harness? But I used Golang before and PyCharm before that.

I used to use a lot of JetBrains tools, but actually my main IDs are just like Vim and whatever's fast and has Vim keys.

So it used to be VS Code for a while, but now it's Zed, which I've been loving as well.

But I'm the sort of person who always likes to move between tools.

Every couple of years, I'll refresh my...

Okay, I used to do Vim and now I'm on VS Code and now I'm on Cursor and now I'm on Zed.

And now I'm on Air also.

I'm trying it out, which is pretty cool.

I've since kind of changed my mind.

I feel like Zed is if NeoVim and VS Code had a baby, and this is what it produced.

That's kind of where it is now, and I want to show you my setup because it's different from anybody else's that I've seen online, and I use it a lot different.

But I want to just run down real fast what it is.

And I can kill that, add this.

I have everything hotkeyed, so I can go right to my edits, but I can also pull up different things.

So let's say I want to add or open up my NeoVim one.

I can go NeoVim, and I have directly here all my NeoVim articles I've written in the past.

And then the same example with exclamation mark colon one will give you the second word, which in this case, because you've put it in quotes, is hello world.

And then dollar sign would be the last word, which if you're a Vim user, you'd be very familiar with.

You can also do colon one dash two to get the second to third word.

And you can use star for all arguments.

You don't necessarily have to finish it within Warp.

And then it's totally changed in the past three months where some of the senior developers on our team have like gotten it and are like able to do like wield it in the same way that they could like, we're awesome at the terminal or awesome at Vim or whatever before they're now awesome at using these agents.

And so, you know, I guess the sort of interesting thing for people who are running companies is like, you might have to force it a little, um, you might have to overcome these biases.

You have to overcome this, this idea that these technologies are fixed at a point in time, because they're not like you might've tried it six months ago and it's, it did suck.

Coding agents are here, they're superhuman.

I'm not matching up curly braces and Vim manually very much anymore.

What's your guys' experience of this last year been like? And to what extent do you trust these things with everything when you still grab the keyboard and do the hard part?

It's funny you mention November.

And maybe it's just confidence, but we'll get into that.

And then on the emotional side of things, you know, it's a pleasing state, right? Like, there's things about Flow that feel meaningful, that feel kind of rewarding.

Where does that come from for the next generation of folks? And also, like, how do you get to be Jamie and JR if you're a 19-year-old now who likes computers a lot and there's basically no realistic way other than, like, some sort of radical self-discipline or something to sit there in Vim and write a million lines of code that actually work?

Yeah, I mean, I think for me, I've always been drawn to the field because of the outputs, the things that the humans are actually going to use.