Boris

I would keep a spreadsheet of all the issues that came up.

And whenever the same kind of issue came up again, I would just like tally it up in the spreadsheet.

And whenever something hit, I think like five or 10 tallies or something, I would write a lint roll.

And what that is, is it's a way to automate that part of the code review so I don't have to comment about it again.

And that was back in the days before LLMs and before the model was any good at coding.

And so this is the equivalent nowadays.

You just tag Cloud and you have it update your CloudMD, which is your team's knowledge base.

So really simple.

And what this means is you don't have to point anything out twice.

I'm curious to see what this looks like for cowork.

I don't think we figured that out yet, but definitely for Cloud Code, CloudMD is kind of the, this is the one thing that you should all be updating all the time.

Yeah, like I said, planning is just the most underused feature in Cloud Code.

Actually, a lot of people use it, but I would say it's still underused.

I use it for almost all my sessions.

Yeah, let's do maybe number 13.

Yeah, number 13.

I think this is probably in addition to using Opus.

When people ask about how to get better performance out of quad code, there's three things that I recommend almost every time.

Number one is use Opus 4.5 with thinking always.

Don't try to use a different model because Opus will just give you better results and more efficiency overall.