God I hate the emoji and checkmark usage so much. It feels so try-hard cutesy.
Just give me normal bulleted items, I can read.
God I hate the emoji and checkmark usage so much. It feels so try-hard cutesy.
Just give me normal bulleted items, I can read.
I like them. It tells very clearly how much effort went into someone's work.
I like them even more on code comments. It tells _precisely_ how much effort went into the pull request, so I don't spend time reviewing lazy work.
It does not at all indicate the effort that went into doing the thing. Clearly not.
I propose that what you enjoy is having a token of the appearance of effort, easily constructed and easily observed and easily suitable for low-effort handling of these proxy objects for actual work.
I think you’re missing the sarcasm in their comment.
They’re saying that the emoji usage is telling them that very little effort was put into the PR and that they’ll treat it accordingly.
Haha! Thanks!!!
My apologies!, sincerely.
(If only the message I was responding to had had emojis and checkmarks for me to efficiently process it!!!!)
So you just rubber-stamp the lazy work? What else can you do when this PR is assigned to you specifically for reviewing?
Recently I reviewed some vibe-coded stuff and sent a list of issues and suggestions to the “author,” figuring he’d read it and then go through each one with Claude until fixed.
Instead he didn’t read it at all, and just threw the whole thing at Claude Code as a big prompt. The result was… interesting!
This is happening with coworkers now. It’s honestly insulting.
They put up a PR with all the obvious tells, the markdown table of files that changed, the description that basically parrots back things the human obviously wanted them to stress in the task (“this implements a secure, tested (no regressions) implementation of a Foo…”), and the code is an absolute mess of one-off functions placed in any random file with no thought to the way the codebase is actually organized.
Then I give feedback after spending like an hour going through their 2000 line change, and then here comes back an update with a very literal interpretation of my feedback that clearly doesn’t really understand what I was even saying. Complete with code comments that parrot back what I said (“// Use the expected platform abstractions for conversion (not bespoke methods”).
Reviewing coworkers PR’s feels like I’m just talking to the LLM directly at this point, but with more steps and I have less control over the output.
The last place I worked for, if it happened with someone new in the company or the team, I would find a polite way to say "do your job and fix this shit" and it worked.
Some people have put me on their blacklists after these interactions, sure, but they're the exact people I don't want to work with again. The important thing here is that I've never done someone else's work for free.
I guess they just close the PR.
You tell Claude to review it and if it breaks something you blame Claude. No one can get mad at you for it because they don't want to look like luddites.
I wonder if we humans are already checking out from PR reviews from human effort that we've misjudged as AI. we are in so much trouble! lol
Lazy or efficient? A dev could spend an hour on something or 10 mins, if the outcome is the same what's does it matter?
Because the reviewer ends up doing the real work actually checking it works.
The laziness is offloading work down the line.
That has nothing to do with using AI, if the dev didn't check their work then that is being a bad dev.
That’s what this whole thread is about. Appearances of productivity, laziness, and the offloading of real work downstream by sending of “looks good enough” ai generated work.
Checkmarks as bullets on progress/comparison lists I really like, assuming you mean //. The emoji properly put me off looking deeper into whatever it is that I am looking at unless I was really interested to start with.
Both predate common use of LLMs, unless my memory is even more shaky than usual on this, but must have been over-represented in the training data (or something in the tokenising/training/other processes magnifies the effective presence of punctuation) because LLMs seem to love spewing them out.
seriously! it feels so over the top.