DEV Community: Abasiodiong Udofia

Scarcity Captures the Mind

Abasiodiong Udofia — Sun, 05 Apr 2026 02:39:36 +0000

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

“Scarcity captures the mind. […] The mind orients automatically, powerfully, toward unfulfilled needs.”

— Sendhil Mullainathan and Eldar Shafir, Scarcity: Why Having Too Little Means So Much

In the world of AI and software, this often means not having enough computer power—like RAM, graphics cards, cloud credits, or even the ability to run models on your own computer without it slowing down or crashing. When these resources are scarce, your equipment suffers as well as your thinking. You feel more cautious, less willing to take risks, and your innovative ideas slow down because it’s so hard to try things out.

Think about many developers, especially those from underrepresented groups in tech. You might get excited to work with open-source AI models at an event, but your old laptop with only 8 GB of RAM struggles to handle the task. The smallest AI models crash immediately, and trying to fine-tune models on free platforms becomes too expensive. Because of this, you stick to simpler projects, avoid more demanding tasks, and hold back on exploring your ideas. The lack of resources drains your mental energy and motivation. You end up spending more time worrying about what you don’t have than focusing on what you could create.

Mullainathan and Shafir’s research shows that scarcity doesn’t just limit your tools — it limits your bandwidth.

But when you finally get better hardware or enough computer power, everything changes. Suddenly, you’re more willing to try new things, experiment with more complex models, explore ideas that seemed impossible before, and be more creative. The tools are there, just waiting for you, boosting your confidence and encouraging innovation. It’s amazing how access to better resources can unlock your potential and make ideas grow faster.

Prominent voices in AI have echoed this dynamic for years. Andrew has repeatedly described AI as “the new electricity” — a transformative force that democratizes possibility, yet only for those who can plug in. Andrej Karpathy, in his teaching and writing, stresses hands-on experimentation as the fastest path to deep understanding in deep learning; that experimentation requires compute most early-career or resource-constrained developers simply don’t have. Fei-Fei Li’s pioneering work in computer vision and her advocacy for human-centered AI underscore the same point: breakthrough ideas flourish when the infrastructure exists to test them at scale.

On X, the conversation is equally pointed. As one recent post highlighted amid broader discussions on AI’s future:

“Only 27% of women are on AI teams. Only 25% minority representation. 29% of AI teams have zero minority employees… We’re building ‘intelligent’ systems while excluding traditional knowledge systems that have successfully guided human decisions for thousands of years.”

These numbers aren’t accidents of interest. They reflect systemic resource gaps — economic, educational, and institutional — that hit women and marginalized developers hardest. When compute is gated behind expensive hardware or paid APIs, entire communities are quietly locked out of the very experimentation that fuels innovation.

Sheryl Sandberg’s Lean In and Reshma Saujani’s work with Girls Who Code make this connection explicit in the broader fight for gender equity. Support networks and education matter, but so does raw access to the tools. Without them, talented developers are forced to play defense instead of offense.

When barriers fall and resources become available, creativity floods. Diverse teams with equitable access redefine what’s possible. Ideas that once died in low-RAM laptops now scale into production. Concepts that felt abstract suddenly become prototypes. Growth becomes exponential, not incremental.

In short, making sure everyone has equal access to powerful technology is at the heart of supporting gender equity and diversity in tech. It’s about providing access to tools like community labs, affordable cloud credits, open hardware projects, and programs that treat access not as a privilege but as essential infrastructure. When all developers—no matter their gender, background, or where they live can experiment freely and confidently, we unlock a wave of human creativity that AI was meant to amplify.

Yes, resource limitations are real. But the moment those limits are minimized, the potential for innovation roars to life. Let’s work toward a future where no one has to wait to dream bigger because they lack the necessary tools today.

Notion Newsroom AI

Abasiodiong Udofia — Sun, 29 Mar 2026 22:54:10 +0000

This is a submission for the Notion MCP Challenge

What I Built

notion-newsroom — An AI-powered newsroom automation system that enriches breaking news articles with historical context in real-time.

When journalists publish a news article in Notion, the system automatically:

Generates semantic search queries using Gemini LLM to understand the article's core topics
Retrieves relevant historical context from a vector database of past articles, archives, and source materials using ChromaDB
Appends enriched context blocks directy to the Notion page with citations, relevance scores, and source links
Provides explicit feedback via Notion comments, so journalists know what context was found or why it wasn't available

This dramatically accelerates research workflows — journalists no longer need to manually search archives or context databases. The system runs on a schedule and handles mixed data sources (Notion articles, CSV archives, RSS feeds) seamlessly.

Core features:

Automated context discovery with configurable relevance thresholds
Rich Notion block composition with collapsed toggle blocks for clean UI
Explicit error reporting (query generation failures, search unavailable, no relevant matches)
Support for heterogeneous archive sources (UUIDs, short numeric IDs)
Transactional append safety with built-in chunk size validation

Video Demo

Show us the code

GitHub: udofia2/notion-newsroom

How I Used Notion MCP

Notion MCP is the core integration that makes this workflow possible. Here's how:

1. Reading Published Articles

The MCP server exposes Notion page content as queryable objects. The Context Hunter reads drafts and published articles from a Notion database, extracts content, and pipes it into the semantic search pipeline.

# Read article from Notion via MCP
article_content = notion_client.retrieve_block(page_id)

2. Appending Historical Context Blocks

Once context is found and ranked, MCP enables real-time append of rich text blocks to the Notion page:

Composition of nested blocks (toggle → bulleted items → paragraphs with citations)
Support for Notion mentions (linking to source pages) and plain text links (for external archives)
Automatic chunking to respect Notion's per-element constraints

# Append context block with MCP
context_block = build_historical_context_toggle_block(results, article_title)
notion_client.append_block_children(page_id, [context_block])

3. Posting Automation Feedback

Journalists get explicit comments on articles for all outcomes:

✅ "Historical context added: 8 items"
⚠️ "Query generation failed: provider returned server error 503"
🔍 "Search unavailable: embedding model offline"
❌ "No relevant historical context found"

This visibility is critical — silent automation failures destroy trust. MCP comments bridge the gap.

4. Notion Mentions & Links

The system intelligently handles mixed source IDs:

Notion page UUIDs → Rich mentions (mention.page.id)
External/Archive sources → Text links with URLs
Short numeric IDs → Plain text citations with metadata

Why OpenClaw Still Worked After I Uninstalled It

Abasiodiong Udofia — Fri, 27 Feb 2026 08:42:55 +0000

The Setup
The “Wait… What?” Moment
The “Oh… There It Is” Moment
What Was Actually Happening
The Real Fix

I removed it.
I followed the docs.
I deleted everything.

Why is openclaw still responding?

If you’re here, you’re probably in the same situation I was in. You run openclaw and instead of command not found, you get the full usage manual printed back at you, even after following the official uninstall instructions.

📘 The Setup

I installed OpenClaw using the official documentation from openclaw.ai. When I wanted to remove it, I followed their uninstall instructions carefully:

Used the built-in openclaw uninstall
Stopped the gateway service
Removed state directories
Removed global npm install
Checked systemd/launchctl/scheduled tasks

Still… openclaw lived.

🤯 The “Wait… What?” Moment

I verified everything:

View terminal checks


bash
systemctl list-units | grep openclaw
# Nothing.

dpkg -l | grep openclaw
# Nothing.

npm list -g | grep openclaw
# Nothing.

At this point, it feels like malware.
The good thing is, it’s not.

🔍 The “Oh… There It Is” Moment

The turning point was running these two commands:

That one word explains everything: hashed

🧠 What Was Actually Happening

I use NVM (Node Version Manager). That means:

Every Node version has its own global npm packages.
I had previously installed openclaw while using Node v22.14.0.
I later switched to Node v25.
But the old Node v22 bin directory was still in my $PATH.
Bash had cached (hashed) the command location.
Even after uninstalling in my current Node version, the old binary still existed in the v22 folder ~/.nvm/versions/node/v22.14.0/bin/openclaw, and Bash kept running it from its cache.

🛠️ The Real Fix

Two commands solved everything:

1. Remove the actual binary

rm -f ~/.nvm/versions/node/v22.14.0/bin/openclaw

2. Clear Bash’s hash cache

hash -r

Then:

which openclaw

Finally returned:
openclaw not found

Gone. For real.

💬 Final Thoughts

OpenClaw’s documentation was correct.

The issue wasn’t the tool.

It was my environment.

If this saved you hours of confusion, share it.

Because someone else right now is typing:

openclaw

And wondering why it refuses to uninstall.

My First Weeks at Web3Bridge

Abasiodiong Udofia — Sat, 12 Jul 2025 16:53:03 +0000

The Journey Begins

My adventure with Web3Bridge started with an early morning departure at 3 a.m., a decision driven by a previous experience of missing an event due to Lagos’ notorious traffic. Determined not to repeat that mistake, I set out in the pre-dawn hours, filled with anticipation for what lay ahead.

Navigating to the Web3Bridge facility was an experience in itself. I noticed the okada* riders here were different from those I was used to as they were meticulous, refusing to start a journey without confirming the exact location. Their cautious approach was a subtle introduction to the precision I’d soon encounter in the program.

First Impressions and New Connections

Upon arriving, I was warmly greeted by Victory, who collected my passport and graciously assisted with printing all required documents at no cost. Her kindness set a welcoming tone. I soon met David Marvellous and Yetunde, who were the first to arrive at the facility. The three of us, bonded by our early arrival, quickly formed a connection that felt like the start of something special.

A member of a previous cohort gave us a friendly introduction, sharing insights about sponsors, past projects, and the bootcamp’s structure. He even pointed out the best room in the facility. Marvellous and I eagerly explored, settling into a room that caught our eye—only to discover it was reserved for the Rust cohort, not Solidity. After a quick shower, I returned to find our preferred room fully occupied, teaching me an early lesson in adaptability.

An Unexpected Role of Becoming Governor

One of the most surprising moments came during the election for cohort governor. My friends playfully teased each other about the role, and I became the target of their jest when Tony called me “Governor.” As an introvert, I dismissed the idea outright, calculating my chances of being elected at a mere 0.001 out of 10. I even tried to disqualify myself by amplifying my introverted tendencies during introductions. When asked to present myself, I hid behind others and even slipped out the door—only to be spotted by Mrs. Awosika, whose sharp eyes missed nothing.

To my shock, Tony nominated me during the election. I bolted out of the room again, but Mrs. Awosika had me brought back to face the nomination. Despite my protests and attempts to rally votes for others, like Tony and Akanimo who was very popular, the cohort elected me as governor, with Yetunde as my assistant. It was a humbling moment that pushed me out of my comfort zone and into a leadership role I never expected.

Settling into the Community and Supports

The Web3Bridge experience is enriched by free meals, accommodation, reliable electricity, internet, and endless learning opportunities. The arrival of food was a highlight, cohort members burst into praise and worship songs, the joy so infectious it could carry us through weeks of hard work.

Our first mentor, Franklin Ejezie provided an engaging introduction to the program, setting clear expectations. As someone new to Web3, I found the ecosystem’s jargon daunting, but Franklin’s approach made it approachable. A memorable moment came when the founder of web3bridge, laughed heartily upon learning that 17% of the class scored zero on a pre-content test. That laughter wasn’t mocking—it was a wake-up call, motivating me to take the lessons seriously. Franklin also inspired me to revive my long-dormant social media presence on X, making it fun to engage online again.

Friends and Mentors as A Supportive Network

The friendships I’ve formed have been a cornerstone of my experience. Deborah, a kind and attentive soul, has made my role as governor manageable. She listens with undivided attention and offers solutions on the spot, making challenges feel surmountable. My close circle—Tony, Akanimo, Tayo, Marvey, DSO, and others—has been invaluable, acting as my unofficial board of advisors. Their support, encouragement, and updates keep me grounded and informed.

Lessons Learned and Goals Ahead

In just two weeks, I’ve gained more knowledge than I did in an entire year prior. From blockchain basics to the intricacies of Web3, the learning curve has been steep but rewarding. What resonates most is the sense of community and the realization that Web3Bridge is not just about technical skills but also about building connections and leadership.

By the end of the 16-week program, I aim to master Solidity, contribute to a meaningful Web3 project, and grow into a confident leader. I’m particularly interested in tackling problems like improving blockchain accessibility for beginners and addressing scalability challenges in decentralized applications.

Looking Forward

My first weeks at Web3Bridge have been a whirlwind of learning, laughter, and unexpected opportunities. As I settle into my role as governor and continue to learn from mentors like Franklin and staff like Deborah, I’m excited to share more about my journey. Stay tuned for my next post, where I’ll dive deeper into my experiences as governor and the evolving world of Web3.

A Web3 Beginner's Perspective on Smart Contracts for Transparency in Africa

Abasiodiong Udofia — Fri, 11 Jul 2025 07:38:38 +0000

As I tinker with Ethereum’s smart contracts in Remix, a tool that feels like a sandbox for my fledgling Web3 experiments, I’m struck by a simple yet profound idea: these self-executing bits of code could bring unprecedented transparency to Africa’s opaque systems. In a continent where trust in institutions often wavers, whether it’s land registries riddled with disputes or public spending shrouded in mystery—Ethereum’s smart contracts offer a tantalizing promise. I’ll explore how smart contracts might reshape transparency in Africa, reflect on my beginner’s journey, and wrestle with the practical hurdles that stand in the way.

The Problem of Trust Deficits in African Systems

Africa’s governance systems often suffer from a lack of transparency. In Rwanda, for instance, land disputes are a persistent headache, with 80% of court cases tied to property conflicts (World Bank, 2023). Across the continent, public spending is frequently criticized for mismanagement—Nigeria’s 2022 budget audits revealed discrepancies that fueled public distrust (CoinDesk, 2024). As a Web3 novice, I see these as symptoms of centralized systems where records can be altered or hidden. Could Ethereum’s smart contracts, immutable and transparent by design, offer a remedy?

Smart Contracts as A Transparent Blueprint

Smart contracts, as I’ve learned through writing basic Solidity code, are like digital agreements that execute automatically when conditions are met. They live on Ethereum’s blockchain, visible to all and tamper-proof. Imagine a land registry in Rwanda using a smart contract to record property ownership. Once a transaction is logged—say, a plot changing hands—it’s etched into the blockchain, accessible to anyone with an internet connection. No backroom deals, no lost paperwork. Projects like Bitland in Rwanda are already experimenting with this, digitizing land titles to reduce disputes (Ethereum.org, 2024).

Or consider public spending. A smart contract could ensure funds for, say, a Kenyan school project are released only when predefined milestones—like completed construction—are verified. This isn’t theoretical; Ethiopia’s Cardano-based Atala PRISM has explored similar ideas for transparent aid distribution (CoinDesk, 2024). As a beginner, I’m captivated by the elegance of this approach: it’s not just about technology but about redesigning trust itself.

My Solidity Experiments from A Beginner’s Lens

Dipping my toes into Solidity via Remix has been both humbling and exhilarating. I wrote a simple contract to track donations, ensuring funds are locked until a recipient meets certain criteria. The code was clunky—my require statements felt like blunt tools—but it worked. Running it on a testnet like Sepolia showed me how Ethereum enforces transparency: every transaction was traceable, every condition enforceable. Yet, I hit a wall with gas fees. Even on a testnet, simulating real-world costs made me realize that a $3 transaction fee is a fortune for many Africans, where daily incomes often hover below $2 (World Bank, 2023).

Opportunity to Rewriting the Rules

The potential is undeniable. Smart contracts could streamline land registries, like Rwanda’s Bitland initiative, reducing disputes by making ownership indisputable. In governance, they could curb corruption by making public budgets transparent—imagine a Nigerian state publishing contract addresses for infrastructure projects, letting citizens verify fund usage. As a Web3bridge student, I see this as a chance for African developers to lead. We’re not just adopting Ethereum; we could build DApps tailored to our context, like mobile-friendly contracts for rural farmers.

Obstacles in The Real-World Grind

But let’s not get carried away. Ethereum’s complexity is a barrier. Writing Solidity isn’t like coding a basic website; it demands precision, and errors can be costly. My Remix experiments crashed when I botched a function—imagine that with real funds. Then there’s infrastructure: only 22% of Africans have reliable internet (Chainalysis, 2023). Without connectivity, smart contracts are a pipe dream. And governments? Many, like Nigeria’s, view decentralization with suspicion, fearing loss of control (CoinDesk, 2024). Scaling solutions like Polygon could lower costs, but they’re not yet mainstream in Africa.

My Take: A Balanced Hope

As a beginner, I’m torn. Smart contracts feel like a master key to unlock transparency in Africa, yet the lock is rusty. The technology is ready—Bitland and similar projects prove it—but the ecosystem isn’t. High gas fees, limited internet, and regulatory pushback are real. Still, I’m optimistic. If African developers like me can master Solidity and build lean, local solutions, we could bridge the gap. Web3bridge’s focus on hands-on learning is a start, but we need broader education and infrastructure investment.

I’d argue the value lies in iterative progress. Smart contracts won’t fix Africa’s transparency woes overnight, but they’re a pattern—a reusable solution—that we can refine. My Remix tinkering is a small step, but it’s taught me this: the blockchain’s transparency isn’t just technical; it’s a mindset. If we embrace it, Africa could lead the world in trust-driven systems.

Sources

Ethereum.org. (2024). Smart Contracts and Blockchain Applications. https://ethereum.org
CoinDesk. (2024). Blockchain for Governance in Africa. https://www.coindesk.com
Chainalysis. (2023). The 2023 Geography of Cryptocurrency Report. https://www.chainalysis.com
World Bank. (2023). Land Governance in Africa. https://www.worldbank.org