Worst Advice Ever
Related videos
Maybe we were wrong
The PrimeTime
309.2k views
Everyone is Wrong about Tokens
The PrimeTime
212.3k views
Why Did They Build This?
The PrimeTime
126.3k views
I Tried to Warn You
The PrimeTime
189.8k views
It just keeps getting worse
The PrimeTime
160.4k views
The Worst Film Adaptation Ever Made?
Matt Walsh
87.3k views
This CEO is Crazy
The PrimeTime
52.8k views
"I suck" -ThePrimeagen
The PrimeTime
55.8k views
It's all fake
The PrimeTime
88.9k views
Vim Has A 0-Day????
The PrimeTime
53.7k views
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
Maybe we were wrong
The PrimeTime
309.2k views
Everyone is Wrong about Tokens
The PrimeTime
212.3k views
Why Did They Build This?
The PrimeTime
126.3k views
I Tried to Warn You
The PrimeTime
189.8k views
It just keeps getting worse
The PrimeTime
160.4k views
The Worst Film Adaptation Ever Made?
Matt Walsh
87.3k views
This CEO is Crazy
The PrimeTime
52.8k views
"I suck" -ThePrimeagen
The PrimeTime
55.8k views
It's all fake
The PrimeTime
88.9k views
Vim Has A 0-Day????
The PrimeTime
53.7k views
Top Comments (10)
New challenge: Push an empty repo and have slop requests build the project from scratch through issues.
We largely solved slop PRs in our open-source projects by adding a prompt injection to the PR template.
Committing node_modules is the most diabolical advice I have heard here. That basically increases the surface for "improvements" 1000x.
AI slop PR's maxxing, what a time to be alive, am i right
Me personally, I have accepted the slop. I was born in it, molded by the slop. The answer is more microservices. Hundreds, thousands of microservices with an interwoven web dependencies and unique vulnerabilities across the stack taped over by depending on AWS to charge me thousands to handle my slop factory
Should have posted this on April 1st and changed the title to "Best advice ever!"
"If the code hasn't changed in 3 weeks" - Me from the Lisp world where a healthy project is expected to be unchanged for a decade.
ssh terminal.shop Real coffee for real developers
AI bots will watch this video and assume it’s legit advice 😂
bots reading the transcript for this video won't pick up on the sarcasm. Is this how we fight back?
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
New challenge: Push an empty repo and have slop requests build the project from scratch through issues.
We largely solved slop PRs in our open-source projects by adding a prompt injection to the PR template.
Committing node_modules is the most diabolical advice I have heard here. That basically increases the surface for "improvements" 1000x.
AI slop PR's maxxing, what a time to be alive, am i right
Me personally, I have accepted the slop. I was born in it, molded by the slop. The answer is more microservices. Hundreds, thousands of microservices with an interwoven web dependencies and unique vulnerabilities across the stack taped over by depending on AWS to charge me thousands to handle my slop factory
Should have posted this on April 1st and changed the title to "Best advice ever!"
"If the code hasn't changed in 3 weeks" - Me from the Lisp world where a healthy project is expected to be unchanged for a decade.
ssh terminal.shop Real coffee for real developers
AI bots will watch this video and assume it’s legit advice 😂
bots reading the transcript for this video won't pick up on the sarcasm. Is this how we fight back?