Pinned Tweet
If you’re looking to automate your Kubernetes deployments and eliminate configuration drift, check out my full tutorial below.
I cover GitHub Actions, Argo CD, and the Argo CD Image Updater step-by-step. 👇
Kubernetes gets a lot easier to manage when Git becomes the source of truth for your deployments.
In this tutorial, Olumoko shows you how to implement GitOps on Kubernetes using Argo CD and GitHub Actions.
You'll also learn how to automate image builds, deploy manifests from Git, and keep your cluster synced through self-healing updates.
freecodecamp.org/news/how-to…
Olumoko Aries retweeted
Role: Senior Devops Engineer
Location: Remote (Lagos preferred) | 8years
Pay: $3K to $5K + Bonus.
Need a Senior Devops Engineer with 8+ Solid hands on experience for a Consultant role.
- It's fully remote with a pay ranging around $3K to $5K + Bonus.
- Available to resume immediately.
If you know anyone or you are sure of yourself?
Click Link to apply below: docs.google.com/forms/d/e/1F…
All the best!
Olumoko Aries retweeted
Any Junior Devops Engineer looking for paid internship?
Stack
AWS x Docker and a little of Kubernetes.
Please send me a link to your resume.
It is a good read, worth it.
Lagos Life was built overnight. Keeping it running was another story.
I spoke with @Shalom_HeyEliy about database migrations, fighting bots, the game economy and the engineering behind @lagoslifeapp.
The full story: africanengineer.com/i/lagos-…
Olumoko Aries retweeted
I loved listening to the radio while playing Lagos Run, but I wanted to keep listening after I stopped playing.
So I built this 😂📻🇳🇬
Listen to Nigerian radio anytime, from anywhere.
fm.puzzofme.com, see you in the room!
I built a game where you drive a danfo through Lagos 🚌
Load passengers, dodge okadas, beat the traffic. Plays in your browser, no download.
danfo.horpey.dev/
#LagosRun #Lagos #IndieGame
Olumoko Aries retweeted
Day 3/365 —After Learning GPU architechture, The “Okay, So What?” Problem 😂
Yesterday I finished my deep dive into GPU architecture.
I understood the GPCs.
--> TPCs.
--> SMs.
--> CUDA Cores.
--> Tensor Cores.
--> HBM.
--> Memory bandwidth.
I was feeling pretty good.
Then one question hit me:
“Okay… so how does an actual AI workload use all of this?”
And I realized I had no idea. 😂
So instead of randomly jumping into CUDA tutorials, I spent yesterday mapping out where to go next.
That led me into AI Performance Engineering.
And then I stumbled into DeepSeek.
This is where things got VERY interesting.
DeepSeek had hardware constraints compared with the newest NVIDIA systems because of export restrictions.
So the problem became:
How do you squeeze more performance out of the hardware you can actually access?
One of the answers was going deeper into the software stack.
Custom GPU kernels.
Think about that for a second.
Instead of simply using existing optimized operations, engineers can write highly specialized code that tells the GPU exactly how a particular computation should be executed.
That's insane. 🤯
Then there was model distillation — training smaller models to reproduce capabilities learned from larger teacher models.
And this started changing how I think about AI infrastructure.
AI performance isn't just:
“Buy more GPUs.”
It's an optimization problem across:
Hardware + Algorithms + Software
And that led me into the world of AI Performance Engineering.
Things like:
→ Benchmarking
→ Profiling
→ Debugging
→ Optimization
→ Scaling
→ Resource management
You measure things like:
Latency. Throughput. Memory usage. GPU utilization.
Then you find the bottleneck.
Then you optimize it.
Tools I'm starting to encounter:
• NVIDIA Nsight Systems
• NVIDIA Nsight Compute
• PyTorch Profiler
• Transformer Engine
• NCCL
There's a BIG difference between:
“I can run something on 8 GPUs.”
and
“I can scale this to thousands of GPUs without the whole thing becoming a very expensive space heater.” 😂
That's the rabbit hole I'm entering now:
Distributed training + inference + GPU communication.
Day 3 complete.
And apparently, learning what's inside the GPU was just the beginning. 😂
#GPU #AIInfrastructure #CUDA #NVIDIA #MLOps #PerformanceEngineering #DevOps #LearningInPublic
Day 2/365 — I went inside the GPU today.
And honestly… I think I may have opened a door I wasn't supposed to open. 😂, I entered into so many rabbit holes yesterday and I actually enjoyed it. (Y'all are missing 😉)
Yesterday was about understanding why GPUs exist.
Today, I wanted to understand:
“Okay, but what is actually inside this thing?”
And that's where GPU architecture gets crazy.
Think of an NVIDIA GPU like a massive company.
At the top, you have Graphics Processing Clusters (GPCs).
Inside the GPCs, you have Texture Processing Clusters (TPCs).
And inside the TPCs?
Streaming Multiprocessors (SMs).
The SM is basically a self-contained workshop where the actual computation happens.
And inside this workshop, things get even more interesting:
• CUDA Cores
• Tensor Cores
• RT Cores
• Warp Schedulers
• Registers
• Shared Memory / L1 Cache
• Texture units and other supporting hardware
So I started thinking:
CUDA Cores = the regular workers.
Tensor Cores = the specialists.
RT Cores = the guys doing one very specific job.
😂
CUDA Cores handle general-purpose arithmetic operations.
Tensor Cores are specialized for matrix operations — which is VERY important for AI workloads.
And RT Cores are specialized for ray tracing — calculating things like how light interacts with objects in 3D scenes.
Then I got stuck on Tensor Cores.
Because this is where things start getting REALLY interesting for AI.
Neural networks are basically drowning in matrix multiplication.
And NVIDIA has spent multiple GPU generations making Tensor Cores increasingly specialized for these workloads.
Volta → Turing → Ampere → Hopper → Blackwell → Rubin.
And Rubin is where my brain started buffering. 😂
NVIDIA's Rubin GPU has:
336 billion transistors. 🤯
224 Streaming Multiprocessors. 🤯
896 Tensor Cores. 🤯
288GB of HBM4. 🤯
And up to 22 TB/s of memory bandwidth. 🤯
TERABYTES/Per second. (I don't think y'all are clocking how insane this is!!!)
At this point I stopped studying and started staring at the numbers.
😂
But here's the part I found even more interesting:
Compute is useless if you can't feed the compute fast enough.
You can have incredibly powerful Tensor Cores sitting there ready to work…
…but if the data isn't arriving quickly enough, your expensive compute resources can sit around waiting.
This is why memory architecture matters so much.
Rubin combines its compute with high-bandwidth HBM4, and NVIDIA says the GPU can have up to 288GB of HBM4 delivering up to 22 TB/s of bandwidth.
And then there's TMA — Tensor Memory Accelerator.
TMA isn't new to Rubin; it was introduced with Hopper.
Its job is to make moving multidimensional blocks of data between global memory and shared memory more efficient, while taking some of that data-movement/address-calculation work away from the SM's normal instruction pipeline.
So my mental model today became:
GPU architecture isn't just about having more compute.
It's about:
Compute + Memory + Data Movement + Scheduling
All working together.
And I'm beginning to understand why AI infrastructure is so much more than:
“Just give me a GPU.”😂
Day 2 complete.
Tomorrow, I'm going deeper into Tensor Cores.
Because apparently I enjoy suffering.
#GPU #AIInfrastructure #CUDA #NVIDIA #MLOps #DevOps #LearningInPublic
Olumoko Aries retweeted
I’m starting a new 12-month learning journey:
GPUs + AI Infrastructure.
I’ve spent years building and operating cloud infrastructure, Kubernetes platforms, CI/CD pipelines, and production systems.
Now I want to understand the infrastructure underneath modern AI — from GPU architecture and CUDA to distributed training, inference, Kubernetes GPU orchestration, optimization and AI platforms.
For the next 12 months, I’ll be learning in public.
I’ll share:
• What I’m learning
• Labs & experiments
• Architecture decisions
• Things that broke
• Cost/performance lessons
• Projects I build
• Resources that actually helped
No pretending to be an expert.
Just 12 months of consistent learning and building.
If you’re interested in GPUs, AI infrastructure, ML platforms, cloud, Kubernetes or just learning something difficult alongside others:
Join me.
Day 1 starts now. 🚀
#GPU #AIInfrastructure #MLOps #DevOps #Kubernetes #Cloud
Olumoko Aries retweeted
This is September 24, 2026(late 2026)
No AI, I repeat, NO AI will delete your DB without your permission!!!
Infact, if it's a production DB, the AI will advise you not to delete it!
Olumoko Aries retweeted
Kubernetes gets a lot easier to manage when Git becomes the source of truth for your deployments.
In this tutorial, Olumoko shows you how to implement GitOps on Kubernetes using Argo CD and GitHub Actions.
You'll also learn how to automate image builds, deploy manifests from Git, and keep your cluster synced through self-healing updates.
freecodecamp.org/news/how-to…
Olumoko Aries retweeted
If you’re looking to automate your Kubernetes deployments and eliminate configuration drift, check out my full tutorial below.
I cover GitHub Actions, Argo CD, and the Argo CD Image Updater step-by-step. 👇
Kubernetes gets a lot easier to manage when Git becomes the source of truth for your deployments.
In this tutorial, Olumoko shows you how to implement GitOps on Kubernetes using Argo CD and GitHub Actions.
You'll also learn how to automate image builds, deploy manifests from Git, and keep your cluster synced through self-healing updates.
freecodecamp.org/news/how-to…
Olumoko Aries retweeted
Very useful if you’re preparing for an interview session ahead of you..
A must watch…
Or maybe 'originality' in it self is just overhyped? creativity is mostly about synthesizing and reinventing existing ideas through a new lens, not pulling concepts out of thin air.
3
533
Resources every software engineer should know about 📌
not courses. not certifications.
just stuff worth bookmarking.
1. Uber Engineering
real systems, scaling, infra + AI
uber.com/blog/engineering/
2. Stripe Engineering
payments, APIs, distributed systems
stripe.dev/blog/topic/engine…
3. Meta Engineering
production ML + infra at massive scale
engineering.fb.com/
4. Cloudflare Learning
DNS, CDN, networking, security, HTTP
cloudflare.com/learning/
5. AWS Architecture Center
real architecture patterns + diagrams
aws.amazon.com/architecture/
6. GitHub Engineering
how GitHub builds and scales its platform
github.blog/engineering/
7. Google Engineering Practices
how engineers actually write and review code
google.github.io/eng-practic…
8. Netflix TechBlog
distributed systems, data + infrastructure
netflixtechblog.com/
Bookmark these.
Reading how companies solve real engineering problems
is a completely different kind of learning.
Olumoko Aries retweeted
Microservices need to communicate, but there’s more than one way to do it.
In this guide, @abisoyeOladayo compares REST, gRPC, and event-driven messaging.
You’ll learn when to use each approach based on performance, scalability, and system design tradeoffs.
freecodecamp.org/news/servic…
Olumoko Aries retweeted
🇺🇸 JUST IN: The White House has reportedly agreed on an ethics package for the Clarity Act and sent the language to certain Senate Republicans, per Eleanor Terrett.
Olumoko Aries retweeted
No worry , Wizkid is HIM…..that man was also looking so healthy🥰🥰 and jacked up💪🏾. Se wiz tin gbe weight ni ?🏋🏾🏋🏾 bobo yen hanssss mehn, baba for d girls ni looto ❤️❤️ #wizkid #AfroNation
Olumoko Aries retweeted
It’s good for focus..
You may have something like this,
-Stock below 20 naira- 50000-100000 units.
-Stock between 50-100 naira- 10-20k units
-Stocks between 100 naira-200 5K-10k units
-stocks above 500 naira, target 1000-5000
Start like this and be adjusting along the way.





























