0.5 Conventions: Why → What → How
When a new idea arrives, read it in this order:
| Step | Question | Tiny Instagram-style example |
|---|---|---|
| Why | What breaks if we ignore this? | Mystery zip → wrong badge build is live |
| What | Name the idea in one line | Git keeps history of every change |
| How | Vertical steps you can type | git init → add → commit → status |
| What you see | Success signal | Clean status; clear commit message |
We keep steps as vertical lists (one under another). We do not hide five steps inside one long paragraph.
Lab
Create a free GitHub account if you do not have one. Create an empty public repository named devops-shipit-labs (or any clear name). Clone it to your laptop with git clone <repo-url>, or open it in GitHub Codespaces. Run git status once and confirm you see a clean working tree or an empty repo message. Do not add any AWS keys or .pem files.