Boris

And so usually my workflow is I'll kick off, you know, like a few different tasks in parallel and I'll just kind of like go back and forth between them and kind of tend to my quads, make sure they're in a good place, see if they have any questions or anything like that.

So it's really a different kind of workflow.

Like I feel like now is the age of like kind of multi-clotting of parallelism of like not going super deep on stuff, but kind of being more of a generalist and more tending to your clods.

And so this was this other chat that we kicked off earlier.

And in this case, it sort of did some research.

So that's pretty cool.

So it didn't just go to, you know, like Startup Ideas podcast website, but it searched the internet, checked a bunch of different places, checked like someone's notes about it.

Yeah, 10 rules for quad code.

Yeah, I'll find that interesting too.

And let's see.

So it seems like this is the email is probably all drafted.

The draft has been saved.

Please send.

And I also use this for like Slack too.

Like a pretty common use case I've been doing maybe a couple of times a week is I have a spreadsheet where we track all the team's work for the month or for the week or whatever.

And instead of having to bug everyone on the team to fill out the status, what I do is I ask a work to look at the spreadsheet, any column that's not filled out, just message the engineer on Slack.

And it does that really well.

So, you know, I just ask it to do that and then I go get a coffee and I don't have to do that anymore.

Yeah, I mean, I think it's like probably two kinds of users.

And it's also, it's funny, cloud code is built originally in a terminal.