Let AI brutally roast it, then fix it instantly.
Real roast. Real pain. Real improvement.
def gd(x):
try:
try:
return x['data']['items'][0]['value']
except:
return None
except:
passA function named gd. Nested try/except with bare excepts. One returns None, the other just… gives up. This isn't code, it's a cry for help.
except swallows every error, including KeyboardInterruptpass hides failures from callersdef get_first_item_value(payload: dict) -> str | None:
items = payload.get("data", {}).get("items", [])
return items[0]["value"] if items else NoneThree steps to emotional damage.
Any language, any size. Even that file you're ashamed of.
Be Nice, Roast Me, or Destroy Me. Pick your therapy.
Take the hit, then receive production-ready code.
Three tiers of truth.
Gentle feedback for sensitive souls.
“Hey! Consider adding a few type hints when you have a moment — great job otherwise!”
The classic savage experience.
“You named three variables 'data' in the same function. I'm calling the police.”
Absolutely no mercy.
“I've seen better architecture in a cardboard box. Quit coding. Become a shepherd.”
Submit code, invite a friend, let the community decide whose code deserves more roasting.
Pick a friend or a random dev.
Drop your worst code. Both of you.
Community roasts decide the loser.
Free therapy, or premium humiliation.
Real reviews. Real emotional damage.
“It called my component 'a useEffect graveyard' and honestly? Fair.”
“Got roasted so hard I refactored my entire service on a Friday night.”
“Brutal, correct, and somehow funnier than my standup jokes.”