3 ms·

Time for my next round of Evals then. I had a 40 PR coding streak last weekend with mostly o3-mini-pro, will test the latest 2.5 now.

• chasd00 2y ago
  PR = pull request? So every bit of garbage from the LLM, over and over, resulted in an individual pull request? Why not just do one when your branch is finally right?
  • Philpax 2y ago
    Presumably because they were discrete changes (i.e. new features), and it didn't make sense to group them together.
    • egeozcan 2y ago
      Or it could be just microservices. One larger feature affecting 100 repositories.
  • fragmede 2y ago
    Why would you assume that?
  • fuzzy_biscuit 2y ago
    I would assume they don't like that style, like if they needed to see a specific diff and make changes or remove a commit outright.
  • ramraj07 2y ago
    A pull request in my workplace is an actual feature/enhancement/bug-fix. That many PRs means I shipped that many features or enhancements. I suppose you don't know what a PR is because you likely still work in an environment without modern version control, probably just now migrating your rants from vim vs emacs to crapping on vibe coding. In my experience, AI today is an intelligence multiplier. A lot of folks just need to look back at the zero they keep multiplying and getting zero back to understand why they don't get the hype.