DEV Community: Congo Musah

Three AIs. One Brain. My Story.

Congo Musah — Thu, 19 Mar 2026 17:04:16 +0000

Three AIs. One Brain. My Story.

How I learned to stop being confused by AI tools — and start using each one like a specialist.

There's a version of me from two years ago who would open a new browser tab every time he had a question — Google, Reddit, a YouTube rabbit hole, maybe a WhatsApp message to a friend who "knows stuff." That version of me spent a lot of energy just finding the door before even walking through it.

Then the AIs arrived. Not one. Not two. Three.
And suddenly I had three very different doors, each leading somewhere completely different. It took me a while to figure out which door was which. This is that story.
I want to be clear about something upfront: I don't use AI to replace thinking. I use it to extend it. There's a difference. And understanding that difference is what made me stop treating every AI tool the same way and start treating each one like a specialist I book an appointment with depending on what I need.
Let me introduce you to my three specialists.

🔵 Tool No. 1 — Perplexity
"The researcher who never sleeps and always cites their sources."
Imagine you need to understand a topic — not just skim it, but actually understand it enough to make a decision or form an opinion. Before Perplexity, I'd fall into the Google trap: ten tabs open, three contradicting each other, and me somehow ending up watching a documentary about something completely unrelated forty minutes later.
Perplexity changed that. My primary use for it is research — pure, clean, sourced research. When I'm trying to understand a market, a trend, a company, a concept, or even just a news story that feels incomplete, Perplexity is my first call. It searches the live web, synthesises what it finds, and — crucially — tells me where it got the information. That last part matters more than people realise. When you're building something, advising someone, or writing something, knowing your source isn't just academic. It's accountability.

"I don't use Perplexity to get answers. I use it to get orientation — a map of a topic before I decide which road to walk down."

One of my favourite flows: I type in a broad question — something like "what's happening in the African fintech space right now" — and Perplexity gives me a synthesis with live citations. Then I follow the threads that interest me. It's like having a research assistant who can speed-read the entire internet and hand you a briefing note in thirty seconds.
Is it perfect? No. Sometimes it misses nuance. Sometimes the sources it cites are contradictory and it doesn't flag that well. But as a starting point for any serious research session? It's the best I've found.
**
My honest ratings:**
CategoryScoreResearch depth9.2 / 10Source reliability8.5 / 10Speed9.5 / 10Conversation feel5.5 / 10Overall utility8.8 / 10
Verdict: Perplexity is the tool I open when I need to know what's real. It's not my companion — it's my fact-checker, my research lead, my orientation device. If you're building anything serious and you're not using it for research, you're spending too much time lost in tabs.

🔴 Tool No. 2 — Claude
"The brilliant co-founder who has read everything you've ever written."
Here's what most people don't know about Claude, or at least what took me a while to discover: it's not just an AI you chat with. It's an AI you can build a context around. And for anyone working on a startup or a serious project, that difference is everything.
I use Claude specifically for startup work. Strategy, positioning, pitch decks, investor thinking, product decisions — the stuff that requires not just intelligence but context. And Claude has a feature that I've genuinely come to rely on: Projects.

I can upload multiple files — pitch decks, research documents, competitor analyses, internal memos, voice notes I've transcribed — and Claude reads all of it. Then when I ask a question, it's not answering in a vacuum. It's answering as someone who has read my actual material.

"Claude doesn't just know things. It knows my things. That's the difference that changes how you work."

Picture this: I'm preparing for a VC conversation. I've uploaded my deck, a market research document, a transcript of a previous investor call, and some notes I wrote at 2am about a pivot I'm considering. I ask Claude: "Given everything you've read, what's the weakest part of my narrative and how would a sceptical investor attack it?"
The answer I get isn't generic startup advice. It's specific, grounded in my actual documents, and often uncomfortably accurate.
That's not a search engine. That's a thinking partner. And for the kind of deep, nuanced, high-stakes thinking that startup-building demands, it's irreplaceable.

Claude also writes well. Beautifully, actually. When I need something to sound considered and precise — not just generated — Claude is where I go. There's a thoughtfulness in its prose that I haven't consistently found elsewhere.
**
My honest ratings:**
CategoryScoreContextual memory (Projects)9.7 / 10Strategic thinking9.3 / 10Writing quality9.5 / 10Real-time information4.5 / 10Overall utility9.4 / 10
Verdict: If you're building something serious and you're not using Claude's Projects feature to upload and work through your actual documents, you're using maybe thirty percent of what it offers. This is where serious builders should live.

🟢 Tool No. 3 — ChatGPT
"The reliable friend who's always available and never makes it weird."
And then there's ChatGPT. My daily companion. The one I message the most — not for the deepest conversations, but for the most consistent ones.
I use ChatGPT for life admin, personal planning, and the kind of thinking-out-loud that doesn't require a specialist. What should I cook this week? Help me plan my schedule around this deadline. I need to draft a message to someone I had a disagreement with — help me strike the right tone. I want to think through this personal decision I'm sitting on.
ChatGPT handles all of it with an ease and warmth that makes it feel less like using a tool and more like texting a very competent friend.

"ChatGPT is the AI I use when I need to think out loud — and I don't want to feel silly doing it."

There's something about ChatGPT's personality that lends itself to casual use. It's conversational in a way that doesn't feel clinical. It meets you where you are. If I'm stressed and I type something slightly chaotic, it doesn't return something stiff and formal — it reads the room and responds accordingly. That's not a small thing. Over time, that consistent, warm availability becomes genuinely useful.

I also use it for quick, on-the-go tasks. Summarise this article. Turn these bullet points into a proper paragraph. Write three options for a subject line. Explain this concept like I'm new to it. These are five-minute tasks and ChatGPT handles them without ceremony. Open it, type, get the answer, move on. That frictionlessness is its own kind of superpower.

My honest ratings:
CategoryScoreConversational feel9.6 / 10Everyday versatility9.2 / 10Speed & ease of use9.4 / 10Deep strategic work6.8 / 10Overall utility9.1 / 10
Verdict: ChatGPT is the AI I'd recommend to someone who's just starting. It's approachable, reliable, and remarkably good at the everyday. Don't underestimate "everyday" — it covers more of your life than you think.

The real lesson isn't which AI is "best." It's that none of them are the same.
The mistake most people make is picking one AI and expecting it to be everything. It's like hiring one person and expecting them to be your accountant, your lawyer, your therapist, and your assistant simultaneously. That's not how specialists work, and increasingly, that's not how AI works either.
I think of my three tools as a team:

Perplexity goes first — it orients me, gives me the landscape, tells me what's real.
Claude goes deep — it knows my context, challenges my thinking, helps me build the hard stuff.
ChatGPT keeps me grounded — it's the daily touchpoint, the planner, the sounding board, the companion.

Together, they cover most of what I need a thinking partner for. Not perfectly. Not without missteps. But consistently well enough that I genuinely can't imagine working the way I used to. The chaos of ten open tabs, the WhatsApp messages asking friends questions they're too polite to say they can't answer, the hours lost to Google rabbit holes — all of that has been replaced by something that, most days, just works.
Find your three doors. Learn which one leads where. And stop using the wrong one just because it was the first one you found.

Thanks for reading. If this resonated, I'd love to know which AI tools you're using and how you split the work between them — drop it in the comments.

A Weekend Exploring the World of Hackers, Scammers, and Online Deception

Congo Musah — Mon, 09 Mar 2026 08:56:42 +0000

This past weekend I decided to explore something many of us hear about but rarely understand deeply — how hackers and online scammers actually gain access to people’s devices, accounts, and personal information.

Out of curiosity, I started watching investigations and educational content from cybersecurity communities such as the Scammer Payback movement. I also read discussions and reports about cybercrime patterns affecting different regions including West Africa, Pakistan, and other parts of the world.

What began as simple curiosity quickly turned into a very eye-opening learning experience.

One thing surprised me immediately: hacking is not always about complex coding or highly sophisticated technology. In many cases, the most powerful tool scammers use is simply understanding human behavior and exploiting small digital weaknesses.

As I explored more, I discovered several common techniques used by cybercriminals.

The Fake Website Trap

One of the easiest ways scammers steal information is by creating fake websites that look exactly like legitimate ones. A fake banking page, a fake login screen, or even a fake online store can trick people into entering their usernames, passwords, or card details.

Once the victim types their information, it goes straight to the attacker.

Sometimes attackers also exploit poorly secured websites by injecting malicious code that redirects visitors to harmful pages.

Because these pages often look identical to the real ones, many victims do not realize what has happened until it is too late.

The Human Hack: Social Engineering

Another major method used by scammers is called social engineering. Instead of attacking computers directly, they target people.

A scammer might pretend to be a bank officer, customer support agent, government official, or even a friend. They might send messages saying your account has a problem or that you need to verify something urgently.

The goal is to create trust or panic so the victim reveals sensitive information like passwords, verification codes, or financial details.

In many investigations I watched, scammers were extremely skilled at conversation. They understand emotions, urgency, and how to push someone into making quick decisions without thinking.

The Man-in-the-Middle Trick

One technique that really caught my attention is called a “Man-in-the-Middle” attack.

This happens when an attacker secretly positions themselves between two parties communicating online — for example, you and a website you trust.

Normally, when you log into a website, your device sends information directly to that website. But in a man-in-the-middle situation, the attacker intercepts that communication.

They can observe the information being exchanged and sometimes even alter it.

Scenario 1: Fake Public Wi-Fi

Imagine you are at an airport, café, or hotel and you see a Wi-Fi network called something like “Free Airport WiFi” or “Hotel Guest Network.”

A hacker nearby might create a fake network with a similar name.

When people connect to it, all their internet traffic passes through the attacker’s system first. This allows the attacker to monitor certain types of information moving between the user and websites.

In poorly protected connections, login details or session information could be exposed.

Scenario 2: Login Interception

Another scenario involves a malicious proxy sitting between a user and a login website.

When the user enters their username and password, the attacker captures the information and then forwards it to the real website so the login still works normally.

From the victim’s perspective, nothing seems wrong. But the attacker now has the login credentials.

The Password Wizard Trick

Another tactic used by scammers involves fake password reset systems that look like legitimate “password wizards.”

Most platforms allow users to reset their password through a guided process. Scammers copy this process and recreate it on fake websites.

Scenario 1: Fake Password Reset Page

A victim might receive a message saying:

“Suspicious login detected. Please reset your password immediately.”

The link leads to a page that looks exactly like the official password reset page.

The victim enters their current password and creates a new one.

However, the page is controlled by the attacker. Both passwords are captured and the attacker can immediately attempt to log into the real account.

Scenario 2: Fake Security Verification

In another case, a scammer might call or message someone pretending to be customer support.

They guide the victim through what they call a “security wizard” or “verification process.”

During this process, the victim might be asked to read out verification codes sent to their phone.

But those codes are actually login authentication codes the attacker requested.

Once the victim shares them, the attacker can take control of the account.

SIM Swap Attacks (Very Common with Mobile Money)

Another dangerous scam that has become common in many countries is the SIM swap attack.

In this situation, a scammer tricks or bribes a telecom agent into transferring your phone number to a new SIM card controlled by them.

Once they control your number, they begin resetting passwords for your bank, email, social media, or mobile money accounts.

Because password reset codes are sent to your phone number, the attacker receives them and gains access to your accounts.

Many victims only realize something is wrong when their phone suddenly loses network service.

WhatsApp Account Takeover

Another scam that has affected many people is WhatsApp account hijacking.

In this scam, someone may message you pretending to be a friend or colleague. They might say they accidentally sent a verification code to your number and ask you to forward it to them.

The code they are asking for is actually the WhatsApp login verification code for your account.

If you send it, they immediately gain access to your WhatsApp account.

Once inside, they often start messaging your contacts pretending to be you and asking for money or promoting fake investment schemes.

What I Learned

After spending the weekend exploring this topic, one big lesson stood out: many cyberattacks succeed not because technology is weak, but because people are unaware of how these tricks work.

Awareness is one of the strongest forms of protection.

Simple habits can make a big difference:

• Always check website addresses carefully before logging in
• Avoid clicking suspicious links in messages or emails
• Never share passwords or verification codes
• Enable two-factor authentication on important accounts
• Be cautious when using public Wi-Fi networks
• Protect your SIM card and report sudden network loss immediately

The internet offers incredible opportunities to connect, learn, and build businesses. But like any powerful system, it also comes with risks.

The more we understand how cybercriminals operate, the better prepared we are to protect ourselves and educate others.

For me, what started as simple weekend curiosity turned into a strong reminder:

In the digital world, awareness is the first line of defense.

I Didn’t Stop Coding. I Just Started Coding Differently.

Congo Musah — Thu, 19 Feb 2026 12:13:00 +0000

Sometime in the middle of last year, I didn’t quit coding.

I leveled it up.

As a founder building across MERN, NestJS, Flutter, Dart, AJAX, PHP, and even jQuery when necessary, I was constantly context switching. Backend logic in the morning. Flutter UI at night. Database indexing somewhere in between.

The bottleneck wasn’t skill.

It was speed.

That’s when I discovered what I now call vibe coding.

And no — it wasn’t laziness.

It was leverage.

What Vibe Coding Really Is

Vibe coding isn’t copy-paste programming.

It isn’t blindly trusting AI.

It isn’t “generate and pray.”

For me, vibe coding means:

Using AI to accelerate execution while your fundamentals stay in control.

When I vibe code, I don’t outsource thinking.

I use the solid foundation I already have — database design, API structuring, async behavior, REST patterns — and then I let AI help me move faster through implementation.

I’m still coding.

I’m just not typing every character manually anymore.

Where It Started

Mid last year, I installed the Blackbox extension in VS Code.

At first, it felt like autocomplete on steroids.

Then I used it to build the first version of the AgriLync waitlist.

Simple stack:

MongoDB schema

Express endpoint

Email validation

Duplicate checks

Clean error responses

I described what I wanted.

It generated a base.

But here’s the key:

I didn’t accept the output.

I refactored it.

Adjusted validation flow

Optimized query handling

Cleaned error structures

Standardized responses

That’s when I realized something important:

AI wasn’t replacing my skill.

It was forcing me to sharpen it.

The Real Shift: From Typing to Directing

When I built Webarb later, I leaned more into vibe coding.

NestJS controllers?
Generated.

CRUD services?
Generated.

Flutter widgets?
Generated.

But architecture?

That was mine.

Database relationships?
Mine.

Auth flow decisions?
Mine.

Security assumptions?
Mine.

AI became an implementation assistant — not an architect.

And that difference matters.

Vibe Coding Pushed Me Into Prompt Engineering (Naturally)

One unexpected outcome?

I became better at giving instructions.

If you give AI vague prompts, you get vague code.

If you give AI structured, specific constraints, you get better output.

So I started learning:

How to structure prompts clearly

How to define constraints

How to specify architecture

How to instruct agents step-by-step

How to iterate responses instead of regenerating blindly

Without realizing it, I was learning prompt engineering in real time.

Not theory.

Practice.

I learned how to:

Instruct agents like junior developers

Break tasks into logical components

Guide outputs toward clean architecture

Refine rather than regenerate

Vibe coding improved my communication skills as an engineer.

That’s something no one talks about.
**
The Discipline Rule**

Let me be honest.

There was a short phase where I started accepting outputs too quickly.

And that’s when things broke.

Async issues.
Poor error handling.
Edge cases not covered.
Inefficient queries.

Not because AI failed.

But because I got lazy reviewing.

That moment taught me the most important rule of vibe coding:

Never ship what you don’t understand.

Now, every generated block goes through:

Refactoring

Cleanup

Naming standard alignment

Edge case review

Performance thinking

AI drafts.

I edit like a senior engineer.

The Pros (When You Use It Right)
1. Speed Without Losing Quality

When building across multiple stacks — MERN backend, Nest APIs, Flutter apps — cognitive fatigue is real.

Vibe coding reduces syntax fatigue.

It frees mental space for:

System design

Scaling considerations

Product thinking

2. Faster Iteration

As a founder, speed matters more than elegance in early phases.

Vibe coding allows:

Rapid prototyping

Fast feature validation

Quick refactoring cycles

You move from idea → working version quickly.

And that changes momentum.

3. It Forces Strong Fundamentals

Ironically, vibe coding exposed weaknesses in my own understanding.

If I couldn’t evaluate generated code confidently, I knew I had a gap.

So I studied more:

Async patterns

Indexing strategies

Security best practices

Architecture layering

Vibe coding didn’t weaken my fundamentals.

It tested them.

The Cons (If You’re Not Ready)
1. Illusion of Progress

You can generate a lot of code fast.

That doesn’t mean you’re building something stable.

If you don’t understand:

Event loops

Query optimization

State management

Error propagation

You’ll ship fragile systems.

2. Debugging Requires Real Skill

Generated code can introduce patterns you didn’t originally write.

If you don’t read and refactor it, debugging becomes painful.

You must review everything.

3. Architecture Drift

AI solves prompts.

It doesn’t protect long-term structure unless you instruct it to.

As a founder, that responsibility is yours.

What You Must Know Before You Start

If you’re a beginner reading this:

Don’t start with vibe coding.

Start with fundamentals.

Learn:

How REST works

How databases index data

How async functions behave

How state flows in your frontend

How authentication works

Then use vibe coding as a multiplier.

Not a crutch.

**
**

I didn’t stop coding.

I still write code manually.

I still debug deeply.
I still design systems intentionally.

But now I build faster.

Cleaner.

More strategically.

Vibe coding didn’t make me less of an engineer.

It made me more of a technical director.

And as a founder shipping products, that shift matters more than typing speed ever did.

Standing Alone Before God -Into a New Year

Congo Musah — Wed, 31 Dec 2025 20:11:00 +0000

As a new year approaches, there is always noise.

Noise about resolutions.
Noise about goals.
Noise about becoming a “better version” of ourselves.

But before the calendar changes, there is a quieter moment many people skip—the moment where you stand alone before God and take stock of your soul.

Not as part of a crowd.
Not behind a leader’s prayer.
Not echoing words you borrowed from someone else.

Just you.

Moving into 2026, I’ve realized that faith cannot be carried into a new year second-hand. You cannot survive what’s ahead on motivational quotes alone. You cannot face uncertainty by reposting hope instead of practicing it.

At some point, faith stops being inspirational and starts being personal.

Regardless of religion, there is a universal truth: every human being must learn to stand on their own feet before God. There will be seasons where community fades, guidance feels distant, and answers don’t come quickly. In those moments, what sustains you is not how loudly you prayed in public, but how honestly you showed up in private.

Hope is not pretending the past year didn’t hurt.
Faith is not denying exhaustion.

Hope is choosing to step into 2026 believing that God is still present—even when clarity is not.

We are entering a year where no quote can do the work for us. Where belief must turn into discipline, prayer into action, and trust into consistency. A year where doing matters more than declaring, and obedience matters more than aesthetics.

Sometimes, the most sincere prayer at the edge of a new year isn’t ambitious or poetic. Sometimes it’s simply: “God, I don’t have everything figured out, but I’m willing to walk.”

And that willingness is sacred.

Standing alone before God does not mean rejecting religion, leaders, or community. It means refusing to outsource your faith. It means taking responsibility for what you believe, how you hope, and how you live.

As we move into 2026, may we carry less noise and more depth. Less performance and more truth. Less borrowed motivation and more grounded faith.

Because when the year truly begins—and challenges inevitably come—it will not be quotes that hold you up.

It will be the quiet strength you built while standing alone before God.

2025: The Year I Built Foundations, Not Perfection

Congo Musah — Tue, 30 Dec 2025 21:32:57 +0000

2025 in one line:
A year of foundation-building, first wins, and learning how hard consistency really is.

I didn’t finish everything I planned.

But I became someone capable of finishing bigger things.

And that matters more.

⸻

What Actually Worked (I’m Finally Giving Myself Credit)

🚀 Career & Tech

This was the year things started to feel… real.

I bagged my first onsite tech job after working in multiple remote roles across african. That alone deserves more weight than I used to give it. I worked professionally with PHP, WordPress, and Sikasoft, and for the first time, my skills were tied to responsibility, deadlines, and impact.

On the technical side, I touched MERN, Node.js, Express, MongoDB, system design, and CI/CD. But more importantly, I didn’t just “learn”—I built.

Some of the projects I shipped or actively worked on:
• AgriLync
• WeBarb
• Artisan Hub
• Real Rate

Along the way, I strengthened my portfolio and—almost without realizing it—started thinking beyond stacks and syntax. I began thinking about products.

Translation: I moved from learning how to build → building things that matter.

⸻
**
🌱 AgriLync: From Idea to Early-Stage Product**

AgriLync deserves its own section because it changed me.

This year, I:
• Created and grew a WhatsApp community
• Built a solid early team
• Hosted webinars
• Designed UI/UX
• Started building dashboards (Grower & Agent)
• Did real strategy work, not just coding

AgriLync moved from a vague idea in my head to an early-stage product with users, conversations, and direction.

That’s not failure.
That’s traction.

⸻

🎤 Visibility, Leadership & Stepping Up

Quietly, I started showing up in rooms I once only watched from the outside.
• Served as a hackathon mentor
• Got invited as a panelist at an AI event
• Attended and learned from multiple webinars
• Began public reflection through DEV posts and journey updates

It didn’t feel loud or dramatic, but I was stepping into thought leadership—learning to share, not just consume.

⸻

*📚 Mind, Growth & Inner Work
*
Beyond tech, I invested in my thinking.

I started reading The Lean Startup and No Excuses. I listened to podcasts, began learning product development, worked on improving my communication, and practiced public speaking—even if only “somewhat.”

Progress here was uneven, but it was real.

⸻

*What Didn’t Work (Without Beating Myself Up)
*
This part matters too.

The pattern was clear:
• Too many parallel goals
• Spiritual, fitness, and reading habits often postponed
• Long gaps of inactivity, especially with consistency-based habits
• Frequent context switching (Node → Flutter → ML → DevOps)

This wasn’t laziness.
It was overload.

I tried to run five lives at once:
• Engineer
• Founder
• Student
• Spiritual growth
• Financial reset

That’s a lot for one human in one year.

⸻

*The Part I Rarely Talk About
*
This year wasn’t just challenging on paper—it was heavy in real life.

There were moments I genuinely felt like giving up.

I found myself in debt. At one point, I lost almost everything I had within a single day. I questioned my decisions deeply, replayed them over and over, and sat with regret—wondering if I had made the wrong choices entirely.

There were sleepless nights, trying to figure out how to recover, how to move forward, and how not to quit.

I even considered shutting down AgriLync.

My roadmap shifted drastically—more than once. Plans I was confident about fell apart. Some days, progress looked like survival, not growth. There were moments I was put out of home, forced to rethink stability while still trying to build something meaningful.

Yet, in the middle of all this, something unexpected happened.

Through my startup journey, I met wonderful people—supportive, kind, and belief-filled. People who reminded me that I wasn’t alone, even when everything felt uncertain.

That season taught me something no course or tutorial ever could:

Resilience isn’t built when things work.
It’s built when you keep showing up after things break.

I didn’t come out of it perfect.
I came out stronger, clearer, and more grounded.

⸻

The Real Wins (The Invisible Ones)

These are the upgrades that don’t show up on GitHub stats:
• I now understand how hard execution really is
• I learned that shipping beats planning
• I experienced community building firsthand
• I tasted real responsibility
• I stopped building only “toy projects”
• I began thinking like a product strategist, not just a developer

Most people never reach this stage.
I did.

⸻

A Hard Truth (Said With Respect)

I don’t have a discipline problem.

I have a focus and energy allocation problem.

My next level isn’t:

“Learn more tech.”

It’s:

Choose fewer things and do them relentlessly well.

⸻

If I Compress My 2025 Into Five Achievements
1. My first paid tech work 💰
2. AgriLync became real 🌱
3. I built multiple usable products 🛠️
4. I stepped into mentorship and leadership 🎙️
5. I started thinking in systems, not tutorials 🧠

That’s a successful year—just not a perfect checklist year.

⸻

One Question That Matters Going Into 2026

I’ll leave myself with this:

Do I want to be a strong engineer who occasionally builds products,
or a product builder who uses engineering as a tool?

I don’t need to answer it loudly yet.
But I already know which direction my feet are facing

Above all, this year reminded me that I am not carrying this journey alone. In moments of loss, confusion, and exhaustion, faith became my anchor—not because everything made sense, but because I trusted that purpose still existed even when clarity didn’t. I’m deeply grateful for the people who showed up, the lessons that reshaped me, and the strength I discovered in seasons I never asked for. As I step into the next chapter, I do so with hope—not the loud kind, but the quiet confidence that growth is unfolding, even when the path isn’t straight. Whatever comes next, I move forward grounded, grateful, and still building.

This is me for the past few Months- growth is not linear 🧨

Congo Musah — Mon, 15 Sep 2025 22:55:53 +0000

When I look back at my developer journey this year, it hasn’t exactly gone as I planned. My roadmap was ambitious, but along the way I’ve realized something important — growth is not a straight line. It’s messy, full of detours, but also full of lessons that stick with you.

My Time with jQuery
“For the past few months, I’ve been working a lot with jQuery and AJAX. Some people may see them as old tools, but for me, they’ve been like a foundation — a way to understand how the web really works. Making dynamic requests, fetching data without refreshing the page, manipulating the DOM — it felt powerful. Almost like React, in its own way. The more I worked with jQuery, the more I noticed how it gave me a small taste of what React tries to solve at a bigger scale.”

A Taste of Real-World Challenges
“At the same time, I’ve been pushing myself to go beyond tutorials. I started integrating third-party authentications — TikTok, LinkedIn, Pinterest, Discord. Real apps, real users, real logins. And trust me, it wasn’t always smooth. Every provider had its quirks, their own OAuth flow, their own way of handling tokens. But through those struggles, I learned something priceless — building for real people is never as simple as the documentation makes it look. It’s in the debugging, the failed requests, the late-night fixes, that I started to feel like a real software engineer.”

My Side Path with Cursor
“And because I didn’t want to lose momentum, I started a personal project with Cursor. Not something big, but enough to keep me productive, to keep my mind sharp, and to remind myself that every small step builds my skillset. Sometimes it wasn’t about finishing the project — it was about staying consistent, staying engaged with the tech, and adopting myself to tools that can shape the future of my career.”

Growth Is Not Linear
“If I’m being honest, my roadmap didn’t unfold the way I drew it up at the start of the year. I thought I’d be deep into Ml and flutter by now, maybe even shipping production-ready apps. Instead, I found myself rediscovering jQuery, battling OAuth integrations, and tinkering with side projects. But looking back, I see that’s okay. Growth is not linear. Every tool I touched, every bug I fixed, every little project I started — they’re all threads weaving together into the developer I’m becoming.”

“So, where do I go from here? Maybe ML, maybe deeper into backend systems, maybe something else entirely. What I know is this — the journey matters more than the roadmap. Because even if it doesn’t go exactly as planned, every detour teaches you something new. And that’s how I know I’m still growing, one line of code at a time.”

Let’s get in touch at https://congodev.netlify.app

[Boost]

Congo Musah — Mon, 15 Sep 2025 22:49:28 +0000

My Transition into System Design: Building Better, Smarter Systems

Congo Musah — Tue, 17 Jun 2025 17:09:28 +0000

From clean code to clean systems — my journey into system design and the architectural insights that changed the way I build.

🚀 My Transition into System Design: Building Better, Smarter Systems

At the end of May, I made a conscious shift in my learning journey — I dove deep into System Design.

It became clear that writing clean, scalable, and maintainable code goes far beyond just knowing a language or framework — it starts with how your entire system is designed.

🔄 Learn — Unlearn — Relearn

I’ve always believed in the cycle of learn–unlearn–relearn. So I paused, re-evaluated, and redirected my focus toward understanding:

What is system design?
Why does it matter?
When do we need it?

This shift opened my eyes to the architectural thinking behind every successful product.

🧱 The Foundation: Architecture & PRDs

I started with:

Architecture patterns
PRD (Product Requirements Document) — understanding how clear documentation shapes the development lifecycle.

🧩 Enter Microservices — Where the Magic Began

Next came Microservices Architecture — and that’s when things got exciting.

I explored:

Architectural styles and service boundaries
API Gateway and NGINX for routing, load balancing, and security
The role of asynchronous communication in system performance

🗃️ Monorepo vs Polyrepo

Version control and project organization also matter. I studied:

Monorepo: Single repository for all services/projects
Polyrepo: Independent repositories for each service/module

Both have their strengths. Knowing when to use one can streamline collaboration and CI/CD processes.

🛡️ Security & Structure

I wrapped up with:

RBAC (Role-Based Access Control) to structure user permissions
ERD (Entity Relationship Diagrams) to visualize data models and relationships across the system

🎯 The Goal

To build systems that are clean, efficient, and easy to evolve.

System design is helping me see how everything connects — from requirements to deployment. And I’m just getting started.

💬 Are you also diving into system design? Share your experience or favorite resources in the comments!

📌 Connect with me on DEV — that’s where I’ll be documenting the journey further.

Dive into jQuery & AJAX Fundamentals – 3-Day Learning Recap with a curiosity mindset. follow with me

Congo Musah — Wed, 28 May 2025 17:03:25 +0000

Over the past three days, I’ve focused on building a strong foundation in jQuery and AJAX, diving into both theory and practice. Here's a breakdown of the key concepts, how they work together, and how I used them in a hands-on project (a simple blog app).

jQuery: What It Is and Why It Matters
jQuery is a lightweight JavaScript library that simplifies DOM manipulation, event handling, and AJAX interactions. It allows developers to write less code while achieving more, especially in projects that rely heavily on dynamic content.

Core jQuery Concepts I Studied
• • Selectors: Easily target HTML elements:
• - $('#id') – selects an element by ID
• - $('.class') – selects elements by class
• - $('tag') – selects all elements of a given tag
• • DOM Manipulation:
• - .text(), .html(), .val(), .addClass(), .hide(), .show()
• • Event Handling:
• - .click(), .on(), .change()

jQuery Filters and Statements
jQuery statements use the $ function as a shorthand for jQuery. Filters help refine selections. Examples:
• $('li:first') // First list item
• $('input:checked') // Checked checkboxes
• $('div:visible') // All visible divs

AJAX: Asynchronous JavaScript and XML
AJAX allows web applications to communicate with a server without reloading the page. It’s essential for dynamic, real-time web apps.
What I Learned About AJAX
• • How it works: AJAX uses the XMLHttpRequest object.
• • Common methods: $.ajax(), $.get(), $.post()
• • Callbacks: success, error
XMLHttpRequest (XHR)
AJAX is built on the XMLHttpRequest object. Key methods include:
• - .open(method, URL)
• - .send()
Example:
let xhr = new XMLHttpRequest();
xhr.open('GET', 'data.json', true);
xhr.send();

jQuery + AJAX: How They Work Together
jQuery simplifies the process of making AJAX calls by wrapping XMLHttpRequest in utility methods like $.ajax() or $.post().
Real-World Scenario: In a blog app:
• • I used jQuery to submit a blog form via AJAX
• • Data was sent to a PHP backend
• • On success, jQuery updated the DOM to show the new post—without refreshing the page

Practical Skills Gained
Select and update DOM elements using jQuery ✅
Use jQuery events like .click(), .on() ✅
Fetch and display JSON data using AJAX ✅
Send form data asynchronously ✅
Handle success and error callbacks ✅
Dynamically update DOM after AJAX responses ✅

Hands-On: Blog Post App
Built with HTML + CSS + jQuery + PHP + MySQL
• • Fetches blog posts from MySQL using PHP
• • Posts are displayed using jQuery and AJAX
• • Form data is submitted asynchronously
• • DOM is updated without full page reload
Backend: PHP + MySQL
Frontend: HTML, CSS, jQuery

Final Thoughts
Mastering jQuery and AJAX fundamentals helped me build dynamic, responsive apps quickly. While modern frameworks like React and Vue handle much of this today, understanding how jQuery and AJAX work gives me deeper insight into how modern front-end works under the hood.

What’s Next?
I’ll continue with AJAX CRUD operations, real-world API integrations, and build a mini project by the end of the week to fully consolidate what I’ve learned.

check out my portfolio here and let's get interactive: https://congodev.netlify.app

Been having fun with TDD for the past two weeks- this is to boost my confidence & and how to logically refactor code

Congo Musah — Fri, 09 May 2025 00:37:15 +0000

Hello Devs! Over the past two weeks, I’ve been sharpening my backend testing skills and diving deep into Test-Driven Development (TDD) using Node.js, Jest, and SuperTest.

Here’s a breakdown of everything I learned and practiced — plus a step-by-step guide to how I implemented it on my backend project.

🔗 GitHub Repo: https://github.com/CongoMusahAdama/webarb-be
🐦 Twitter/X: @1real_vee

1. Test-Driven Development (TDD) The Foundation

I learned that TDD flips the traditional workflow:
• Red – Write a test that fails.
• Green – Write just enough code to make it pass.
• Refactor – Clean up the code while keeping tests green.

This cycle ensures that code is:
• Behavior-driven
• Reliable and testable
• Cleaner over time

2. Unit Testing with Jest

Unit tests target small, isolated functions. Using Jest, I could:
• Test logic like validation, utilities, and controllers.
• Avoid dependencies like databases.
• Use clear structure (AAA Pattern).

I used Unit Testing on the Auth and User Management modules to ensure isolated logic was tested thoroughly.

Arrange
const input = 2;

Act
const result = square(input);

Assert
expect(result).toBe(4);

3. API Integration Testing with SuperTest

To test real-world behavior, I used SuperTest to:
• Simulate HTTP requests (e.g., PUT /profile).
• Test how routes, middleware, and services work together.
• Confirm correct status codes and JSON responses.

✅ I applied Integration Testing to the Barber Management module to verify end-to-end flow and API behavior across multiple components.

✅ Tested Scenarios:
• Authenticated user can update their profile.
• Returns 400 for invalid data.
• Handles errors from services.

4. AAA Pattern – Arrange, Act, Assert

This structure gave my tests clarity:

Arrange
Set up data, mocks, and preconditions

Act
Call the function / make the request

Assert
Check the result or output

5. Mocks and Spies

I mocked database logic using:

jest.mock('../services/userService.js', () => ({
updateProfile: jest.fn(),
}));

This helped me:
• Avoid hitting real DBs
• Test error handling
• Control the response of services

6. Test Coverage

To ensure I tested enough of the code, I used:

[jest --coverage ]

It reports:
• ✅ Statements
• ✅ Branches
• ✅ Functions
• ✅ Lines

🎯 Goal: Write meaningful tests—not just 100% for the sake of it.

These two weeks gave me a solid foundation in:
• TDD mindset
• Unit & integration testing
• Writing clean, maintainable tests

🧑🏽‍💻 I’m open to criticism, suggestions, and areas for improvement — and also ready to collaborate on backend projects using Node.js!

Let me know if you’re starting your TDD journey or want to connect!

🧑🏽‍💻 GitHub: @musahcongoadama
🐦 Twitter/X: @1real_vee

[](`url`)

[Boost]

Congo Musah — Thu, 08 May 2025 20:42:03 +0000

Looking for FastApi Buddy !

Congo Musah — Thu, 27 Jul 2023 21:30:35 +0000

Good day techies, trust y’all good?
Who is currently taking up Fastapi project or have an idea about fastApi
🇬🇭