Brian Maucere

And I believe when I use co-work and I give it a task that requires cloud code, co-work uses cloud code, even though it may not make me go over to the tab.

Right.

It still uses bash commands in the terminal.

So I'm eager to confess.

I have a confession to make, which is I use terminal, but I don't understand the syntax of the language like an engineer would working in terminal.

I take advantage of the fact that Claude codes 512,000 lines of code, letting me speak to Claude

in terminal with natural language.

I do not write any bash commands.

I say, give me the command to do this.

So there's a translation layer that's available to everyone that makes using terminal not scary at all because you're talking in the same way you would to a chatbot.

And then Cloud Code answers in terminal, in text, and will also give you a little thing that's copyable that you can then plug back into terminal that will run the command, right?

So that's the way I do that.

And the same is true with Markdown.

If you sat me in front of a line editor and said, write this in Markdown, I'd go, what?

I have no idea how to write Markdown, but I know how to download Markdown files given me by Claude, right?

And I can use those.

I can plug those in anywhere.

And I generally favor Markdown as a format now for saving files, which I wouldn't have done before.

I probably would have used Word or something, right?

Anyway, it's clear that there's not a need for anybody to get to very high levels of proficiency in using CLI, command line interface, because every one of the CLI applications out there now lets you speak to it as a normie user.