It's time to stop doing code reviews

(blog.brokk.ai)

4 points | by jbellis 2 hours ago

5 comments

  • sagabai 2 hours ago
    I wonder what's going to happen after applying no-review practice, when nobody knows what code-base actually does, in enough details to provide technical guidance?
    • budman1 1 hour ago
      Consultants will make a mint dealing with these systems. It will make Y2K look like a nothing-burger.
  • thomasdziedzic 1 hour ago
    > If I were looking for work as an IC, I would avoid orgs that still practice this as a kind of make-work nearly as offensive as gratuitous meetings.

    Would you get on a plane knowing its systems weren't code reviewed by humans?

    • budman1 1 hour ago
      No. Not only that, I would not get on a plane where a defined and followed process was not used in the development of the software.

      Code review is one step of many.

  • mmcdermott 1 hour ago
    > Technical debt is nearly a nothingburger now. If you went in the wrong direction, just... change the code to go in the right direction.

    Uncharitable though it may sound, what I hear reading this is "Tell me you've never worked on a large system without telling me you've never worked on a large system."

  • jbellis 2 hours ago
    Because there are better ways now to solve the problems that code review exists to solve.
  • esafak 1 hour ago
    How are you going to know the AI did not build the wrong thing? Not entirely wrong, but they will make some bad decision without consulting you. Even with a spec, AIs find a way to do it. (Humans can do this too.)