#literatedevelopment — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #literatedevelopment, aggregated by home.social.
-
… #LiterateDevelopment vs #VibeCoding. FIGHT!
Also, people have *always* vibe coded!
You don't have to be around long to find code that makes you wonder … until you realize the author just didn't care.
Vibe coding is the engine driving so many startups toward their exit. If the goal is to exit, not maintain, it just has to "work" until the ink on the sale dries.
Slop code has always been. #AI has merely lowered the bar for its creation.
These people are not writing literature.
-
… #LiterateDevelopment vs #VibeCoding. FIGHT!
Also, people have *always* vibe coded!
You don't have to be around long to find code that makes you wonder … until you realize the author just didn't care.
Vibe coding is the engine driving so many startups toward their exit. If the goal is to exit, not maintain, it just has to "work" until the ink on the sale dries.
Slop code has always been. #AI has merely lowered the bar for its creation.
These people are not writing literature.
-
Actually, I want to pit #LiterateDevelopment against #VibeCoding directly.
Clean code has *always* been literate. That means a dev with the skills to maintain the code base should be able to read the code. The *only* valid argument against documentation has been that the code is self-documenting. Okay, maybe with a high level language and enough care, the docs can be fairly spare. I would still argue for documentation, but I have lost some of those arguments.
… -
Actually, I want to pit #LiterateDevelopment against #VibeCoding directly.
Clean code has *always* been literate. That means a dev with the skills to maintain the code base should be able to read the code. The *only* valid argument against documentation has been that the code is self-documenting. Okay, maybe with a high level language and enough care, the docs can be fairly spare. I would still argue for documentation, but I have lost some of those arguments.
… -
Whether you agree with, hate, or are turbulently navigating the transition of many teams to agent-mediated coding (I am considering the post from @anildash where he talks about #codeless, IE #LiterateProgramming or #LiterateDevelopment), Robert C Martin's book, Clean Code should be the bible in these times.
-
Whether you agree with, hate, or are turbulently navigating the transition of many teams to agent-mediated coding (I am considering the post from @anildash where he talks about #codeless, IE #LiterateProgramming or #LiterateDevelopment), Robert C Martin's book, Clean Code should be the bible in these times.
-
@anildash I do have a better term than #codeless!
I mean Donald Knuth does: #LiterateProgramming.
AI is new, but everything about what the developer does is, well, let's call it #LiterateDevelopment, just a slight shift into this millennium, reflecting that it really becomes enough to develop a system, still obviously referencing Knuth.
I think the word "literate" emphasizes the care and responsibility a dev should take not to produce slop. -
@anildash I do have a better term than #codeless!
I mean Donald Knuth does: #LiterateProgramming.
AI is new, but everything about what the developer does is, well, let's call it #LiterateDevelopment, just a slight shift into this millennium, reflecting that it really becomes enough to develop a system, still obviously referencing Knuth.
I think the word "literate" emphasizes the care and responsibility a dev should take not to produce slop.