Why ruin good work by letting Claude write it all? Full of em dashes, riddled with Claudisms.

I personally don't mind letting Claude write about work.

You could spend 80% doing the work and 20% writing about it, or 99% doing the work and 1% copy-pasting Claude's writeup about it into a blog.

There is nothing wrong with writing if you are into it, and yes you can probably do better than Claude, but I can related to engineers who just want to build.

▲

spzb 4 hours ago | parent | next [-]

If you can’t be bothered to write it, why should I bother to read it?

	▲	cannonpr 2 hours ago \| parent [-]
		Because it contains information of value to you ? I mean if it doesn’t, just don’t read it.

▲

selfhoster11 4 hours ago | parent | prev | next [-]

I could spend 100% doing the work with my own Claude, and 0% reading yours. That's a negative-sum outcome. I do think that the 80%/20% split is better (though anything that is mostly human voice is fine for me).

▲

Groxx 3 hours ago | parent | prev [-]

Because the failures are so frequent and often load-bearing that it makes it a negative sum to even attempt to read stuff that appears generated.

▲

skybrian 3 hours ago | parent | prev [-]

Why let an obsession with writing style prevent you from learning from a reasonably decent writeup?

	▲	JSR_FDED 2 hours ago \| parent [-]
		He’s doing the author a favor