I have a confession: I almost didn't go to any of them.
Each time, there was a reason not to. Too far. Too expensive. Too early on a Saturday. Too many things on my plate. Too much imposter syndrome whispering what would you even say to a Google recruiter?
But I went. And every single time, I walked away with something that no tutorial, no documentation, no YouTube video had ever given me — a clear picture of where I stood, where the industry was moving, and exactly what I needed to do next.
This is the story of four events that quietly rewired how I think about my career as a developer. Not all at once. Not dramatically. But brick by brick, event by event — a map started taking shape.
Event 1: The Cursor × Claude Hackathon — The Day I Stopped Just Writing Code
I want to be honest: I signed up mostly because it was free.
The pitch was something about "agentic engineering" and "AI workflows," and I had a vague sense that I should probably know what those words meant. What I didn't expect was that within the first hour, my entire mental model of what it means to be a developer would be gently — and then violently — shaken.
The format was a one-hour build challenge. Ship a working, deployed prototype. In sixty minutes. Using Cursor and Claude.
I remember thinking: that's not possible.
And then watching a team beside me finish in forty-three.
What happened in that room wasn't just about speed. It was about a shift in how you relate to code. Up until that day, I had been — and I say this with zero shame — vibecoding. Generating, accepting, tweaking, generating again. Treating AI as a very fast autocomplete. The code shipped, sure, but I wasn't growing.
The hackathon exposed the ceiling on that approach.
The facilitators introduced a concept I hadn't heard articulated so cleanly before: agentic engineering — the practice of thinking in workflows, not lines. Instead of asking an AI to write a function, you define a system: what the agent needs to know, what tools it has access to, what a successful outcome looks like, and where you sit in the loop as the supervisor, not the typist.
The distinction they drew — and it stuck with me — was between Cursor and Claude Code as two philosophies. Cursor is the intelligent collaborator inside your IDE, human-in-the-loop at every step. Claude Code is the autonomous agent in your terminal, capable of reading, modifying, and reasoning over an entire codebase while you review rather than write. Neither is better. But understanding when to use which, and how to structure your prompts as architecture rather than requests — that's the skill.
I left with a deployed prototype, yes. But more importantly, I left with a question I've been sitting with since: Am I building with AI, or am I just letting AI build for me?
There's a version of every developer's future where they become an orchestrator — someone who designs multi-agent workflows, defines constraints, reviews outputs, and ships faster than any solo engineer ever could. That future was previewed in that room and I realised I needed to start preparing for it now.
Event 2: Nation.dev — The Uncomfortable Mirror
If the hackathon told me how to build better, Nation.dev showed me where I stood in the global picture.
And the global picture was not flattering — for any of us.
Nation.dev was a community-forward tech event focused squarely on the question that's haunting every developer right now but most of us are too proud to ask out loud: What is our place in the age of AI?
The opening speaker didn't waste time. The slide that stopped the room read something like: "The average software developer job description is being rewritten. Not next year. Now."
They weren't being paranoid. They were being precise. The data they walked us through painted a picture I had been half-aware of but hadn't confronted:
- Global demand for junior developers is compressing as AI handles increasing amounts of boilerplate and scaffolding logic.
- The developers who are thriving are those who moved up the value chain — closer to product, architecture, and business logic — while letting AI handle the mechanical layers below.
- Africa, and Kenya specifically, is at an inflection point. We have one of the fastest-growing developer communities on the continent, a young population, and genuinely world-class talent coming out of programs like Zone01, Moringa, and others. But we're also at risk of building a generation of developers who are highly skilled at a layer of abstraction that AI is rapidly commoditising. The conversation that hit hardest was about positioning. Not skills — positioning. The speaker argued that the question isn't whether you can write Go, Python, or TypeScript. The question is: what problem do you uniquely understand? An African developer who deeply understands M-Pesa integration, informal financial systems, low-bandwidth UX, or cross-border remittance flows has a competitive advantage that no model trained on Stack Overflow can replicate. Your context is your moat.
I walked out of Nation.dev slightly bruised but newly focused. I stopped thinking about my career as a list of languages and started thinking about it as a set of problems I was uniquely positioned to solve.
Event 3: Build From Here Conference — The Room Where They Told You the Truth.
Most career advice is sanitised. "Keep learning." "Build your portfolio." "Network." "Be passionate." It's not wrong. It's just not particularly useful.
Build From Here was the first event where I heard people with actual hiring power and actual war stories speak without a filter.
The lineup was stacked in a way I hadn't seen at a local event before: Google recruiters, CTOs, PMs, and founders — not as distant keynote speakers, but in a format that felt genuinely conversational. These were people who had interviewed thousands of candidates, built products from zero to scale, and made or missed critical career bets. And they were telling you exactly what they wished candidates understood.
A few things I scribbled down and haven't stopped thinking about:
On interviews:
The Google recruiters were refreshingly direct. They're not primarily looking for people who know everything. They're looking for evidence of how you think when you don't know something. The candidate who walks through their reasoning — even imperfectly — consistently outranks the one who either knows the answer cold or goes blank. Thinking out loud is a skill. Practice it.
On what companies actually look for:
One CTO put it plainly: "I can teach almost any technical skill in six months. I cannot teach curiosity, ownership, or the ability to sit with ambiguity without panicking." The traits that get you through the door are trainable. The traits that get you promoted are harder to fake. Know which you're developing.
On sneaking into the job market:
This is the part that felt almost too honest. Multiple speakers talked about the myth of the "perfect application" — that idea that you need every checkbox ticked before you apply. One founder said she'd hired some of her best engineers because they reached out directly, had done homework on the company's actual problems, and proposed a specific idea for how they could help. Cold. Unsolicited. Hired.
The lesson: the formal application pipeline is one path, not the only path. GitHub contributions to projects a company uses. Public writing about problems in their domain. A cold email with a specific, well-researched observation. These are not shortcuts — they're alternate routes that most candidates never take because they require more initiative.
On positioning yourself:
A PM who'd hired across multiple companies offered a framing I've used since: think of your resume not as a history of what you've done, but as a prediction of what you'll do next. Every line should answer the implicit question: "Why is this person the right bet for where we're going?"
Build From Here didn't give me a job. It gave me a map of how the game is actually played — and the confidence to play it intentionally rather than just hoping to get lucky.
Event 4: Africa Free Routing — Bitcoin, the Lightning Network, and Building for Your Continent
I'll be honest again: I almost skipped this one too.
"Bitcoin developer bootcamp" felt far from where I was focused. I was deep in Go backends, API design, concurrency — the usual Zone01 territory. What did I need with wallets and mining?
Everything, as it turns out.
Africa Free Routing is, in their own words, a network of lightning nodes across Africa — built by Bitcoiners who believe that the Lightning Network can do for payments in Africa what mobile money did a decade ago, but faster, cheaper, and without the gatekeeping. Their five-day developer bootcamp in Kisumu was one of the most technically dense and philosophically rich experiences I've had.
Day one: what Bitcoin actually is. Not the price. Not the hype. The protocol. How transactions are constructed, signed, and broadcast. How the blockchain actually works as a data structure. And why, in a continent where a significant percentage of the population remains unbanked or underbanked, a permissionless, programmable money layer is not an abstract concept — it's infrastructure.
The Lightning Network was where things got deeply interesting for a backend developer. The Lightning Network is Bitcoin's Layer 2 — a system of payment channels that let two parties transact off-chain at high speed and extremely low cost, settling to the main chain only when they need to. Building on Lightning means thinking about channel capacity, routing, node management, and liquidity — problems that are architecturally fascinating and genuinely unsolved at scale in Africa.The bootcamp wasn't just teaching you about Bitcoin. It was recruiting you into building the infrastructure that doesn't exist yet.
By day three, we were creating wallets, managing channels, and by day four, exploring how to build applications — payment systems, micropayment platforms, remittance tools — on top of the Lightning stack.
The insight that landed hardest wasn't technical. It was strategic. The Afrobitcoin Fellowship and organisations like Btrust Builders and Chaincode Labs are actively backing developers and enthusiasts building in the African Bitcoin space — and the talent pool is still very thin. Thin talent pool in a growing, well-funded ecosystem means opportunity. The developers who understand this infrastructure deeply, who know how to connect M-Pesa flows to Lightning channels, who can build custody solutions that work on 2G — those developers are not competing against the global market. They're building the market.
I left with a working Lightning wallet, a GitHub repo with a basic payment app skeleton, and a radically expanded sense of what "backend development" could mean.
The Thread Connecting All Four
Step back and look at these four events together, and a single story emerges:
The Cursor/Claude hackathon told me that the craft of software engineering is changing faster than most of us have admitted. The developers who survive and thrive will be the ones who learn to think in systems and workflows, not just functions and files.
Nation.dev told me that the global market is brutal and honest: AI is compressing the value of generic technical skill, and the developers who win will be the ones who combine technical ability with deep domain knowledge — particularly the kind of domain knowledge that comes from living in Africa and understanding African markets.
Build From Here gave me the tactical layer — the unfiltered view of how hiring actually works, how to position myself, and how to take the initiative instead of waiting for permission.
Africa Free Routing showed me an entire frontier — financial infrastructure, Bitcoin, the Lightning Network — where skilled developers are scarce, the problems are real, and the impact potential is enormous.
None of these insights came from a course. None of them came from a YouTube video, a Twitter thread, or a dev.to article. They came from being in a room with people who were building real things and were willing to be honest about it.
The best career guidance I've ever received didn't come from a mentor sitting across a table, telling me what to do. It came from showing up, slightly unsure, to a room full of people who were a few steps ahead — and paying attention.
Go to the event. Especially the one you almost didn't.
