Honestly it feels like AI is... something like optimizing for nitpicking "best practices" while completely missing the real issues.
Nobody writes code according to all "best practices". Error handling in the example above is an anti-pattern. This isn't a kernel. Littering your code with NULL checks for memory allocation (and functions which can only fail due to memory allocation failures behind the scenes, like fdopen) is a net negative because it achieves nothing (if small mallocs are failing you code is going to crash anyway) while making the code more obtuse and complex and hard to read, which means real bugs will slip through more often.
If you're the kind of person that cares about having more "strictly correct" code... you shouldn't be using C to begin with, but rather a language where doing that doesn't hurt readability (like Rust). But AI isn't going to give you that advice...
Hoshino Lina (星乃リナ) 🩵 3D Yuri Wedding 2026!!!
npub14w…zuequ
2026-03-09 02:14:06 UTC
in reply to nevent1q…j3cf
Author Public Key
npub14w78207els8vs5fxduhhval0r9zgujpf2khcqyfuhmkt2tlyvcyq2zuequSeen on
wss://relay.ditto.pubPublished at
2026-03-09 02:14:06 UTCEvent JSON
{
"id": "e5594c76c42de52b930e22d79fb592651606cddfe92f0ce474de88ee2b158613",
"pubkey": "abbc753fd9fc0ec851266f2f7677ef19448e482955af80113cbeecb52fe46608",
"created_at": 1773022446,
"kind": 1,
"tags": [
[
"e",
"d2c877ea2c85152d01bc47baa1063f3882ee00c9ad3c97f5668c13195f8a6102",
"wss://relay.ditto.pub",
"reply"
],
[
"proxy",
"https://vt.social/users/lina/statuses/116196799052292404",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "Honestly it feels like AI is... something like optimizing for nitpicking \"best practices\" while completely missing the real issues.\n\nNobody writes code according to all \"best practices\". Error handling in the example above is an anti-pattern. This isn't a kernel. Littering your code with NULL checks for memory allocation (and functions which can only fail due to memory allocation failures behind the scenes, like fdopen) is a net negative because it achieves nothing (if small mallocs are failing you code is going to crash anyway) while making the code more obtuse and complex and hard to read, which means real bugs will slip through more often.\n\nIf you're the kind of person that cares about having more \"strictly correct\" code... you shouldn't be using C to begin with, but rather a language where doing that doesn't hurt readability (like Rust). But AI isn't going to give you that advice...",
"sig": "c7dde36c24576d723241053de5be21749a81ea0524b639eddb9a1d9b36146ea25aeb63e10b3687735bf19f69732abe31dd2b56a03712ce73fe74db43e4caf8cf"
}