This is one of the few AI hills I will die on: not disclosing AI tool usage when you produce a product where the writing is the end result (in this case, the website I'm being sent to) is disrespectful to your readers and users.
`The quickest way to see QSOE run — no hardware, no -kernel juggling.`
`Real hardware, real disk.`
`A working plan, not a contract: milestones may shift as the work reveals what's really next.`
I have no problem with using AI to draft docs, or as an editing tool, or even to help writing (if, e.g., you are not a native speaker) but this is just egregious low-effort slop. If you can't even put the time to write your own documentation (or at least disclose AI tool use), why would I trust you to even test your own sofware?
Dupe. Posted 6 days ago, 29 comments: https://news.ycombinator.com/item?id=48630085
This is one of the few AI hills I will die on: not disclosing AI tool usage when you produce a product where the writing is the end result (in this case, the website I'm being sent to) is disrespectful to your readers and users.
I have no problem with using AI to draft docs, or as an editing tool, or even to help writing (if, e.g., you are not a native speaker) but this is just egregious low-effort slop. If you can't even put the time to write your own documentation (or at least disclose AI tool use), why would I trust you to even test your own sofware?I was going to say dual-kernel seems pretty pointless other than that it's something you can prompt an LLM to implement.
In the other thread (mentioned above) the author says that nearly the entire thing was created by Claude. So yeah, no.