Vim

Yeah, that's one script I made.

Smithers lets you build these multi-step workflows really fast, so it can be addicting in the negative way, in the like, I spend all my time configuring my Vim config, but I don't actually get any work done type of way, you know what I mean? It's very easy to fall in that trap of like, hey, I keep building these Smithers scripts, maybe I should make a Smithers script that builds Smithers scripts for me.

Amazing.

When you were talking about the forking of TypeScript earlier, I was thinking about the singularity.

I learned a ton off of Nithin, specifically when it comes to...

Really being a good craftsperson in working with, he was the one that introduced me to using a Linux laptop, using a split keyboard, being able to program your own keyboard, Doom Emacs, a mashup of Vim and Emacs, KaleScale, a ton of technologies that I saw him taking and sharing and elevating his craft.

I definitely got a lot of insight and had a lot of his technological worldview rubbed off on me in that time that we worked together.

And it's definitely continued to affect the way I approach, the way I work with technology, the way I think about picking up and using new tools to build bigger things.

And I just remember being like, what is this screen? What is this? And he's writing CD, LS, and it's just this most intimidating thing in the world.

And so then the next time I touch the terminal, I'm in college because my CS class is like, you must use Vim and you must learn Vim.

And, and I just like have this memory of being like, what is this like archaic tool that people use? Why do people use this archaic tool? Like, why don't we just have like VS code? You know, like why did we need the terminal? And then obviously as I became like, I went more into like software engineering and deeper into engineering, I understood it.

But I totally understand that like when you're building a product like that, it is, it is a really, it is a really intimidating tool in the first place because and you have to deeply understand how the thing works how current developers use it but then also like how do you introduce new developers into it and so just people who can speak speak that language and have also this like presence or marketing presence it's just like such a niche intersection of skills

I think there's – as developers, like we've gone through – A little bit of change, right? We have to adapt.

I'm a Vim user.

I was a Vim user for a really long time.

I still am.

And I really like the idea of Tmux and Vim.

And then I really disliked Cursor because I didn't want to feel like I was going back to VS Code.

And so when Cloud Code came out, I was like, OK, this is amazing, right? And so the problem that we hit immediately when we started our company was that we were writing so much code, and it's so annoying to manage 15 different cloud code sessions in Tmux.

And this is just also a commentary on what we really need to focus on engineers.

really do.

No, and that's, I mean, you know, there is something to be said too, like with like Helix Editor, it's like, or like a Vim.

I know, you know, You know, you just install your .file, you know?

Yeah, it's a little hard to argue against a Vim hero.

You're like, yeah, you're probably right, but I just don't like how it looks, so sorry, you know? Well, I

just, I feel like I'm going to put a hand on a mouse at some point, you know, but...