Menu

32% of This File Is Comments About Bugs That Already Happened
πŸ“°

32% of This File Is Comments About Bugs That Already Happened

DEV Community: aiΒ·Enjoy KumawatΒ·about 13 hours ago
#KQWYx6dF
#devtoai#devto#dev#comment#lines
Reading 0:00
15s threshold

"AI Code Is Unmaintainable? So Is Ours." has been doing the rounds this week, and the honest answer for my own repo isn't the one I expected. The logic in my git-manager scripts isn't the unmaintainable part. The comments are β€” not because they're wrong, but because of how much of the file they are, and because every one of them is a duplicate of something that already exists somewhere else.

I write these scripts with an AI agent across sessions that don't share memory. The pattern that emerged, without anyone deciding on it as a policy, is that whenever a bug gets fixed, the fix gets a comment that doesn't just say what the code does β€” it narrates the whole incident: what broke, how it was found, why the fix is shaped the way it is. I wanted to know how much of the actual file that is, not guess at it.

import tokenize , io

for fn in [ "publish_devto.py" , "reply_comments.py" , "server.py" , "git_commit.py" , "scripts/check_key_facts.py" ] : src = open ( fn , encoding = "utf-8" ) . read ( ) total = src .…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.