Engineering Explained
Code quality, testing, architecture, and engineering discipline applied to AI-assisted work.
The collection19 saves · newest AUG 29
Player 1 · this device0 / 19 adopted
- LV.1One Cloud and One Infrastructure File Instead of Five Vendors
- LV.2Staged Deployment Explained for Solo Builders
- LV.3Three Environments in Thirty Minutes
- LV.4Cheap AWS Services and the Ones to Avoid
- LV.5Three Things to Fix Before a Vibe-Coded App Ships
- LV.6Make Internal Knowledge Answerable Instead of Documented
- LV.7A Branching Strategy That Starts Simple
- LV.8Vibe Coding vs. Agentic Engineering: Why the Process Matters
- LV.95 Performance Problems AI-Generated Code Always Misses
- LV.10Git Branching Strategy Every Engineer Uses (Vibe Coders Too)
- LV.115 Performance Fixes Every Vibe-Coded App Needs
- LV.12Reproduce a Research Paper as a Portfolio Project
- LV.13Refactor a Vibe-Coded File in Phases, Not All at Once
- LV.14Write 3 Docs Before Building: Spec, Stack, and Lock Decisions
- LV.15Four Vibe Coding Mistakes That Cost Real Money
- LV.16Three Gaps Found in Almost Every AI-Built App
- LV.17Why Long AI-Written Comments Are Worth Keeping
- LV.18Designing an API Rate Limiter: Fixed Window vs Token Bucket
- LV.19Five Levels of AI Building, From Coder to Engineer