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.
-
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.
-
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. -
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 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
-
@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 That's curious, because that aspect doesn't seem to bug me.
I'm the person who writes documentation of techniques I've derived and shares them with colleagues - none of whom ever seem to return the favour.
However, they will happily video chat about or screen-share what they've done, so it's not the sharing part that puts them off.
My guess is that commitment into stored text scares them, plus the risk of it being critiqued - and they know the LLM won't do that.
-
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 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 …
-
R relay@relay.publicsquare.global shared this topic
-
@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 @Binder it's a bitter pill. I think a significant difference is that random strangers being helped by documentation and mentoring are not as emotionally satisfying as helping machines that are engineered to be directly grateful and endlessly complimentary. Which I believe is an intentional, manipulative choice by LLM service providers to encourage loyalty beyond reason.
-
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 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…
-
System shared this topic
-
@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. -
@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 …
-
