Sitemap

Computer Engineering at UB

7 min readSep 28, 2026

--

Press enter or click to view image in full size

The Faculty of Engineering and Technology (FET) at the University of Buea is one of Cameroon’s top engineering institutions. Everyone knows that. What no one tells you is what it actually costs to survive there.

I’m an undergraduate in the computer engineering department, and I think someone needs to provide an honest narrative. Not the polished version you see on LinkedIn, but the real one. So here’s mine. Grab a seat.

You will learn to manage pressure, or pressure will manage you.

I was at an event once and met a guy who was one of the organizers. I told him I was a student at FET. His response landed like a badge of honor: “Oh, you’re the ones who manage pressure.” That sentence has stayed with me. Because I knew he was right.

Engineering demands that you know your priorities clearly, manage your time ruthlessly, and make hard calls about what you’re giving up every single day.

As the late Kobe Bryant once said, “Rest at the end, not in the middle.”

I didn’t fully understand that quote until I lived it at FET. I have rarely had a week where I wasn’t sacrificing one thing to show up for another. That’s just how life is here.

Some weeks felt like war. My friends jokingly often said, “Let them just kill us at once,” and we laughed it off, but the exhaustion behind that joke was very real. Projects, presentations, research, bulky assignments, submissions, exams, and meetings. Some days, you show up to campus purely because of a team meeting. Not for class. Just because the project has to work.

If you are the kind of person who needs everything to be comfortable before you perform, FET will be a tough teacher. But if you can learn to work under fire, you’ll come out the other side sharper than you went in.

I refused to be ordinary, and that cost me something.

Most students wait until their fourth year to think about internships. From my very first year, I had already set a goal: three internships before I graduated. Not because someone told me to. Because I looked at the standard path and decided it wasn’t fast enough for me.

That decision was strenuous. It was a risk. But I took it anyway.

On top of coursework, assignments, and exams, I was showing up to internship meetings, delivering tasks for people outside of school, and trying to hold everything together at once. I slept less. I became less free. There were stretches where freedom felt like a luxury I had voluntarily surrendered. But mediocrity felt worse. I was young, I was ambitious, and I wasn’t willing to wait around to become who I wanted to be.

Warren Buffett has a line that stuck with me: “Someone’s sitting in the shade today because someone planted a tree a long time ago.”

I wanted to plant early. The earlier you plant, the more shade you have later.

The advice I’d give anyone reading this: go as hard as you can, as early as you can. The cost is real, but so is the distance it puts between you and where you started.

You will learn what teamwork actually means.

Different courses came with different group projects and different groups of people. One of my teams scored a low mark because not everyone carried their weight. That hurt. But the lesson it taught me was sharper than any grade.

Leadership is not about doing the work yourself. It’s not about forcing people to do it either. It’s about making people want to do it. John Maxwell puts it well:

“A leader knows the way, goes the way, and shows the way.”

Working effectively with people is like solving a jigsaw puzzle. You need the right piece in the right place. The beautiful thing about people is that we have the capacity to become the right piece for one another.

For me, the key was finding common ground. I didn’t isolate myself from people; I created spaces where I could connect with them naturally around shared interests. That changed everything.

That low-scoring presentation also hit differently. Feeling like my fate was tied to other people’s commitment shook me. My first instinct was to protect myself by doing everything alone. But I sat with that feeling honestly and realized it leads nowhere. No man is an island. Not in life, and certainly not in engineering.

The philosophy I eventually landed on was simpler and stronger: as long as my name is on it, it cannot fail. That shift made me stop thinking of projects as things I was doing among others and start thinking of them as wholes I was responsible for. That perspective is a big part of who I am today.

You will learn how to find the point of what you’re studying.

Not every lecture at FET left me inspired. I’ll leave it at that (you know how it is). But here’s unsolicited advice for anyone in the same boat.

Get Grai Rudolf’s stories in your inbox

Join Medium for free to get updates from this writer.

The curriculum is actually well-designed and important.

The problem isn’t usually what you’re studying. It’s how you’re studying it. Richard Feynman.

One of the greatest physicists of the 20th century had a learning technique built on one simple principle: if you can’t explain something simply, you don’t understand it yet. That rule changed how I approached every course.

Look for practical applications of what you learn. Build a roadmap. Connect the dots. Ask yourself where this topic lives in the career you’re building.

Let me give an example in my context: In my sophomore year, I took a security course. At first it felt abstract, unmoored from anything real. Then I went looking. I found out exactly where and how security operates in the application layer of the TCP/IP model and how I could actually work with it. Suddenly the course had a home. It made sense. That shift in perspective made studying it feel completely different.

The material isn’t the enemy. Passive learning is.

Nobody sees what goes on under the hood.

People, my friends, my coursemates, they think I have it all figured out. I can land internships, I show up, and I keep moving. So they ask me for money sometimes, and more often, they ask me for a roadmap. How do you do it? What should I follow?

But here’s the honest answer: I don’t think we’re walking the same road.

Most of them want to be software engineers, network engineers, or telecom engineers. Building dashboards, deploying systems, and solving local infrastructure problems. That’s real, important work. But it’s not mine. I’m tired of that lane. My goal is not to solve problems within my community’s current reach. I want to contribute to the global research frontiers of the world. I want to create the biggest impact I possibly can. That’s a different ambition, and it demands a different path. Perhaps become the next Geoffrey Hinton, Fei-Fei Li, Andrej Karpathy, etc.; the list goes on.. Not just because I want to, but because I want to.

I’m tired of sailing my little boat

Far inside of the harbor bar;

I want to be out where the big ships float —

Out on the deep where the Great Ones are!

And should my frail craft prove too slight

For storms that sweep those wide seas o’er,

Better go down in the stirring fight

Than drowse to death by the sheltered shore!

— Daisy Rinehart

Some people have even told me that’s not what Cameroon needs right now. I understand why they say it. But here’s something I’ve observed: brilliant solutions exist everywhere around us. Genuinely great ideas, great products. And yet people don’t use them. Innovation that should be working just isn’t landing. Why?

Because building something useful and convincing people they need it are two entirely different skills. As Robert Cialdini writes in Influence, people don’t just act on what is good for them. They act on what feels right to them. You have to build from the perspective of what people will reach for instinctively, not just what solves their problem on paper. Make them feel like they cannot exist without what you’ve built. That’s the gap between a great idea and a product that actually moves. A lesson I’m still learning.

As for the roadmap requests, I can’t give anyone a blueprint to follow. But I can tell you what I think you should do.

Stop looking for a map. Start identifying a goal.

Not a vague wish. A real, specific ambition sitting somewhere in the distant future. Then connect it backwards to today. What does that future require? What does the person who gets there look like, and what are they doing right now?

Then, and this is the part most people skip, develop a creed around that goal. Not just a to-do list, not a vision board. A creed. A set of convictions you return to when things get hard, when people question your path, and when you feel like you’re falling behind. Your creed is what keeps you oriented when the road disappears. Mine has kept me going through nights I don’t write about publicly.

The goal I have isn’t just an ambition anymore. It has become an apprehension, something I can almost reach out and touch. That shift changes how you operate. You stop asking what’s possible and start asking what’s required.

I can’t complain about having too much on my plate. My goal was to eat.

This is still a work in progress, much like the person writing it. More to come.

--

--

Grai Rudolf
Grai Rudolf

Written by Grai Rudolf

Disciple of Jesus Christ, Software Engineer & AI Researcher