9 comments

  • dap32 minutes ago
    If your plan is to not review and just have the LLM rewrite if it doesn’t work, it doesn’t sound like the rewrite is gonna be any better.
  • eschneider1 hour ago
    Failures in production remain expensive.
  • dmitrig011 hour ago
    Writing blog posts has become cheap, making them sound human has become hard.
    • netsharc56 minutes ago
      The simple sentences LLM keep generating break my brain, it&#x27;s like 95% of writing is now 3rd grade level.<p>Compare that to e.g. Martin Amis: <a href="https:&#x2F;&#x2F;en.wikiquote.org&#x2F;wiki&#x2F;Martin_Amis" rel="nofollow">https:&#x2F;&#x2F;en.wikiquote.org&#x2F;wiki&#x2F;Martin_Amis</a>
      • defen8 minutes ago
        Martin Amis level prose is neither possible nor desirable for a technical blog post.
  • m46358 minutes ago
    ai can do some of the reviewing, checking calling and called arguments, even things like crufty shell scripts.<p>but the higher-level &quot;should you do this?&quot; or &quot;check your design&quot; - could AI do that stuff?
    • ares62348 minutes ago
      I think the question is now &quot;should you care?&quot; And it seems the magnificent, incorruptible thought leaders of our time are all converging on &quot;No&quot;
  • hluska1 hour ago
    I’m not sure I agree with this or maybe I don’t understand. In my experience, the over engineered code LLMs create have more big problems. Rewriting vast parts of code when I have an outage or need a new feature means the code evolves far faster than my understanding. That gets more and more dangerous. Or maybe I’m not smart enough to follow the new pace?
    • bryanlarsen7 minutes ago
      AFAICT, the author is talking about rewriting code during a review as part of the review process.<p>quote: &quot;If I identify code that’s more complex than it needs to be, in my own work or in someone else’s PR&quot;<p>If so, that makes a lot of sense to me. The best time to rewrite code is before it hits production.
    • joshka50 minutes ago
      [flagged]
  • nryoo18 minutes ago
    [dead]
  • simianwords1 hour ago
    Why is reviewing hard? I use LLMs for reviewing. It is dogmatic to review every line written by an LLM.
    • bryanlarsen56 minutes ago
      LLM&#x27;s are good at some types of reviews and awful at others. They generally tend to overcomplicate things and miss opportunities to simplify. They pretty much have to take pre-existing code and tests as gospel and cannot distinguish which is buggy, incomplete, unimportant or important. They have no knowledge of unwritten business requirements, customer preferences, et cetera so high level review is always necessary.
    • CBLT1 hour ago
      I also like having long, pointed conversations with LLMs as I review code. Then when I&#x27;m done, it&#x27;s different code, and it has all of my blind spots and knowledge gaps, so I cannot effectively review it anymore.<p>It&#x27;s like turning a code review that requests you, into a code review that requests someone else. And it tramples on the original author quite a bit too. It&#x27;s hard only having the ability to add incremental value to large amounts of code, instead of large amounts of value to incremental code.
    • g-b-r4 minutes ago
      always true to your name
    • happytoexplain1 hour ago
      I&#x27;m confused - are you purposefully pretending that the author isn&#x27;t talking about human review?
    • gravypod1 hour ago
      What kind of systems do you work on? Does it have production traffic? Is there a cost to downtime?
    • cyanydeez1 hour ago
      you arnt reviewing. youre playing loophole semantics.