[seattle_spring]

Can you elaborate on some scenarios you are describing? The only organization I can imagine that can't do code reviews would be organizations of 1. I don't even see how performing code reviews could ever be a net negative in terms of money nor overall productivity.

[ben_w]

Not OP, but I've been in a few organisations with many devs but also where I was the only iOS dev — the other devs being Android, back-end, or web.

I would have preferred to have someone to collaborate with at each of those places.

[sensanaty]

Even if you're not working in the same language/framework/whatever, you can still do code reviews. You might not know all the syntax and high-level details, but even just an overview of the logic happening in the code is already better than 0 review of any kind

[sensanaty]

Even if you're not working in the same language/framework/whatever, you can still do code reviews. You might not know all the syntax and high-level details, but even just an overview of the logic happening in the code is already better than 0 review of any kind

[oytis]

I think it should be possible (and encouraged) for an Android developer to know enough about ios to do review and vice versa.

[JTyQZSnP3cQGa8B]

Or pair-programming reviews. It doesn't matter if you don't know a language, it's still very useful.