I'm not a fan of praising government officials for doing their job. The fascinating thing for me here is the fact that His administration did all of these without borrowing funds and also had to settle debt from 1996
Did you people think you could distract me from posting some @PeterObi goodness? Never!
So walk with me 🚶🏾♂️ let me take you through the first of a three part series detailing Peter Obi's legacy in Anambra state
This first part covers his achievements in Education, roads & health
Your registration endpoint shouldn’t leave orphaned users in the database when the welcome email fails to send.
The problem: user creation lives in PostgreSQL. Email sending lives in an external service. You can’t wrap both in a single database transaction.
The fix: if the email fails, delete the user and their invitation. This is the SAGA pattern. When a multi-system operation fails partway through, you compensate by undoing the completed steps.
Built this today in Go with Resend for email delivery and PostgreSQL transactions for the rollback.
WE ARE IN CHARGE.
Stay On Course: ADC Must Not Be Distracted
Nigeria is a democratic nation. Everyone is free to join or leave any association; political, ethnographic or religious.
However, in politics, intent is often revealed not by declarations, but by patterns. The recent movements around Peter Obi and the African Democratic Congress have followed a pattern that demands scrutiny, not sentiment.
When he made overtures toward the African Democratic Congress (ADC), many within the party approached the overtures with caution—and rightly so.
Political coalitions are not built on optics; they are built on alignment, discipline, and shared purpose. Yet, from the outset, there were contradictions. While engagement was being signaled at the top, a significant portion of his support base remained outside the fold, often antagonistic toward ADC structures and leadership.
That disconnect was not incidental—it was instructive.
Rather than consolidating, there appeared to be an attempt to probe, test, and perhaps reposition internal dynamics. But institutions that are grounded in process do not yield easily to transient ambition. ADC members held their ground. Solidly.
Then came the decisive intervention of the Supreme Court of Nigeria—a ruling that effectively reset the narrative and extinguished the manufactured turbulence within the party. With stability restored and no internal crisis left to exploit, the strategic interest quickly dissipated.
The exit was as telling as the entry.
Now, the relocation to another platform raises familiar concerns. Political migration is not inherently problematic—democracy allows for it. But when movement is frequent, opportunistic, and seemingly tied to where leverage can be maximized rather than where structure can be strengthened, Nigerians must ask hard questions.
We have seen this playbook before:
⬇️Enter where there is momentum
⬇️Attempt to influence internal levers
⬇️Exit when structure resists manipulation
➡️Re-emerge where disruption is easier to manufacture.
And accompanying this cycle is often the orchestration of perception—through elite endorsements, online bullying, curated narratives, or favourable projections that give a false impression of their strength. Figures like Atedo Peterside will now be invoked to lend technocratic credibility, with opinion polls or projections that conveniently elevate a preferred candidacy.
But Nigerians must distinguish between data and design—between genuine public sentiment, engineered and manipulated consensus.
Democracy is not a marketplace for inflated expectations.
A WORD TO ADC MEMBERS.
The temptation to engage distractions is real—but it is also costly. ADC stands today at a critical inflection point. With internal stability reinforced and judicial clarity established, the task ahead is not reaction—it is expansion.
🧊Build stronger ward-to-national structures
🧊Deepen grassroots engagement across all regions
🧊Recruit credible leaders with proven constituency value
🧊Institutionalise discipline and internal democracy
🧊Present a coherent national alternative rooted in policy, not personality
Noise will come—and it will grow louder as momentum builds. But political maturity is measured by focus, not frenzy.
The future of ADC will not be determined by who comes and goes. It will be determined by what is built—and how firmly it stands.
The Bottom Line
Nigeria does not need more political tourism or nomadic movements. It needs commitment, consistency, and character.
Let others chase platforms that bend easily.
ADC, the only credible alternative, must remain a platform that stands firmly.
Stay focused. Stay disciplined. Expand.
Firmly we stand. Arise and shine Nigeria.
God bless Nigeria.
Lauretta Onochie @Laurestar
National Coordinator
1ADC
@atiku@ChibuikeAmaechi@AWTambuwal@raufaregbesola@BolajiADC@aamalamiSAN@omonlakiki@CGD_ADC@dawisu@BalarabeRufai_
O - Organized
B - broad-based
I - Inclusive
D - democratic
I - international
E - excellence-driven
N - Nigerians from every ethnic group.
T - Transparency in governance. -PO
@royaltyuso But AA inferred from his interview that none of this people are ready. There's need for a transition government lead of course by him for "4 or 8" years.
@DejiAdesogan Well minister of defense is busy conducting security checks for a political party convention, meanwhile there's serious insecurity going on in the country
Most people treat CLAUDE.md like a prompt file.
That’s the mistake.
If you want Claude Code to feel like a senior engineer living inside your repo, your project needs structure.
Claude needs 4 things at all times:
• the why → what the system does
• the map → where things live
• the rules → what’s allowed / not allowed
• the workflows → how work gets done
I call this:
The Anatomy of a Claude Code Project 👇
━━━━━━━━━━━━━━━
1️⃣ CLAUDE.md = Repo Memory (keep it short)
This is the north star file.
Not a knowledge dump. Just:
• Purpose (WHY)
• Repo map (WHAT)
• Rules + commands (HOW)
If it gets too long, the model starts missing important context.
━━━━━━━━━━━━━━━
2️⃣ .claude/skills/ = Reusable Expert Modes
Stop rewriting instructions.
Turn common workflows into skills:
• code review checklist
• refactor playbook
• release procedure
• debugging flow
Result:
Consistency across sessions and teammates.
━━━━━━━━━━━━━━━
3️⃣ .claude/hooks/ = Guardrails
Models forget.
Hooks don’t.
Use them for things that must be deterministic:
• run formatter after edits
• run tests on core changes
• block unsafe directories (auth, billing, migrations)
━━━━━━━━━━━━━━━
4️⃣ docs/ = Progressive Context
Don’t bloat prompts.
Claude just needs to know where truth lives:
• architecture overview
• ADRs (engineering decisions)
• operational runbooks
━━━━━━━━━━━━━━━
5️⃣ Local CLAUDE.md for risky modules
Put small files near sharp edges:
src/auth/CLAUDE.md
src/persistence/CLAUDE.md
infra/CLAUDE.md
Now Claude sees the gotchas exactly when it works there.
━━━━━━━━━━━━━━━
Prompting is temporary.
Structure is permanent.
When your repo is organized this way, Claude stops behaving like a chatbot…
…and starts acting like a project-native engineer.