Prediction: The Shopify CEO's Pull Request Will Never Be Merged nor Closed
birdculture
50 points
8 comments
March 31, 2026
Related Discussions
Found 5 related stories in 50.4ms across 3,471 title embeddings via pgvector HNSW
- 1.5M GitHub pull requests have had ads injected into them by Microsoft Copilot bundie · 340 pts · March 30, 2026 · 45% similar
- I created my first AI-assisted pull request nelsonfigueroa · 67 pts · March 24, 2026 · 42% similar
- A standard protocol to handle and discard low-effort, AI-Generated pull requests Muhammad523 · 138 pts · March 05, 2026 · 42% similar
- GitHub backs down, kills Copilot pull-request ads after backlash _____k · 23 pts · March 31, 2026 · 42% similar
- The bespoke software revolution? I'm not buying it FireBy2024 · 102 pts · March 20, 2026 · 39% similar
Discussion Highlights (4 comments)
osmsucks
This article has a weird tone. It directly criticizes the results of this AI-driven coding effort (which the author admits is of bad quality), while at the same time it tries to reassure the reader that they're not here to criticize the author of the PR. Only of these can be true at the same time.
zug_zug
Yeah -- 93 commits in there. Not to say AI can't make an improvement in a domain like this, but it's definitely not a YOLO situation right now. I use AI code heavily at work and it's quite prolific but also often creates bugs of various severities.
whattheheckheck
Instead of writing a blog post he could have written agentic instructions to fix the mr and prove it works and make another mr and send it back to the ceo
jaredcwhite
Liquid (Ruby) has been a bit of a backwater repo for a long, long time now. I lost confidence in building any of my own websites using it, having forked Jekyll to create Bridgetown which afforded me the opportunity to switch to other template engines (including one I wrote which is a superset of ERB with Liquid-like features called Serbea). Turning a questionable project into a vibe-coded slop fest doesn't surprise me tbh. Folks, unless you neeeeeeed to use Liquid, uh, don't. (Unless you're using another language port of Liquid, in which case maybe it's still fine.)