> It would constitute signalling possibility the whole effort is superficial
Our company has been developing many core projects for years and one among them is our in-house database Dip. Hiring a writer or spending engineer's time on Dip's docs raises operational cost. Mentality like this gets a startup killed.
Dip's code is pure 100% human written and scrutinized by AI where appropriate. Docs are AI generated and we have it proof-read for correctness. Developers care about documentation being correct and vetted by the people who built the system.
Bitching about docs being AI slop is nothing but virtue signaling.
We are not working for a company here. The 'gzip as a language model' is not a company project. I agree what you say would be right about inner company workings or also when working with contractors and customers. AI can save significant time, and there are another multiple guardrails in place for guaranteeing code will work - and it doesn't even matter if it's generated or written by hand.
This experience doesn't translate to Internet news aggregator at all. We are an audience, not a paying customer. There are no guardrails. And the OP is trying to get our eyes to read his post. The only experience most of us will have with it is the text of the post - so it's basically a main thing. I'm fully in right to note the post is generated with low effort.
Our company has been developing many core projects for years and one among them is our in-house database Dip. Hiring a writer or spending engineer's time on Dip's docs raises operational cost. Mentality like this gets a startup killed.
Dip's code is pure 100% human written and scrutinized by AI where appropriate. Docs are AI generated and we have it proof-read for correctness. Developers care about documentation being correct and vetted by the people who built the system.
Bitching about docs being AI slop is nothing but virtue signaling.