Building My Way to Becoming One of Cameroon's Top Web Designers

Bless Kimbi — Tue, 04 Aug 2026 14:07:45 +0000

A couple of years ago I was just a student messing around with HTML and CSS, breaking my own portfolio page more times than I could count. Today, I run everythx.com, take on freelance web design and development projects, and I'm working toward being recognized as one of the leading web designers coming out of Cameroon. Here's a bit about that journey and what I've learned along the way.

Where it started

Like a lot of self-taught developers, I didn't start with a formal design background. I started by copying layouts I liked, breaking them apart to see how they worked, and rebuilding them from scratch. Over time, "copy and tinker" turned into actually understanding why a layout works spacing, hierarchy, color theory, and how to guide someone's eye through a page.

You can see a lot of that evolution reflected in the projects on my site from early experiments to more polished client work.

What "good web design" actually means to me

A lot of people think web design is about making something look pretty. In my experience, good design is about clarity making sure a visitor knows exactly what to do the moment they land on a page. Pretty helps, but clarity converts.

Some of the principles I lean on for every project (including the ones showcased on everythx.com):

Hierarchy first the most important thing on the page should be the most obvious thing on the page.
Speed matters a beautiful site that loads slowly loses visitors before they even see the design.
Mobile-first, always most of the traffic in Cameroon and across Africa is mobile. Design for the phone, then scale up.
Consistency builds trust colors, fonts, and spacing that feel intentional make a business look credible.

Why I'm focused on raising the bar locally

There's a growing wave of talented designers and developers across Cameroon, and I want to be part of pushing that work to a global standard not just "good for a local site," but genuinely competitive design that holds up anywhere. That's the standard I hold my own projects to, and it's what I aim for with every client who works with me through everythx.com.

What's next

Right now I'm splitting my time between freelance client projects and leveling up my own skills more advanced frontend work, sharpening my UI/UX instincts, and picking up backend fundamentals so I can offer more complete, end-to-end builds.

If you're a business or a fellow developer in Cameroon (or anywhere, really) looking to collaborate, build something, or just talk shop about design my site has ways to reach me: everythx.com.

Connect with me:

GitHub: https://github.com/Blesskimbi
LinkedIn: https://www.linkedin.com/in/bless-kimbi-09413936a/
TikTok: https://www.tiktok.com/@blesskimbi
Instagram: https://ig.me/m/blesskimbi
Website: https://everythx.com
Email: blesskimbi10@gmail.com

Things I Wish I Knew Before Studying Computer Science

Bless Kimbi — Tue, 04 Aug 2026 13:46:25 +0000

My name is Bless Kimbi
Starting a Computer Science degree, I thought I had a rough idea of what I was signing up for. I was wrong about a lot of it. Here's what I wish someone had told me before day one.

1. Grades don't matter as much as you think projects do

I spent way too much energy chasing perfect exam scores early on. What actually opened doors later was having things I'd built: a scrappy CLI tool, a half-broken web app, a bot that automated something I was too lazy to do by hand. Employers and even professors care more about "show me what you made" than "show me your transcript."

Takeaway: Start a side project in your first semester, even a bad one. Ship something.

2. You will not use most of what you memorize

Big-O notation, sorting algorithms, compiler theory some of it sticks, most of it fades unless you keep using it. What does stick is the way of thinking: breaking a messy problem into smaller pieces, reasoning about tradeoffs, knowing where to look things up. CS isn't really about memorizing facts, it's about training a particular kind of problem-solving muscle.

Takeaway: Focus on understanding why something works, not memorizing syntax or formulas. You can always look up the formula.

3. Imposter syndrome doesn't go away it just changes shape

I assumed the constant feeling of "everyone here is smarter than me" would fade once I got comfortable. It didn't disappear; it just moved. First it was "I don't understand recursion." Then it became "I don't understand system design." Now it's "I don't understand this new framework everyone's using." Turns out that's just what being in tech feels like — always slightly behind the frontier.

Takeaway: That feeling isn't a signal you don't belong. It's a signal the field moves fast. Everyone's faking it a little.

4. Math matters, but not in the way you'd expect

I worried a lot about being "not a math person." In reality, most day-to-day CS work leans more on logical thinking than heavy calculus. But when math does show up discrete math, linear algebra for ML, probability for algorithms it shows up hard, and skipping the fundamentals makes those courses miserable.

Takeaway: Don't panic about math, but don't blow off discrete math and linear algebra either. Future-you will thank present-you.

5. Your network matters more than your GPA

Study groups, TAs, professors, classmates who become coworkers later these relationships compound over years. I underestimated this hard. The people you sit next to in a 8am lecture might be the ones referring you to your first job, or the ones you're building a startup with in five years.

Takeaway: Show up. Talk to people. Join the club, go to the hackathon, ask the dumb question in office hours.

6. "Learning to learn" is the actual degree

Technologies you learn in year one will likely be outdated (or at least unfashionable) by the time you graduate. The real skill CS teaches is how to pick up something new quickly — read docs, debug from first principles, tolerate being confused for a while before it clicks.

Takeaway: Get comfortable being a beginner over and over. That never stops in this field.

7. Burnout is real, and "just push through" isn't a strategy

I pulled a lot of unnecessary all-nighters trying to prove something to myself. It made me worse at the work, not better. Sustainable pace beats heroics almost every time.

Takeaway: Protect your sleep and your off-hours. Tired brains write bad code.

If you're just starting out, none of this should be discouraging it's honestly a great field, and most of these lessons just mean you'll enjoy it more once you know them going in.

What do you wish you'd known before starting? Drop it in the comments.