I didn't start because of AI. I was already building when it arrived.
Then AI came and reframed everything. New tools. New possibilities. A new story about what the market would reward. I leaned in — harder than most, because I had more to prove.
I have seven freeCodeCamp tutorials live.
Not drafts. Not unpublished. Live. With real readers, real comments, real engagement.
I built an SEO audit agent from scratch — Python, Browser Use, Playwright, the Claude API — evolved it through three versions, documented every failure. I built a production RAG system with hybrid search, multimodal vision, and a native MCP server, running on Cloudflare for about $5 a month. Not a demo. Not a tutorial project. Something anyone could deploy today. I built a federated knowledge commons. A suite of Claude Code skills because the defaults weren't good enough for how I actually work. I published on DEV.to, contributed to open source, earned an AWS Community Builder badge, maintained a 100% Job Success Score on Upwork.
I did everything the internet said to do.
2026 still hasn't paid me back.
Here's what nobody tells you when they say "build in public":
The AI era didn't democratize opportunity. It democratized output.
Those are not the same thing. Alex Hormozi said it cleaner than I can: "AI doesn't reduce the value of money. It reduces the value of labor. Big difference."
When everyone can publish a tutorial in a day, seven tutorials mean less. When every developer suddenly has a GitHub portfolio, portfolios stop being signal. When AI writes 90% of the job application emails landing in recruiters' inboxes, the remaining 10% gets buried with them.
The bar to produce something "good enough" collapsed. So the market for "genuinely good" collapsed with it.
I didn't know that when I started. I believed the story — build enough, publish enough, the right person notices. That was the theory.
The theory was wrong.
The data backs this up, but I didn't need the data. I felt it.
Entry-level tech hiring dropped 25% year-over-year in 2024. Developer employment for people aged 22–25 is down nearly 20% from its 2022 peak — a gap that Stanford researchers confirmed opened specifically when generative AI arrived, with younger developers losing work while developers over 35 saw employment grow. Developers are sending out 200–300 applications to get one callback.
Not because they're bad developers.
Because companies are figuring out how much of the work AI can absorb before they need to hire again. And while they're figuring it out, they're not responding.
The silence isn't personal. But it lands personally.
I want to be honest about something I haven't seen written anywhere:
The AI era created a content surplus that made human content invisible.
Think about what happened. AI lowered the cost of creating tutorials, blog posts, open source tools, portfolios. So everyone made more of them. Supply exploded. Recruiter attention didn't. The math was always going to end this way — we just didn't want to see it while we were building.
I spent months producing content that AI could have generated in minutes.
That's not an insult to my work. My work is real, tested, honest — I catch fabrications before I publish, I build systems before I write about them. But the market can't tell the difference at the speed it's moving. It doesn't have time to read deeply enough to notice.
So signal and noise look the same from the outside.
I'm not angry at the technology.
I'm angry that I believed the story around it.
The story went: learn the tools early, document everything, build in public, the market rewards signal. The AI era is the great equalizer. Geography doesn't matter. Credentials don't matter. What you build matters.
I'm from Port Harcourt, Nigeria. I believed this story harder than most, because it was the story that said someone like me could compete on a global market through sheer quality of work.
Maybe that was always naive. Maybe the market never actually worked that way and the AI era just made it obvious faster.
But I built real things. I didn't fake the metrics. I didn't cut corners on integrity. And I still have bills I can't pay.
Here's what I think happened — not just to me, but to a whole generation of developers who did everything right:
We optimized for visibility in a market that was optimizing for cheapness.
Think about what's happening on both sides simultaneously. Applicants are using AI to write cover letters at scale. Recruiters are using AI to screen those cover letters at scale. The human beings — the ones with seven live tutorials and a 100% Job Success Score — are somewhere in the middle of a conversation happening entirely between machines. We became the signal that neither side had time to read.
Recruiters aren't searching for seven-tutorial developers on DEV.to. They're using AI tools to screen 500 applications in the time it used to take to read five. The filtering happens before a human sees anything. And the filters weren't built to find people who built honest, production-grade systems and wrote about them carefully.
They were built for keywords.
We were writing essays. They were scanning for tokens.
I don't know what comes next.
I'm not going to pretend I have a reframe ready. I'm not going to tell you to "niche down" or "build an audience" or "the right opportunities are coming." I'm too tired for that and you'd see through it anyway.
What I know is this:
A lot of developers are sitting where I'm sitting right now. Some of them have more tutorials than me. Some have more GitHub stars, more followers, more credentials. And they're also not getting callbacks.
This isn't a skill problem.
It's a market that moved faster than the promise did.
The AI era asked us to learn fast, build fast, publish fast, adapt fast.
We did.
It just didn't tell us that fast was the only thing it valued — and that the moment we got fast enough, it would stop needing us to be fast anymore.
I built real things. I did it honestly.
The bills are still real too.
Top comments (1)
Great insights in your piece about AI's practical limitations.
As someone active in multiple tech communities, what advice would you give to developers trying to stay grounded while working in this space?