Builder Passport
Vestor
@kingdomvestor
Web Dev · AI Automation · Building in public
43 posts 93 comments 12 followers 10 following Lagos
June 3
Building web systems and AI workflows | Learning something new with every deploy
Professional Passport
Professional Builder
Free courses and real projects strengthen your Passport.
Your journey
-
01 Learn
Browse free Academy courses
-
02 Prove Done
1 Certificate(s) of Completion
1
-
03 Showcase Done
5 public project(s) · 10 challenge(s)
5
-
04 Discover Done
Recruiter-facing Passport completeness · 100%
100/100
Activity score
A living view of what they’ve been doing — posts, comments, projects, and learning.
Posts
Part 3: Why Shipping Is Not the Same as Solving
Part 3: Why Shipping Is Not the Same as Solving Many teams celebrate when something ships. The feature is live. The project is marked complete. The work is considered done. But shipping is not the same as solving. A solution only works when people actually use it and the outcome changes. Until then, it remains unfinished work dressed up as progress. Too often, effort stops at delivery. The team moves on while the intended users ignore the new tool, stick to old habits, or find workarounds. The original problem stays in place. The better test is simple: Who will behave differently because of this, and how will we know? If that question has no clear answer, the work is not finished. Real completion happens at adoption — when the change takes root and produces the result it was meant to create. Delivery is a milestone. Adoption is the finish line.
Part 2: Shrink the Problem to Something Actionable
Part 2: Shrink the Problem to Something Actionable Sometimes, the problem isn't that we don't understand what needs to be done. It's that we've made it too big to act on. We define the problem so broadly that it becomes overwhelming. Work gets delayed, meetings pile up, and eventually, nothing moves. The solution? Shrink the problem. Break it down into something a specific person can own, complete within a reasonable time, and turn into visible progress. Ask yourself: What's the smallest useful version of this problem we can solve now? Big ambitions matter, but progress comes from breaking them into manageable pieces. Most problems don't stay unsolved because they're too difficult. Sometimes, they're simply too big to start.
Part 1: Diagnose Before You Solve
Part 1: Diagnose Before You Solve One of the biggest mistakes we make is trying to fix problems before fully understanding them. We see something wrong, feel the pressure to act, and immediately reach for a solution. But what if we're fixing the wrong thing? Real progress begins with diagnosis: understanding the root cause, not just the visible symptoms. Sometimes, the issue isn't technology. It's poor communication, unclear ownership, or a flawed strategy. Before proposing a solution, ask yourself: Can I clearly explain the problem without mentioning a solution? If not, investigate further. Skipping diagnosis wastes resources on fixes that change very little. Sometimes, the most productive thing you can do is pause, ask better questions, and understand the problem before trying to solve it.
Why Big Problems Stay Unsolved
Why Big Problems Stay Unsolved We often think solving a problem means finding a solution as quickly as possible. Spot the issue. Find a fix. Take action. But moving fast doesn’t always mean making progress. When we rush to solutions without understanding the real problem, we risk treating symptoms instead of causes. We waste time, direct our energy toward the wrong things, and sometimes create even bigger problems. Over the next four threads, I’ll explore a better approach to problem-solving: - Diagnose before you solve. - Break the problem down into something actionable. - Measure success by adoption, not just delivery. - Expect complexity and be ready to re-diagnose. In this first thread, we’ll look at what happens when we skip diagnosis, why our first solutions often miss the mark, and how rushing to fix things can make them worse. Let’s get into it.
Did you know your browser is already a powerful debugging tool? 👀
Did you know your browser is already a powerful debugging tool? 👀 Most of us open DevTools only when something breaks. But what if I told you it could help you find bugs faster, without randomly changing lines of code? Here are 3 DevTools features I use to troubleshoot web applications: 1. Network tab — Find failed requests Open DevTools, select Network, and reload the page. You can see which requests failed, how long they took, and what responses the server returned. It helps you figure out whether the problem is coming from the frontend, backend, or the request itself. 2. Console — Test before you change your code You can run simple JavaScript commands directly in the browser. Try: `document.querySelector('.btn')` This checks whether an element with the `btn` class exists on the page. Or type: `localStorage` to inspect the browser's local storage object. You can test ideas and inspect values without editing your source code. 3. Performance tab — Find what’s slowing your page down Record a page load or a short interaction. The Performance panel helps you investigate slow JavaScript, expensive rendering, and layout shifts. Instead of guessing why your page feels slow, you can examine what the browser is actually doing. I used to jump straight into the code whenever something felt wrong. Now, I check DevTools first. Sometimes, the clues are already there. I just need to know where to look. The lesson? Don't just write code. Learn to investigate it. What's one DevTools trick you wish you'd learned earlier? 👇
I almost quit Storyloom in the messy middle.
I was this 🤏 close to giving up on the project. Week 1 was exciting. The core feature worked: Text → Carousel → PNG. I felt unstoppable. Then the to-do list started growing. Better authentication Credits Brand library Mobile layout Landing page Deployment The more I added, the harder it became to finish. I almost lost sight of what I was building. Storyloom had one main job: Turn text or a URL into a usable carousel. Everything else could wait. What was going wrong? I kept adding “just one more thing” before making sure the main feature worked well. One decision helped me stay focused: using the same HTML template for both the preview and exported images. This helped keep them consistent without maintaining two separate designs. The change that helped I asked myself: What is the smallest thing Storyloom needs to do to be useful? The answer was simple: Paste text or a URL → Get an editable carousel → Export as PNG. I moved authentication improvements, credits, galleries, and extra designs to the “not built yet” list. Suddenly, the project felt manageable again. The bug that kept me going Screenshots were being taken before fonts finished loading, making the preview and exported images look different. I fixed it by making the page wait until the fonts were ready. After testing, I achieve 20/20 pixel-perfect consistency between the preview and export. That small win gave me more motivation than adding another feature. What kept Storyloom alive? * Finish small tasks before starting new ones. * Write down the next step before closing my laptop. * Share the problems I solve, not just the features I build. Progress over perfection. Sometimes, you don't need more features. You need a smaller plan and the discipline to finish what matters. What's one thing you're cutting or finishing this week to keep your project moving?
How I fixed my AI agent by splitting every prompt
Part 2: How I fixed my AI agent by splitting every prompt In Part 1, I shared how one messy prompt kept failing. Here’s what fixed it. I now treat the agent like a junior developer on a tight deadline. One clear task. One clear output. Then the next task. Here’s the simple process: Write the single goal What is the one thing this step must finish? Example: “Extract the user ID from this JSON.” Give only the needed context Don’t dump the whole project. Pass only the data and rules for this step. Ask for a clean, checkable output Tell it the exact format you want. Example: “Reply with only the user ID as a string. Nothing else.” Check the result yourself and If it’s wrong, fix the small prompt. Don’t add more instructions to the same one. Chain the next small job Take the clean output and feed it into the next prompt. What changed for me: Fewer random errors Easier to debug I can reuse the small prompts later The agent actually finishes the work The model didn’t get smarter. My prompts got smaller and clearer. Practical takeaway If your AI agent is failing, don’t add more words to the same prompt. Split the job. One step. One clean result. Then the next. Here is the link to the Part 1 - https://afr.com.ng/tsf69bv
Why your AI agent keep failing to execute task...
Why your AI agent keep failing to execute task... — Part 1 I spent days fighting one messy prompt. The agent would start strong, then go sideways. It skipped steps. It invented answers. Sometimes it just stopped halfway. I thought the model was the problem but It wasn’t. It was because the prompt was trying to do five jobs at once. Most of us write prompts like this: “Build a full feature, handle errors, format the output, check edge cases, and make it production-ready.” 😂😂😂 That’s too much. The model will start to guessing which part matters most and that’s when things starts to break. I learned the hard way: one giant instruction almost always fails and will mostly not meet your expectations. In Part 2, I’ll show the exact process I now use to split the work into small jobs that actually finish. Have you also had a prompt that looked perfect on paper but kept breaking in real use?
Wall
Leave a note for Vestor. The builder and Africoders staff can moderate this wall.
Sign in to post on this wall.
Comments
Replies across Africoders — open any thread to read the full conversation.
Challenges
5 wins · 6 placed · 6 completed · 6-challenge streak
Weekly · Winner · Won 18 Sep 2026 · ₦5,000
About
Share one useful tool, course, article, video, or resource. Explain what it teaches and who should use it — in simple language.
- Status
- Winner
- Date won
- 18 September 2026
- What they won
- Winner · ₦5,000
- Rewards
- 70 campaign points · Weekly recognition ₦20,000 (staff-selected)
- Rank
- #1
Weekly · Winner · Won 11 Sep 2026 · ₦5,000
About
Imagine you have ₦10M and a full developer team. What problem in Africa would you solve, and how? Write the problem and your solution in 250 words or fewer.
- Status
- Winner
- Date won
- 11 September 2026
- What they won
- Winner · ₦5,000
- Rewards
- 70 campaign points · Weekly recognition ₦20,000 (staff-selected)
- Rank
- #4
Weekly · Winner · Won 4 Sep 2026 · ₦5,000
About
Post about a project you built, are building, or built before. Explain the problem, what you made, and what you learned.
- Status
- Winner
- Date won
- 4 September 2026
- What they won
- Winner · ₦5,000
- Rewards
- 70 campaign points · Weekly recognition ₦20,000 (staff-selected)
- Rank
- #4
Weekly · Winner · Won 28 Aug 2026 · ₦5,000
About
Share something useful. Quality beats volume.
- Status
- Winner
- Date won
- 28 August 2026
- What they won
- Winner · ₦5,000
- Rewards
- ₦5,000 wallet prize for Community Poster of the Week. Nigeria-only; Nigerian bank account required to receive. Must post every day Mon–Fri. Quality over volume — never automatic from post count.
- Rank
- #1
Weekly · Winner · Won 28 Aug 2026 · ₦5,000
About
Tell us your nickname, why you joined Africoders, what you are currently learning or building (or want to learn/build), and the one specific goal you will work toward over the next...
- Status
- Winner
- Date won
- 28 August 2026
- What they won
- Winner · ₦5,000
- Rewards
- 70 campaign points · Weekly recognition ₦20,000 (staff-selected)
- Rank
- #2
Build challenge · Runner-up · Result 5 Oct 2026 · ₦120,000
About
Build something useful. Ship it. Get discovered.
- Status
- Runner-up
- Result date
- 5 October 2026
- What they won
- Runner-up · ₦120,000
- Rewards
- Prize pool ₦400,000 — 1st ₦200,000 · 2nd ₦120,000 · 3rd ₦50,000 · Community Choice ₦30,000. International winners are eligible; Africoders coordinates payout.
- Rank
- #2
- Score
- 82 pts
Weekly · Submitted · Submitted 25 Sep 2026 · Up to ₦20,000
About this challenge
Use a platform feature (Learn, Build, Community, Passport, messaging, etc.) and share honest feedback: what worked, what was confusing, what you liked, and what should improve.
- Status
- Submitted
- Challenge ends
- 25 Sep 2026
- Prizes to win
-
- Weekly recognition · ₦20,000
- Rank
- #8
Weekly · Joined · Joined 9 Oct 2026 · Up to ₦20,000
About this challenge
Invite one new person to Africoders using your invite link. The referral counts when they complete their profile (username, headline, bio, and onboarding).
- Status
- Joined
- Challenge ends
- 16 Oct 2026
- Prizes to win
-
- Weekly recognition · ₦20,000
Weekly · Joined · Joined 8 Oct 2026 · Up to ₦20,000
About this challenge
Pair with another Africoder. Teach each other something useful, then write up what you taught, what you learned, and who you paired with.
- Status
- Joined
- Challenge ends
- 9 Oct 2026
- Prizes to win
-
- Weekly recognition · ₦20,000
Weekly · Joined · Joined 1 Oct 2026 · Up to ₦20,000
About this challenge
Create a short video (about one minute) teaching the community one useful thing — a tip, tool, concept, or technique.
- Status
- Joined
- Challenge ends
- 2 Oct 2026
- Prizes to win
-
- Weekly recognition · ₦20,000
Proof of work
5 projectsConference-Reg
ActiveLead Developer
Internal registration and room allocation system for a Christian creative conference
Outcomes: Building the import and cleaning core, with planned attendee management, room allocation, meal registration, Supabase-backed administration, and realtime mobile check-in.
Activity
Challenges, projects, and profile milestones.
Skills & stack
Industries: AI/Automation, Content & Media, E-commerce, Education, Fintech, Web3/Crypto