DISAGREE

@skillfoundryio

11.9K followers · usually 1.2K views a post

Views

12.5K

Likes

713

Comments

86

Shares

24

Selling · Course / Info

Skill Foundryseen in 6 videos →https://linktr.ee/skillfoundry ↗

Why it worked

The video uses a strong, contrarian hook ('DISAGREE') and presents a clear, albeit controversial, opinion on a topic relevant to the target audience (programmers). The use of on-screen text and relatable scenarios likely contributed to engagement.

Summary

The speaker argues that developers should understand every line of code in their software, especially when it's shared with others, as it's crucial for professionalism and user experience. They contrast this with personal projects where 'vibe coding' might be acceptable.

Structure

1Introduction and disagreement with 'vibe coding'
2Importance of understanding code for security and data protection
3Distinction between personal projects and shared software
4Responsibility for user experience
5Conclusion: Professionalism requires understanding code

Product placement

The video mentions 'Skill Foundry' in the creator's bio link, implying it's a platform or service related to coding education or development. The content itself discusses the importance of understanding code, aligning with the potential offerings of such a service.

Original caption

As a professional, you should understand every line of code you ship. #coding #programming #LearnCoding #motivation #DevCommunity #developer

More from @skillfoundryio

Their other posts in the index, biggest breakout first.

On-screen text

DISAGREE you should understand ever piece of code that goes into your software not not doing that is dangerous especially especially with security holes especially with confidential data Privacy it depends on what kind I do not vibe code I do not support vibe coding NEED UNDERSTAND OF INTO unless it's a personal if it's just for vibe code your THE MINUTE YOU GIVE THAT SOFTWARE TO SOMEBODY ELSE YOU ARE RESPONSIBLE FOR THEIR EXPERIENCE

Transcript

I disagree. You should understand every piece of code that goes into your software. Not doing that is dangerous, especially with security holes, especially with confidential data. I mean it obviously it depends on what kind of application you're writing. I do not vibe code. I do not support vibe coding. You need to understand every piece of code that goes into your software unless it's a personal project. If it's just for you, who cares? Vibe code your heart out. The minute you give that software to somebody else, you are responsible for their experience. That's part of being a professional. So you need to understand that stuff. So I disagree.