Worst Advice Ever
Related videos
I was right again
The PrimeTime
166.7k views
4 words triggered a war
The PrimeTime
150.4k views
You Owe Him
The PrimeTime
71.0k views
The Craziest AI Pivot yet
The PrimeTime
97.7k views
The Craziest Coding Contest Ever
The PrimeTime
54.5k views
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
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
I was right again
The PrimeTime
166.7k views
4 words triggered a war
The PrimeTime
150.4k views
You Owe Him
The PrimeTime
71.0k views
The Craziest AI Pivot yet
The PrimeTime
97.7k views
The Craziest Coding Contest Ever
The PrimeTime
54.5k views
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
Top Comments (10)
We largely solved slop PRs in our open-source projects by adding a prompt injection to the PR template.
The sarcasm is so high I forget it's sarcasm.
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)
We largely solved slop PRs in our open-source projects by adding a prompt injection to the PR template.
The sarcasm is so high I forget it's sarcasm.
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?