Comment

Comment by Aurornis

My strategy is to skim the workshop to find suspicious sections, then prioritize debunking at least one part that makes the creator look bad.

Then respond with that addressed, with a firm but polite explanation that the document has some problems that need to be addressed carefully before we invest time on it.

None of this works if it’s coming from your boss, but it’s very effective at making people think twice before sending you slop.

People only do the workslop thing when they believe the benefits of showing the work outweigh the reputational risks. If they get caught every time they do it and exposed on an email chain, they start doing less.

parent Aurornis 24 days ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton