Logo & Brand Identity Designer | Data Science Enthusiast
Python · Excel · Data Analysis · Creative Technologist
Building solutions with data and design.
Count of Distinct: in data analysis means counting unique values without repeating them.
Seeing a young lady striving among many others reminds me of it — not because she is the only one there, but because she stands out as a distinct individual.
Recognize where you belong
10 Backend APIs you’ll find in almost every modern application.
If you’re learning backend engineering, these are worth knowing ↓
1. Authentication API → Registration, login, logout, tokens
2. Authorization API → Roles, permissions, access control
3. User Management API → Profiles, settings, user CRUD
4. Resource Management API → Products, posts, orders, items
5. Payment API → Payments, refunds, invoices, transactions
6. Notification API → Email, push & in-app notifications
7. Analytics API → Events, user behavior & reports
8. File Storage API → Upload, download & secure file management
9. Configuration API → App settings & feature flags
10. Third-Party Integration API → Connect with external services
The goal:
> Don’t just learn how APIs work.
> Build them.
> Ship them.
> Put them in your portfolio.
That’s how you turn backend knowledge into real-world experience.
Knowing APIs won’t make you a good DevOps engineer. Knowing how they work in production will.
Early in my career, I mostly thought about APIs as:
GET → POST → PUT → DELETE
But working on real systems changes the questions:
→ Should this API be public or internal?
→ REST, GraphQL, or SOAP?
→ Should services communicate synchronously or asynchronously?
→ Is this a partner integration or internal service?
→ How do we secure, monitor, and rate-limit it?
→ Should this traffic go through an API Gateway?
→ How do we handle authentication, TLS, retries, and failures?
That's when you realise there isn't just one type of API.
Different API patterns solve different problems:
🔹 REST → Application & service communication
🔹 GraphQL → Flexible data fetching
🔹 SOAP → Enterprise integrations
🔹 Internal APIs → Service-to-service communication
🔹 Partner APIs → External integrations
🔹 B2B APIs → Business system connectivity
The syntax is the easy part.
The real skill is understanding how the API fits into the overall architecture and behaves in production.
That's what separates someone who knows the tools from someone who understands the system.
@DabereNnamani D. Competitor activity.
Product quality and experience would've caused a gradual drop-off, not a sudden stop. A clean break like that usually means something external pulled them away; a competitor's offer, pricing, or convenience.
I can’t forget how I chose not to register for NYSC in March so I could join @3MTTNigeria & pursue my career in Data Science as a graduate of The Federal Polytechnic Offa, Department of A. I.
I’ve learnt a lot between then and now.
And I’m just getting started.
The countdown is officially on. 4 days until #Capstone submissions close.
If you haven't started, today's the day; open your brief and take that first step. If you're already building, keep going; you're closer than you think.
Every hour from here counts. Let's finish strong.
From idea to screen. 💻✨
One project at a time. 🚀
Sharing a little glimpse of what I’ve been working on for this COMPANY.
It takes ideas, collaborations, revisions, and dedication to get these done.
#Design#CreativeProcess#flyers
The first time I heard “MVP,” I thought it meant “Most Valuable Person” 😂
Then along the line, Irealized it means "Minimum Viable Product".
Tech really has its own language. 😅