GreenJacketBoy

15 dagen geledendiscuss

I may be the only one feeling this way, but the repetitive mention of Claude – worded as if it was a coworker ("we", "me and my friend") to the point that somebody reading it just 3 years ago would reasonably assume this "Claude" was in fact a human – made it hard to read. How much am I reading a behind the scenes of the "making of" of the application VS an essay on what somebody else (Claude) did ? I don't know. The reason I browse this website is to see what other humans are saying, inventing, using. But in some cases like this one, I see the line between tool and co-author being blurred for LLMs. And unless what they did is a specifically impressive thing on its own, I do not want to know what an LLM did. (Don't get me wrong, I would much rather have this than people lying, but I would also much rather people treat LLMs as tools.)

GreenJacketBoy

2 maanden geledendiscuss

The problem I have with this shift is that you basically give up on writing documentation by hand, not only for you, but for everybody who might want to edit your documentation.

I'm also not convinced that it solves meaningful problems :

> I've found I tend to not actually read more than a 100-line markdown file, and I certainly am not able to get anyone else in my organization to read it. But HTML documents are much easier to read, In my experience, LLMs are not concise when it comes to documentation, so using an easier file format to read because the text is too large sounds to me like solving the wrong problem

> Markdown files are fairly hard to share since most browsers do not render them natively well. Yes, but developers tools (IDE, Git forge) do. What most/some of them don't render natively IS HTML.

GreenJacketBoy

4 maanden geledendiscuss

"fully autonomous weapons" from a private company; "Department of War". Hard to believe I'm not reading science fiction.

GreenJacketBoy

7 maanden geledendiscuss

[dead]

comments