Explaining API secrets but we're both vibe coders

@aimn.dev

1.8K followers · usually 1.7K views a post

Views

150.7K

Likes

9.3K

Comments

111

Shares

511

Selling · SaaS › AI Tool

Claudeseen in 998 videos →https://claude.ai ↗

Why it worked

The video uses a relatable, high-stakes pain point (losing money due to a coding mistake) and provides a clear, actionable technical solution in under 30 seconds.

Summary

A software engineer explains the importance of using .env files to protect API keys from being exposed on GitHub. The video uses a simple visual demonstration to show how this practice prevents costly AWS security breaches.

Structure

1Identify the problem of pushing secrets to GitHub
2Show the consequence of a high AWS bill
3Introduce the .env file solution
4Explain the role of .gitignore
5Show the safe result

Product placement

The video is tagged with #claude in the caption, and the creator uses a visual style consistent with AI-assisted coding tutorials.

On-screen text

Explaining API secrets but we're both vibe coders SECRETS (api key, password) You GitHub aws 40000$ WHAT DO? .env file (in gitignore) SAFE aws 0$

Original caption

Save this for later ⬇️ #coding #softwareengineer #computerscience #programming #claude

More from @aimn.dev

Their other posts in the index, biggest breakout first.

Transcript

Explaining API secrets but we're both vibe coders. You put secret in code. You push code with secret to GitHub. Bot finds your secret in three seconds. Your AWS bill $40,000. You cry. What do? .env file. Put secrets like API key in .env file. .env file put in .gitignore. GitHub never see .env file. Secrets stay secret. Safe. AWS bill $0. Very good, very nice.