Spoke at #DevFestLagos this weekend ๐
It was an amazing experience speaking and meeting with folks in the community. I got a lot of feedback on how interactive the session was.
Thank you, @gdglagos
If you attend, how do you find the session?
Repo: bit.ly/lookforthedanfo
Slide: docs.google.com/presentationโฆ
2
22
Mubarak (Poly4) retweeted
In Codelab 2 at DevFest Lagos 2026, Mubarak Alhazan (DevOps Engineer at Catering Rewards) led a hands-on session on From CI/CD to AI/CD: When Gemini Decides Whether Your Code Goes to Production.
His golden rule for putting AI in the deployment pipeline: "Whenever AI makes a decision, write down what you can and let the model judge the rest."
#DevFestLagos2026 #DevFestLagos
I'll be speaking at DevFest Lagos this Saturday ๐
Come see an AI decide whether code goes to production, and help me play gatekeeper managing production
Tickets at devfestlagos.com, 70% off with the code LASTCHANCE
#DevFestLagos
AI is finding its way into almost every part of tech,and software deployment is no exception. ๐
Mubarak Alhazan, @poly4concept DevOps Engineer at Catering Rewards, will be showing us whatโs possible in his #DevFestLagos session, โFrom CI/CD To AI/CD: When Gemini Decides Whether Your Code Goes To Production.โ
๐๏ธ devfestlagos.com | ๐
Nov 13th & 14th
1
3
270
Last week I shared an AI deployment gate I built. It decides whether a code change ships fully, rolls out to a few users first, or waits for a human.
This week I tested whether the AI was actually earning its place ๐งต
1
1
41
So I wrote that rule down as code and left the judgement to the model. With the rules in place, the models caught every dangerous change in the test.
The takeaway: give the model only the judgement that can't be computed and write down the part that can.
1
3
Here is the full write-up, with the numbers and the code to reproduce them: poly4.hashnode.dev/ai-pre-trโฆ
AI is helping us write more code than ever, but most of it still ships on one signal: a green build.
A README typo and a big payments change can both pass CI. Should they ship the same way if the payments service already has alarms firing?
I built something for this ๐งต
๐ค Made with AI
The AI can't deploy anything itself. A separate component holds the deploy permissions.
Getting it to work wasn't the most interesting part. I tested whether the AI was adding value, and what I found changed how I think about AI making production decisions.Sharing that next week
1
2
13
It's open source: github.com/poly4concept/ai-pโฆ
How does your team decide what's safe to ship?
2
12
Most times in Infra: T๐ก๐ ๐ญ๐ซ๐๐๐๐ข๐ ๐ญ๐ก๐๐ญ ๐ง๐๐ฏ๐๐ซ ๐ฅ๐๐๐ฏ๐๐ฌ ๐ฒ๐จ๐ฎ๐ซ ๐ฉ๐ซ๐ข๐ฏ๐๐ญ๐ ๐ง๐๐ญ๐ฐ๐จ๐ซ๐ค ๐ข๐ฌ ๐๐จ๐ญ๐ก ๐ญ๐ก๐ ๐ญ๐ซ๐๐๐๐ข๐ ๐ญ๐ก๐๐ญ'๐ฌ ๐ก๐๐ซ๐๐๐ฌ๐ญ ๐ญ๐จ ๐๐ญ๐ญ๐๐๐ค ๐๐ง๐ ๐ญ๐ก๐ ๐ญ๐ซ๐๐๐๐ข๐ ๐ญ๐ก๐๐ญ'๐ฌ ๐๐ก๐๐๐ฉ๐๐ฌ๐ญ ๐ญ๐จ ๐ซ๐ฎ๐ง ๐ซณ๐๏ธ.
4
122
Rate limiting is the first thing teams reach for against bot attacks. But attackers have adapted. distributed bots using residential proxies can spread requests across 200+ real IPs, each staying under your threshold. Your logs show nothing unusual. ๐งต
That's exactly what happened to us. Rate limiting didn't catch it, as every request looked legitimate. By the time the aggregate told the story, our email sender reputation was already taking damage.
1
2
45
The fix was using AWS WAF CAPTCHA and Cloudflare Turnstile. I wrote about how we diagnosed it, why the obvious defences failed, and how we solved it.
If you're running any public endpoint that triggers an email, this is worth a read: poly4.hashnode.dev/why-rate-โฆ
3
81
Just published this article on importing manual AWS resources into the Serverless Framework Stack
Worth a read if you are doing IAC work: poly4.hashnode.dev/how-to-imโฆ
Just passed the AWS Certified DevOps Engineer โ Professional exam!
Definitely a tough one; long, complex questions that really test your real-world AWS experience.
On to the next one ๐
credly.com/badges/124cf997-6โฆ
4
6
1,630







