Code review

My argument is this.

Code review does a bunch of things.

Code review is not supposed to be the gate where you find, is this code bad or good? That's not what code review is for.

But it is part of one of the, like, where else would you find that this code is bad or this code is not good? Oh,

sorry.

It's not just for, well, I didn't say it's not for that, right? But that's not the primary reason for what Code Review is for.

Okay.

Code Review is, I think the biggest thing that Code Review does for me is aligning people about what it is that the systems that they oversee does.

And we were really looking at the practices that all the engineers had.

Part of that was code reviews.

We owned a code review tool.

We were looking, how are they doing code reviews and running studies also on understanding not only what they are doing, but also is that effective? Should they change something and educating and training them? When we met around 2018, I left Microsoft.

I left Microsoft in 2019, but in 2018, I already wrapped up a little bit to start my own consultancy and a research company.

In 2019, I actually left Microsoft and started doing workshops on code reviews.

and working with people on their engineering practices, on their productivity, developer productivity.

I was then also head of research at DX.