Iโm building my career at the intersection of Cloud & AI. ๐
My journey started with Cloud Engineering and AWS.
Now Iโm expanding into:
โ๏ธ Cloud & DevOps
๐ค AI & LLM Engineering
๐ง AI Agents & Automation
๐ Python
๐ Real-world projects
Iโll be documenting what I learn, what I build, the challenges I face, and the lessons I discover along the way.
๐ณ๐ฌ Building from Nigeria.
If youโre also learning, building or working in tech, letโs connect.
Your AWS bill can teach you a lesson that no tutorial will.
You can build an application that works perfectly and still make a costly engineering mistake.
Why?
Because working doesnโt always mean well-designed.
Before deploying to AWS, ask yourself:
โ Am I using the right resources for the workload?
โ Have I removed resources I no longer need?
โ Am I monitoring usage and spending?
โ Is my architecture more complicated than necessary?
โ Have I considered what happens as usage grows?
You donโt need the most expensive architecture to build a great solution.
You need an architecture that meets the requirements, protects your users, and makes sense financially.
Good Cloud Engineering isnโt just about making things work. Itโs about making the right things work efficiently.
Cloud engineers, whatโs one AWS cost lesson you learned the hard way?
Building from Nigeria.
Your AWS bill can teach you a lesson that no tutorial will.
You can build an application that works perfectly and still make a costly engineering mistake.
Why?
Because working doesnโt always mean well-designed.
Before deploying to AWS, ask yourself:
โ Am I using the right resources for the workload?
โ Have I removed resources I no longer need?
โ Am I monitoring usage and spending?
โ Is my architecture more complicated than necessary?
โ Have I considered what happens as usage grows?
You donโt need the most expensive architecture to build a great solution.
You need an architecture that meets the requirements, protects your users, and makes sense financially.
Good Cloud Engineering isnโt just about making things work. Itโs about making the right things work efficiently.
Cloud engineers, whatโs one AWS cost lesson you learned the hard way?
Building from Nigeria.
One important lesson Iโm learning in AI Engineering:
An AI response can sound confident and still be wrong.
Thatโs why building useful AI applications requires more than connecting an LLM to an API.
We also need to think about:
โ Evaluating output quality.
โ Grounding responses in reliable data.
โ Validating tool calls and inputs.
โ Handling failures gracefully.
โ Monitoring performance.
โ Protecting user data.
A successful demo proves that something can work.
Good engineering helps prove when it works, where it fails, and how to improve it.
Thatโs the side of AI Engineering Iโm excited to keep exploring alongside Cloud and DevOps.
Still learning. Still building. Still documenting.