People who previously wouldn't touch a README.md with a ten foot pole are now writing entire novels in Markdown for their AI tooling.
-
@frederic Yes. People who couldn't be arsed to write a single word of documentation for their human colleagues suddenly don't have any issue at all with writing miles and miles of instructions for their AI colleagues.
Same for people who previously couldn't find time to mentor a student or new junior colleague because "it's too much work to describe the task in enough detail". For their LLM? No problem at all.
That's the one that really gets under my skin.@mmeier @frederic I keep seeing this, and I can only imagine that like, half of it is generated anyway, and the rest is the "one more hit bro" effect of the dopamine feedback loop that generating output so rapidly causes, so they just keep adding more and more and more and then they're used to doing whatever to generate that feedback loop.
Couple with how real people don't give the same "you're absolutely right!"-style feedback and repeated exposure to doing this and it becomes their default. Unfortunately.
Welp, they keep vibe coding their shit and they'll keep ending up with music hosting servers that have a paid component but isn't shipped as a separate binary and requires a single line or 2 of code to be patched to enable for free.
-
@frederic seeing the same - as a person with a mild obsession over readme files I will say this - AI tooling is better at getting through reading of readmes than most devs I worked with.
If I had a dime for each time I've written "It's in the readme" or "This should be in the readme" in chats …
-
People who previously wouldn't touch a README.md with a ten foot pole are now writing entire novels in Markdown for their AI tooling.
@frederic@chaos.social and then there's a group of users who say they don't know markdown until you call it "discord formatting"
-
@frederic Yes. People who couldn't be arsed to write a single word of documentation for their human colleagues suddenly don't have any issue at all with writing miles and miles of instructions for their AI colleagues.
Same for people who previously couldn't find time to mentor a student or new junior colleague because "it's too much work to describe the task in enough detail". For their LLM? No problem at all.
That's the one that really gets under my skin. -
-
People who previously wouldn't touch a README.md with a ten foot pole are now writing entire novels in Markdown for their AI tooling.
@frederic i can't believe this is what it took for people to write readable high level docs
-
@frederic also, developers who never gave a shit about #accessibility now bending over backwards to make their forms/controls "AI agent friendly" ... https://mastodon.social/@patrick_h_lauke/116453512115422196
"WebMCP"... Does anyone else think https://en.wikipedia.org/wiki/Master_Control_Program_%28Tron%29 there, or is it just me?
-
People who previously wouldn't touch a README.md with a ten foot pole are now writing entire novels in Markdown for their AI tooling.
@frederic same people who refused to install a linter
-
@frederic reminds me of the "Oh no Linux is too complex you have to use the command line" crowd that at the same time dig entire forums to find the REGEDIT magic to make their games work on Windows…
-
In recent years I had seen an increasing amount of "Open powershell and paste these commands" instructions on the internet.
-
@frederic Yes. People who couldn't be arsed to write a single word of documentation for their human colleagues suddenly don't have any issue at all with writing miles and miles of instructions for their AI colleagues.
Same for people who previously couldn't find time to mentor a student or new junior colleague because "it's too much work to describe the task in enough detail". For their LLM? No problem at all.
That's the one that really gets under my skin.@mmeier @frederic Yes! I accidentally read one of those agent-files in a project, and was ALMOST impressed by how comprehensive it all was (at least there) in terms of architecture, style, and even comment tone, because that's obviously useful. And then I realized that they'd probably scream if an actual prospective contributor read it for advice...
-
People who previously wouldn't touch a README.md with a ten foot pole are now writing entire novels in Markdown for their AI tooling.
@frederic often times it is not even a good documentation or README.md for humans still.
-
People who previously wouldn't touch a README.md with a ten foot pole are now writing entire novels in Markdown for their AI tooling.
Yes, And people who celebrated the freedom of "just talking to the computer in human language" and "getting rid of formal programming languages" are now definiing specifications how a good AGENT.md or RULES.md or SKILLS.md has to be written ... to formalize the language to talk to the computers
-
-
-
@frederic Yes. People who couldn't be arsed to write a single word of documentation for their human colleagues suddenly don't have any issue at all with writing miles and miles of instructions for their AI colleagues.
Same for people who previously couldn't find time to mentor a student or new junior colleague because "it's too much work to describe the task in enough detail". For their LLM? No problem at all.
That's the one that really gets under my skin.I guess I am guilty of not writing sufficient documentation for some of the code I have written. But I have definitely taken the time to explain to new colleagues how it works. And I have also done many pair programming sessions with colleagues to improve the code. And they have now written documentation of the code for AI to read.
But the documentation they wrote actually looks good, so that can probably be helpful for new hires as well. We haven’t stopped hiring, we have hired a couple of new people this year.
-
K koefoed@helvede.net shared this topic