DEV Community: Gold Agbonifo_Isaac

How to actually Create a Portfolio That Gets You Hired (Even Without Experience)

Gold Agbonifo_Isaac — Wed, 22 Oct 2025 05:11:31 +0000

Pick a Focus (What You Want to Be Known For) If your portfolio says, "I can do a bit of everything," people will assume you're not great at anything. Decide who you want to be in people's minds.

Are you "the UI designer who builds sleek SaaS dashboards"?
Or "the growth strategist who gets startups from 0 to 1,000 users"?

When people know what to come to you for, it's easier for them to hire you.

Collect Your Best Work (or Create Mock Projects) Don't panic if you don't have "client work." Most people don't. Create mock projects that solve real problems. The point is to show how you think. Not just what you can make.

Tell a Story Around Each Project Don't just post the finished result. Tell the story behind it. ✅ What problem were you solving? ✅ What was your process? ✅ What went wrong and how did you fix it? ✅ What did you learn? That story is where the magic lives. It makes you human, credible, and memorable. Anyone can say, "I designed this." But not everyone can make a recruiter feel, "Damn, this person thinks deeply."

Add Credibility (Screenshots, Testimonials, Results) Don't be shy. Show proof. If someone loved your work, quote them. If your redesign increased clicks, show the numbers. If you have screenshots, feedback, or messages, include them. Your goal: make anyone scrolling through your portfolio say, "This person doesn't just talk. They deliver."

Get it Live, Fast You've done all this work, don't hide it in your Google Drive. You don't need to code. You don't need to design. You don't need to overthink. Just upload your projects, add your stories, and hit publish. That's literally what I built PortfollyMe for, to help you go from "I don't know where to start" to "Here's my professional portfolio" in minutes.

After speaking with multiple hiring managers and startup founders, I've learned:
They don't care about how many projects you have.
They care about what your projects say about your thinking.
They want to know who they're hiring before they even meet you.

Ready to Build Your Portfolio?

If you're tired of saying "I'll start soon"…

👉 Use PortfollyMe to create your own professional portfolio without doing any real work. All you have to do is upload your random proofs of work, like screenshots, videos, etc, and get a ready-made portfolio like this:

https://www.portfollyme.online/portfolio/tomisin-babs-oxt9o6

[Boost]

Gold Agbonifo_Isaac — Wed, 16 Jul 2025 19:38:39 +0000

How to actually build Multitenant Agents without Redesigning your Architecture

Gold Agbonifo_Isaac ・ Jul 16

#ai #multitenant #architecture

How to actually build Multitenant Agents without Redesigning your Architecture

Gold Agbonifo_Isaac — Wed, 16 Jul 2025 19:37:09 +0000

Multitenancy is often treated as a systems-level problem. Most teams assume they need to overhaul their infrastructure to support multiple users or agents, when in reality, if your system can isolate context, persist memory intelligently, and handle scoped user sessions, you’re already 80% of the way there.

This article explains how to build multitenant agents without redesigning your architecture and explores the practical paths teams can take today to support multiple users from a single agent setup.

What is a Multitenant Agent in AI?

In AI, multitenancy refers to the ability of a single AI system to serve multiple users while keeping each user's data, context, and memory completely isolated. These users are referred to as “tenants”. With multitenancy, even though everyone interacts with the same model, each user gets a private, personalised experience, as if the system were built just for them. This is achieved through proper context handling, session management, and memory separation, without creating new model instances for every user.

A multitenant agent is an AI agent that serves multiple customers (called tenants) simultaneously, while keeping their data, configurations, and interactions completely isolated. That means the same backend, different experiences per user and no mix-ups or data leaks.

A multitenant AI agent can be seen as an apartment building with various tenants(the users), sharing the same elevators, electricity, water, and security. However, tenants have their own private, customised space, different decorations, and furniture inside each apartment. No tenant can see or access another’s apartment in this building. Their spaces are entirely separate, even though they share the same building infrastructure.

A multitenant agent means you don't have to create a new instance for every user or client. An instance is a running version of a program, tool, or service. This architecture offers leverage over traditional single-tenant approaches, where each user requires their own dedicated agent instance.

How to approach Multitenancy in AI agents.

There are three major ways to approach multitenancy in AI agent systems. Each has different implications for control, scalability, and developer experience. Your path will shape your ability to build and how well your agent performs under real-world load.

The Custom Route: Total Control, High Complexity

The most hands-on approach is to build multitenancy from scratch. In this setup, you manage user sessions, store memory, and inject context into every interaction. This usually involves creating a dedicated data layer for storing user-specific memory, using tokens or session IDs to track activity, and writing custom logic to route requests and responses correctly per tenant.

Every time a user interacts with your agent, your system must detect their identity, retrieve their past interactions, apply their settings, and store the result in their isolated memory space. This can work beautifully when done right, providing precise control over how agents behave for different users.

But this level of control comes at a cost. You’re maintaining every part of the infrastructure, memory management, context scoping, session recovery, data isolation, and more. Unless you're backed by a strong engineering team or working in a highly regulated space, this route tends to slow you down more than it empowers you.

MCP (Model Context Protocol):

MCP, or Model Context Protocol, is a structured way to provide an AI agent with everything it needs to act intelligently for a specific user or task. It wraps together instructions, memory, context, personalisation, and task-specific inputs into one package. This protocol is crucial in helping AI agents behave consistently, recall important information, and tailor their responses to different users. If you’re building a personal growth coach, a customer support agent, or a SaaS onboarding bot, MCP is how the AI understands who it’s talking to, what the situation is, and how to behave.

How then does MCP enable multitenancy?

In a multitenant system, where many users or teams are using the same AI infrastructure, MCP is what makes personalisation possible without creating separate AI models for each tenant.

It acts as the boundary between users, loading in their specific memory, preferences, and goals into the AI’s “mind” for each session.

But the downside is, while MCP solves a lot of personalization and scaling problems.

First, because everything the model knows in a session is passed via MCP, the prompt size can become large, which leads to high token usage (i.e., more expensive API calls and slower response times). If you’re injecting long-term memory, task data, system prompts, and personalisation into every single request, that’s a lot of overhead.

Second, there’s a real risk of context conflict or bloat. If the MCP isn’t structured well, for example, if overlapping or outdated memory is injected, the model may become confused, generate irrelevant output, or start mixing tenant data. That’s a big problem in multitenant systems where user isolation is a non-negotiable. One small prompt engineering error or memory leak, and suddenly, User A’s preferences or data might influence User B’s session.

Another issue is maintenance and governance. As you scale, keeping MCP clean, up-to-date, and secure for every tenant becomes complex. You’ll need rules to prune memory, control scope, and validate the data being injected. Otherwise, you risk injecting stale information, which leads to hallucinations or broken workflows.

FASTN:

By now, you’ve seen the two most common ways teams try to “make multitenancy work.”

One gives you control, at the cost of complexity.

The other gives you speed at the cost of durability.

Let’s be honest: neither is ideal for most product teams.

With the custom route, you're effectively building a second product under the hood, managing databases, writing session handling logic, allocating memory, and debugging context bleed issues. All to make your agent usable by more than one person.

Imagine launching a B2B AI tool for HR teams, where every time a new company signs up, your engineers must manually configure how context is stored, what data is remembered, and how that data is retrieved for each user. That’s not scale, that’s technical debt.

With MCP, you can move faster. But the minute someone says, “Can the agent remember what I said last week?” or “Can we track decision history across the team?” you would be back to hacking around prompt windows, compressing memory. Think of a founder building an AI coach for sales teams. It works great with MCP at demo time. But once users start asking for coaching feedback based on their full conversation history, performance drops and personalization breaks.

What if instead of making you build multitenancy or simulate it, you use a native system that supports:

Scoped sessions for each user or tenant

Persistent memory, tied to identity

Private configurations per tenant

Shared logic and infrastructure

Zero leakage, zero duplication

But FASTN goes beyond just session isolation. It includes a Multi-Tenant Embedded App Store built directly into your agent.

This means every user or team can:

Browse and connect apps like Slack, Notion, or Zapier

Individually configure their tokens, settings, and permissions

Use the same agent logic in completely different ways

If you're building agents for real users, not just demos, multitenancy isn’t optional.

👉 Test out what multitenancy should feel like at ucl.dev, or explore the documentation to get started.

Rants of a Beginner Techie 5

Gold Agbonifo_Isaac — Wed, 07 Feb 2024 18:11:21 +0000

It's been a while, and it's my fault. I forgot to share my pains, struggles, and wins with the world for people to learn from. I have been struggling with the worst form of imposter syndrome, and because of this, I couldn't summon the courage to write an article. I mean, there were days I picked up my laptop to write, but I just couldn't. It's weird, I know. I'm back, and as I write this, I wonder why I ever bothered to not let out my thoughts in months. I mean, it is the "rant of a beginner Techie" for a reason, right?

Well, I'll do you the honor of introducing the writer of this unusual blog article. I am Gold Agbonifo-Isaac, a Python developer who probably doesn't know what in the world she is doing and just tries hard to show up every day, hoping that someday, somehow, her consistency would pay off.

How has the year been so far? I know some of you reading this started this year with a huge plan for the year. Maybe it was learning a new skill, getting a job, or even something crazier. Well, at the time of this write-up, it is February 7th, 2024, 4:43 pm in Edo state, Nigeria, and I might not be the best person to give advice, but I want you to not give up. Your future self is cheering you, saying, "You can do this!!! One step at a time, you can do it!"

Find some means to let out the steam after the day's work; this helps. I don't think I have ever mentioned in my previous episodes, but I am a final year undergraduate student of Computer Science, and it is crazy trying to balance tech and school. I want to excel at both school and Tech. It is difficult and requires a lot of planning and devotion, especially since I am a huge volunteer at my school. I organize tutorial classes and events for my department and the Google Developer's Students Club.

It's crazy and hard, but I won't give up! So, fellow human who has for some reason continued to read this unusual article, this is a sign.

"DO NOT, I REPEAT. DO NOT DARE THINK OF GIVING UP! WE, YOU, I CAN DO THIS!"

With this, I, for now, wrap up another episode of the rants. Expect more articles from me sooner than ever. So cheers to the rants! Please share your thoughts or reach out to me at goldisaac33@gmail.com. I am always available to talk or have a meetup!

The Good and Bad Of My First Tech Event

Gold Agbonifo_Isaac — Fri, 08 Dec 2023 10:09:54 +0000

"Hello amazing humans!" with me holding a mic and dressed up all classy, would have been my go-to line if this were showbiz. But it isn't. I am Gold Agbonifo_Isaac and welcome to the Rant of a Beginner Techie series!

Today's rant matches the title: "The good and bad of my first Tech event". I'll delve into what I liked and didn't like about my first tech event. My aim? To share lessons from my journey, hopefully helping others plan their first tech event attendance.

I'd heard endless tales from articles, videos, and social media—how Tech Events catalyze careers. Learn, Network and grow. was all I heard. Typically, The more good they had to say, the more I wanted to experience attending one.

After numerous attempts and disappointments, I finally mustered the courage to attend. It took me months of trying and failing, but I finally overcame my fears and decided to leap. I attended Devfest Benin. Devfest is an event that brings people from various tech fields together.

THE GOOD.

Let me highlight three gems from the tech event:

Everyone was so nice and friendly, it felt like a family that finally came together after trying to plan meetups and failing. The welcoming feeling I got from the environment was gratifying, being surrounded by people who shared similar interests and values provided a sense of support, understanding, and connection.
Listening to Seasoned developers discuss their passions and journeys was truly inspiring. The thought that they too had humble beginnings motivated me in more ways than I could explain with words. I left the event filled with more determination than I came with.
I made new friends and had a ton of fun!

THE Not-so-good

The not-so-good? Introducing myself. I'll explain. In such an environment, beyond your name, and initials, your identity is what you do. Learn how to introduce yourself and what you do so that you don't end up in some awkward moments like I did!

I'll end today's rant with a quote to keep your drive alive.

"The only way to discover the limits of the possible is to go beyond them into the impossible." - Helen Hayes

Reach out to me at goldisaac33@gmail.com, or on Twitter.

Your self-proclaimed bestie signing out!

Rants of a Beginner Techie 4

Gold Agbonifo_Isaac — Tue, 10 Oct 2023 20:59:41 +0000

Hey there, it's Gold Agbonifo Isaac, your self-proclaimed number one fan, even though I have no clue who you are! Welcome back to the "Rants of a Beginner Techie" series, where I'm here to share my joys, pains, struggles, and whatever else comes to mind. Frankly, I'm having a blast doing it!

Just like always, I don't have a strict plan or a fixed idea in mind when I start writing these articles. It all just flows out as I let my thoughts pour onto the page. That's what makes it a rant, after all, isn't it?

It's easy to lose sight of why you started something, who you are, and even your own mental well-being when you get caught up in comparing yourself to others, especially on social media. I used to be guilty of that, too, until very recently. Let me tell you why you should stop it right now.

In the words of wisdom, "YOU'LL DESTROY THE LITTLE SANITY OR ANY SANITY YOU HAVE LEFT!!" Comparing yourself to others is a slow and insidious poison that can leave you with nothing but depression and constant fear gnawing at your soul.

I've had to distance myself from that toxic space by cutting back on content that makes me feel like I'm lagging behind or wasting my time. It's tough, and it seriously crimps my productivity. Trust me, if I were you, I'd avoid it like the plague!

On a brighter note, my first portfolio project is coming together, albeit at a snail's pace. But I'm genuinely proud of all the lessons I'm learning along the way. I'm in no hurry to just build and showcase something I'm not genuinely proud of. I want to burst with pride when I finally complete my project!

Now, let's talk about some of those tech influencers out there. They can really get on your nerves with their do's and don'ts, especially when they're talking about stuff they've never tried themselves. They treat it as though it were "textbook wisdom" and try to cash in on newbie techies. From what I've learned so far, the best strategy is to simply ignore people like that. They tend to pile on unnecessary pressure and stress, and I can't stand it.

Yes, there are some folks out there genuinely trying to help you grow, but sadly, they are few and far between. We, you and I, need to be discerning and not fall into the trap of influencers who are just trying to hawk their products and boost their social media presence. Being a beginner developer doesn't make you or me a fool. We're on our own unique journeys, and we'll make our impact in our own ways!

And with that, my fantastic readers, we've reached the end of today's episode. Join me next time for another exciting episode of "RANTS OF A BEGINNER TECHIE." Feel free to drop a comment or reaction if you're enjoying my series. P.S. I'm really digging this whole series thing, and I'm considering starting one on web development from scratch. I promise it'll be more beginner-friendly than any other web development series out there! Let me know what you think of my idea.

You can also follow me on .

Rants of a Beginner Techie3

Gold Agbonifo_Isaac — Sat, 30 Sep 2023 21:15:47 +0000

Hello and welcome to another episode of "Rants of a Beginner Techie!" It might seem a bit odd that I change my greeting each time, but I enjoy keeping things spontaneous.

Today, as usual, I've got a lot to talk about, and I hope you find something valuable or relatable in what I'm sharing.

Lately, I've been working on a project (it's a secret for now, but I'll reveal it once it's ready). This marks my first real portfolio project. Even though I know HTML, CSS, C, and I'm currently learning Python, this project feels distinct from the ones I did during courses or experiments while learning. It's challenging, and honestly, it feels a bit strange. At times, I even wonder if I'm a bit crazy because a voice in my head keeps saying, "Are you nuts? You'll never finish this!" But I'm not disheartened because I've learned a lot from my past failures. I've gained more programming knowledge and a deeper understanding of tech in general. I'm approaching this project with a startup mindset because I believe that portfolio projects should have a purpose. If I'm going to present them to potential employers, shouldn't they aim to solve real problems? With each passing day, I'm starting to see programming languages as tools for solving problems and building software. I'm building and learning because I want to solve problems I'm passionate about. What interests you? Find a problem and create a solution! Trust me; it's a fantastic way to create a perfect portfolio project. I'm putting my heart into this project.

To be honest, others may have already devised solutions to similar problems, but that shouldn't discourage you. Why? Because we're all unique, and my approach to solving a problem might differ from yours. In fact, I've learned a thing or two by observing someone else's approach, and I'm open to learning more!

I also noticed something else that I'd like to share in today's rant. Some months ago, I frequently experienced burnout, even though I read blogs and watched tech videos. I couldn't pinpoint the cause of my burnout until recently.

I had turned tech into an idol, making it a "do or die" for me. I stopped doing the things I loved and dedicated more time to learning. It's not that I wasn't happy learning new things, but I felt like I was losing myself. I no longer had time for other things I enjoyed. Burnout slowly crept in, and I felt drained every day. So, my advice to anyone reading this, especially beginner techies, is simple: "Just because you're pursuing a tech career or dream doesn't mean you should forget who you are or neglect your family and friends. Be yourself but with a touch of tech." This approach helped me prevent burnout because my mind no longer viewed it as a burdensome task.

Remember to have fun and enjoy the journey! I'm starting to realize that it's a journey, not just a destination.

I'll conclude today's episode with a quote:

"Embrace the tech journey, but don't forget to dance to the rhythm of your own passions along the way."

Thanks for reading! I hope you enjoyed the article. You can reach me on Twitter or send me an email at goldisaac33@gmail.com. I appreciate you all. See you next time!

Rants of a Beginner Techie 2

Gold Agbonifo_Isaac — Sun, 24 Sep 2023 04:45:22 +0000

Welcome to the "Rants of a Beginner Techie" series! If you could see me in person, I'd probably appear as if I were holding a microphone, adopting a showbiz-like persona. The primary goal of this series is to provide a platform for expressing the common frustrations experienced by beginners in the tech world. I'm Gold Agbonifo_Isaac, and here we are with another episode of the rants!

I firmly believe that beginners are the most ambitious dreamers in the tech industry. To be more specific, let's talk about me. Yes, that's a clearer and less accusatory way to express it. I dream of the day when all my hard work will finally pay off. Among dreamers like me, the most challenging are those who have nothing to cover their bills and still depend on their families. They hold onto this tech dream, hoping it will eventually lead them out of their struggles. Each new step they take feels like a new chapter, and sometimes, as beginners, all we really crave is a glimmer of hope.

Imagine this: no money, dwindling motivation, no good news on the horizon, yet we persevere, grinding relentlessly to pursue our dreams. We read stories, listen to podcasts, and sometimes watch videos of people who once walked the same path we're on now. Besides the mental strain of learning something new, it's an entirely different challenge when you see no immediate results and have doubters around you, questioning whether you're wasting your time. If this resonates with you, then I understand because we're in this journey together.

I've recently found the career path I've been yearning for in software engineering, and it's none other than "DevRel Engineering." I don't want to be the type who just sits at a computer coding all day (even though I love that too). I have a deep passion for writing, teaching, giving speeches, and presentations—ultimately, I thrive on helping people. Identifying a path, committing to it, and aligning all my efforts around it has made my journey as a beginner in tech much more captivating. You should consider giving it a try too!

I have this peculiar belief that each career path in tech reflects a person's personality, and I believe I'll excel even more in my chosen field if I find a path that feels tailor-made for me. For me, it's clear that I want to become a DevRel Engineer, and suddenly, the path doesn't seem as daunting. In case you're wondering how a beginner like me stumbled upon this role, well, I was doing my usual research when I decided to delve into the world of DevRel Engineering, reading up on the responsibilities and watching videos of professionals in the field. The thing is, I had come across the title a few times in blogs and decided to satisfy my curiosity by researching it further. So far, I can only envision myself performing the duties of a DevRel Engineer. To be honest, I see it as putting a name tag on doing what I love. I've learned that typically, only senior developers get to become DevRel Engineers. However, I'm undaunted by that and will continue to write, teach, and create things that help people. "Find something you love and become excellent at it" – this is my sole focus right now, and it should be yours if you're like me, a beginner. As Oprah Winfrey once wisely said,

"Passion is energy. Feel the power that comes from focusing on what excites you." - Oprah Winfrey

And with that, we wrap up another episode of "Rants of a Techie." Until next time! Feel free to leave a comment or two if you have something to share, or reach out to me on Twitter.

Rants of a Beginner Techie1

Gold Agbonifo_Isaac — Fri, 08 Sep 2023 05:18:29 +0000

I thought for a long time about what to write for my first post on dev.to. I had a bunch of ideas, like making tutorials or sharing tech tricks. But this morning, at 5 A.M, I came up with something even better.

I started tech blogging for two main reasons. First, I wanted to keep a record of my journey in tech. Second, I wanted to share what I know by doing what I love most – writing. But until now, I never really got the chance to express myself. All I did was write about hacks and technical stuff. Don't get me wrong; I love doing that and put a lot of passion into it. I make sure my articles are easy to understand, especially for beginners.

But now, I want to start a new series called "Rants of a Beginner Techie". It's a bit different, where I'll talk about my thoughts and my good or bad days as a beginner in tech. It might seem strange, but that's what I want to do. Of course, I won't stop writing other types of articles because they're already a part of me that I love, and I couldn't stop even if I tried.

Being a beginner in tech is tough. Some days, I wonder when I'll stop feeling like a beginner. I love learning new things, especially in the tech world, but one thing that really bothers me is something they call "Imposter Syndrome." We all deal with it, I know, but I think beginners like us should have our own special version called "The Beginner's Imposter Syndrome." It's mentally draining and often discouraging, but my determination and dream keep me going.

I find myself spending hours searching for success stories in tech and how others overcame their struggles. It's hard to find something that truly inspires me sometimes. What keeps me motivated is reading or watching the success stories of techies I can relate to. If I can't connect with their journey, it doesn't have the same impact. So, whenever I feel down, I make it a habit to seek out relatable success stories.

I've asked a few people about this, and I wonder, "If even experienced techies struggle with imposter syndrome, what should beginners like myself do?"

I love coding because I enjoy turning ideas into reality and solving real-world problems. Sometimes, the thrill of it all is so intense that I have to take a deep breath to stay calm. I remind myself that I need to learn the tools to make my dreams come true. It's a lot to take in, but starting somewhere is a good step.

Being a newbie in tech is undoubtedly challenging, but I also see it as a time to get to know ourselves and prepare for the tougher days ahead when we're working in the field.

As American author Susan Gale once said, "Anything worth having is worth fighting for."

So, fellow techies, let's buckle up and tackle this journey together. I'll catch you in my next article on "Rants of a Techie!"

You can connect with me on Twitter (or X) at https://twitter.com/Golden_builds.

Feel free to send me a message via email at goldisaac33@gmail.com.

Here's a link to my other blog: https://goldenbuilds.hashnode.dev/