• 1 Post
  • 222 Comments
Joined 3 years ago
cake
Cake day: January 29th, 2024

help-circle

  • Yeah ironically growing up this was the argument. I closed the toilet lid and my sister was outraged. She eventually went to my mother and asked her to talk to me about the toilet. So my mom brought us together and said “lengau, you need to stop leaving the toilet seat up.” I looked confused and my sister said “no, he keeps closing the lid!”

    My mother burst into laughter and told my sister that she should do so as well.





  • I maintain several small open source projects. I sometimes use AI for my own PRs, especially ones that are almost mechanical but not quite. A great use for AI is “fix the new listing issues from this litter update.”

    I’ve been getting a moderate amount of AI slop PRs recently, though it has also coincided with a similar increase in PRs that are probably written by (or an least partially written by) AI but are actually useful. The ones I’d call “AI slop” tend to be huge, change a lot of tests, and may or may not even achieve their goal. A recent AI-written PR I got from an external first-time contributor fixed a bug by refactoring some code into a function, ending up with 4 calls to that function, of which 3 of the previous implementations had been correct and one had missed a step back in 2021. Net code added? 1 line, and only because it added a test.

    The main problem is how much time I end up spending on these slop PRs. It can take a while to even describe why you’re rejecting the change, though ironically AI has made this easier too.





  • Ive done a few of those, but they were all preparatory refractors, pulling out bits of code to turn them into standalone functions that are only used once because my next PR uses them, and then adding unit tests for those new functions. -100 or so lines of code, +300 or so when you take into account the new docstrings, etc.

    (The secret to doing these preparatory refractors is to actually do them after writing the “next” PR so you’re not unnecessarily refactoring stuff you’re going to touch.)