I Lost My Cloud Resume to a Corrupted File — Here’s the GitHub Lesson I Needed

Stephanie Ebolue — Fri, 19 Jun 2026 09:32:39 +0000

I’ll be direct about what happened.
While building my Cloud Resume on AWS, I lost several hours of work to a corrupted local file. My HTML was structured. My CSS was clean. My GitHub repository was completely empty — because I hadn’t prioritized pushing to it.
I’m writing this not as a cautionary tale, but as a practical argument for something I now consider non-negotiable: version control as a discipline, not an afterthought.

Set an AWS Billing Alarm Right Now — Before You Do Anything Else

Stephanie Ebolue — Fri, 19 Jun 2026 09:29:16 +0000

Hey devs 👋
Quick one today — if you’re new to AWS (or even if you’re not), this is your reminder to set a billing alarm if you haven’t already.
AWS is pay-as-you-go, which means every running service is potentially adding to your bill. A billing alarm through CloudWatch + SNS will email you the moment your charges cross a threshold you define. Think of it as a smoke detector for your AWS account.
Steps:
1. AWS Console → search CloudWatch
2. Alarms → Create Alarm
3. Select Metric → Billing → Total Estimated Charge → USD
4. Set threshold (I use $5 as a starting point)
5. Create SNS topic → enter your email
6. Confirm the subscription email from AWS ← CRITICAL STEP
7. Name the alarm → Create
The trap everyone falls into: AWS sends a confirmation email for the SNS subscription. If you don’t click that link, the alarm exists but will never notify you. Check spam. Confirm it. Then you’re good.
Total time: ~5 minutes.
Total peace of mind: immeasurable.
Go set it up. Your wallet is counting on you. 💸☁️

DEV Community: Stephanie Ebolue

I Lost My Cloud Resume to a Corrupted File — Here’s the GitHub Lesson I Needed

Set an AWS Billing Alarm Right Now — Before You Do Anything Else