Let Me Be Honest First
My name is Filebar. I'm a software engineering student in Addis Ababa, Ethiopia. I'm building towards becoming a fullstack developer and, eventually, an entrepreneur.
I don't have a mentor down the street who works at Google. I don't have a startup ecosystem that throws money at ideas. I have the internet, a laptop, and an uncomfortable amount of stubbornness.
And I'm watching the same headlines you're watching: AI is eating software. Every week. A new model, a new tool, a new LinkedIn post about how developers are obsolete.
I did what any reasonable person would do. I looked at the actual data, tested the tools, and thought hard about what this means for someone like me — someone building from a city the world doesn't put on tech maps.
My conclusion might surprise you.
"Software has eaten the world, and now AI is eating software. Developers will specify outcomes while AI generates components." — Capgemini TechnoVision 2026
Most people read that and feel dread. I read it and felt opportunity. Here's the difference in thinking.
What AI Is Actually Doing (Not What Twitter Says)
Let me kill the dramatic narrative first: AI is not writing entire production systems. It is not replacing software architects. It is not going to wake up one morning, email your boss, and take your desk.
What it IS doing — aggressively, right now — is eliminating the tedious, mechanical parts of coding. Boilerplate. Documentation. Unit tests. Basic refactoring. The stuff that used to eat 30–40% of a developer's day.
84% of developers are already using AI tools daily. That number jumped from 76% last year. GitHub Copilot, Cursor, Claude Code — these aren't experimental toys anymore. They're the new default workflow.
Here's the actual shift happening: the developer role is moving up the abstraction layer. You now spend less time typing and more time thinking — about architecture, product decisions, user experience, business logic. The stuff that actually requires a human brain.
If that scares you, the question to ask yourself is: were you only valuable for the typing?
Why Being From Africa Might Be a Secret Weapon
Here's the take nobody says out loud, so I will.
Developers who grew up in resource-constrained environments — slower internet, fewer Stack Overflow answers in their language, no senior engineers to ask — developed something most Silicon Valley developers didn't: deep problem-solving instinct.
We couldn't just copy-paste our way through things. We had to understand them.
That's exactly what the AI era rewards. You can't use AI tools well if you don't understand what you're building. You can't catch hallucinations if you don't know what correct looks like. You can't prompt well if you can't think clearly.
The developers who will struggle with AI are the ones who were never really thinking in the first place — they were just Googling faster. That's not a geography problem. That's a mindset problem.
Meanwhile — the African tech scene is moving. Ethiopian startups are getting funded. Pan-African developer communities are growing. The AI wave is, for the first time in tech history, arriving everywhere at roughly the same time. We are not behind. We are exactly at the starting line.
What I'm Actually Doing About It
I'm learning in public. Every. Single. Day.
I'll post on LinkedIn daily — industry analysis, personal lessons, AI breakdowns, African tech spotlights, CEO insights worth knowing about. Raw and honest, not polished and fake.
I'll write this blog weekly — long-form, researched, opinionated. The kind of writing I wish existed when I started this journey.
I'm betting that radical transparency beats personal branding. Nobody needs another person performing success online. People need someone being real about the climb.
The gap between where I am and where I want to be is not a wall. It's a curriculum. And I'm enrolled.
The One Thing I Want You to Take Away
If you're a developer — student, junior, senior — anxious about where AI takes this industry, stop asking the wrong question.
Stop asking: "Will AI take my job?"
Start asking: "What kind of developer does the AI era actually need — and am I becoming that?"
The answer is someone who thinks across the full stack. Someone who understands systems, not just syntax. Someone who communicates clearly, makes product decisions, and uses AI as leverage rather than a replacement for thinking.
That's who I'm becoming. Out loud, from Addis Ababa, starting today.
Follow the journey. I'll make it worth your time. 🔥
— Filebar · From Addis to Everywhere · Issue 001
Top comments (0)