|
| ▲ | xboxnolifes an hour ago | parent | next [-] |
| > Generally speaking people don't use a service/library for the author's ability to write excellent proses. I think this is incredibly wrong. I'd even go as far to say that a well presented README/website is the second most important factor, only behind network effect. |
|
| ▲ | benrbray 7 hours ago | parent | prev | next [-] |
| Presentation matters. Good documentation is evidence of a library that has been carefully thought through. Slop in the readme suggests slop in the code. |
| |
| ▲ | raincole 2 hours ago | parent | next [-] | | I've seen developers who genuinely like to write code, but never met one who likes to write documents. I know they exist somewhere, but I'd not judge someone's programming ability/willingness by their English writing ability/willingness. | |
| ▲ | satvikpendem 3 hours ago | parent | prev | next [-] | | I could vibe code the hell out of something but write a good README for it by hand, doesn't mean that something is actually good. But yes, A -> B != B -> A, as your last sentence says. | |
| ▲ | roywiggins 6 hours ago | parent | prev [-] | | From my point of view, if I wanted an AI summary of a project I could generate one myself. An unlabeled AI readme is almost worse than nothing! I've generated AI readmes myself- they can be useful- but they aren't something to show off. I'll read a badly-formatted readme written by a human with far more interest than a formulaic LLM summary of a project. But it seems like nobody even notices a readme is slop because it has nice Markdown, and my best guess as to why is that people have become habituated to this stuff. |
|
|
| ▲ | add-sub-mul-div 7 hours ago | parent | prev [-] |
| In this case the point is that they accompany the new flood of low-effort self-promoted shovelware vibecode projects. |
