How would I know, CodeFlow is internal to Microsoft. As far as I can tell from public sources, it's trying to solve some of the same problems (keeping track of structured, possibly multi-party and multi-round conversations over revisions), but it's a Windows app, and Critique is really Google's V2 or even V3 of this kind of thing that runs in the browser and is deeply integrated with the rest of their engineering infrastructure. I hope it eventually makes it into Google Cloud, it really is that good.

> How would I know, CodeFlow is internal to Microsoft.

Lots of people have worked for both Google and Microsoft. The article said CodeFlow was good. You said no, Critique is better! But I guess you don’t actually know one way or the other.

Which is too bad. Because it’d be great to hear thoughts from people who’ve tried both.

I have worked for both and prefer CodeFlow, my more detailed comment is above.

I see this arrogance inside Google lots.

The way we do things is the right way because that's what we do. Any disagreement is ignorance.

>> You said no, Critique is better!

Nope, I did not. I just said that people really want Critique, which they do. Even CodeFlow itself is evidence of that.

Maybe what I really want is CodeFlow. Maybe Critique is evidence that I need CodeFlow in my life! It could be that you want CodeFlow in your life, you just don't know it yet.

Seeing that I haven't willingly used Windows in the last decade and wrote zero code for it, I highly doubt it. I would, however, pay for Critique+Blaze+Forge if Google offered it on Google Cloud. It's an incredible force multiplier.