Code reviews are not only about raising quality, but mainly about communicating changes to the wider team. Suggesting to eliminate code reviews when LLM use is so rampant is also quite uhm courageous.
Asking questions on code reviews is one of the most powerful tools to learn more about a codebase, and fostering a culture where junior devs feel empowered to ask questions is one of the best ways to help junior devs succeed.
Hard no buddy. Junior dev means junior code and junior judgement. Countless times we had prod issues because some dev thought the change was harmless and they didn't need review.
No, it is an article that includes a short in-article ad for Linear. It's the text equivalent of when a YouTube video thanks some company for sponsoring the video and spends 30 seconds saying some good things about them before resuming whatever the video is about.
This is good. This is the kind of advertising that people here usually say that sites should be using if they need ads.
> Switching to another tool felt like a huge project that was just not worth it. Linear took that to heart, and made switching super simple with a 2-way sync, keeping your legacy tool updated. I haven’t met an engineer who tried Linear and didn’t like it. Teams that switch to Linear see 2x more reported issues - engineers actually want to use the tool. More visibility => fewer meetings => happer engineers.
Yeah that's very clearly an ad. They didn't even try to be subtle lol.
Sometimes code reviews and approvals are required due to various conpliance regimes that dictate it as part of the Software Developement Lifecycle (SDLC).
Code reviews are not only about raising quality, but mainly about communicating changes to the wider team. Suggesting to eliminate code reviews when LLM use is so rampant is also quite uhm courageous.
Communicating changes and communicating learning too! Every few years I rewatch one of my favorite videos on code reviews: https://www.youtube.com/watch?v=PJjmw9TRB7s.
Asking questions on code reviews is one of the most powerful tools to learn more about a codebase, and fostering a culture where junior devs feel empowered to ask questions is one of the best ways to help junior devs succeed.
The author never suggested to eliminate code reviews entirely. Just to give individuals more autonomy, which is great in my book.
Hard no buddy. Junior dev means junior code and junior judgement. Countless times we had prod issues because some dev thought the change was harmless and they didn't need review.
Linear Ad
No, it is an article that includes a short in-article ad for Linear. It's the text equivalent of when a YouTube video thanks some company for sponsoring the video and spends 30 seconds saying some good things about them before resuming whatever the video is about.
This is good. This is the kind of advertising that people here usually say that sites should be using if they need ads.
Exactly what I thought and why I checked the comments , an lo and behold it's not just me..
> Switching to another tool felt like a huge project that was just not worth it. Linear took that to heart, and made switching super simple with a 2-way sync, keeping your legacy tool updated. I haven’t met an engineer who tried Linear and didn’t like it. Teams that switch to Linear see 2x more reported issues - engineers actually want to use the tool. More visibility => fewer meetings => happer engineers.
Yeah that's very clearly an ad. They didn't even try to be subtle lol.
Sometimes code reviews and approvals are required due to various conpliance regimes that dictate it as part of the Software Developement Lifecycle (SDLC).