This is a submission for the DEV April Fools Challenge
What I Built
A CLI that drops a single markdown file into your repo, one that in...
For further actions, you may consider blocking this person and/or reporting abuse
Can't it just learn from my own code?
Not sure about you , But surely mine atleast nowadays
With the right repos, we could train a new model: SlopDiffusion.
This is simultaneously the funniest and most terrifying thing I've seen this week. The
checkIfValueIsNullOrUndefinedhelper wrapping a null check is chef's kiss.We maintain the polar opposite — a CLAUDE.md that explicitly says 'production-grade code, no shortcuts, no TODOs left behind, parameterized queries always, never use var.' It's essentially PURESLOP.md's evil twin.
The scariest part is that half the patterns in PURESLOP.md look exactly like real code I've seen in production repos.
anyeverywhere, try-catch wrapping code that can't throw, comments that restate the line below them. The line between satire and reality is thinner than it should be."The line between satire and reality is thinner than it should be" that's the README I should have written.
And the scariest part of building this was realizing I didn't have to invent any of the patterns. I just had to write them down.
I like the idea of overstepping on ai agent normal too perfect code , this could turn out into a signature file every body make so ai follow our methodology
I love the idea. What about something like SIGNATURE.md?
Ya that's a great name the implementation though is the factor like how a developer will put his signature on , personalization questions maybe or only who needed it like seniors
A simple markdown file could do the job.
Got some 90's vibes here, good job!
In the next sprint, I would add a blink tag to the headings.
Already in the backlog. Priority: critical.
I love it !
glad you do