DEV Community: Chesea

Who Is Chesea Dev? (Etengwe Chesea)

Chesea — Fri, 24 Jul 2026 10:26:45 +0000

Who Is Chesea Dev? (Etengwe Chesea)

If you searched for "Chesea Dev" or "Etengwe Chesea" and landed here, here's the full picture.

My name is Etengwe Chesea. Online, I go by Chase, and my brand across YouTube, blogs, and freelance platforms is Chesea Dev.

I'm a self-taught web developer based in Buea, Cameroon, working primarily with PHP/Laravel and MySQL. I didn't come into development through a formal program or a bootcamp. I came in the long way, through tutorials, trial and error, broken projects, and a lot of late nights figuring things out on my own.

I'm building both the practical, self-taught side of my skills and the formal, structured side at the same time.

What I Actually Do

I work as a freelance web developer, taking on projects through Fiverr, Upwork, and referrals from people I've worked with before. My focus is on building functional, well-structured websites for real businesses, not just polished-looking templates.

I'm especially interested in working with startups and small businesses that are just getting off the ground. Early-stage businesses usually can't afford to get their website wrong, they need something fast, built around their actual audience, and structured to convert visitors into customers from day one. That's the kind of work I enjoy most: sitting down with a founder, understanding what their business actually needs, and building a site meant to grow with them rather than just look good in a screenshot.

One of my main projects is ZeevoNet (zeevonet.com), a Cameroon-focused services and jobs marketplace I've been building and rebuilding on a full PHP/MySQL stack. It's meant to solve a very specific, local problem: a lot of useful information, job openings, services, listings, currently lives scattered across WhatsApp groups and personal networks instead of being organized somewhere searchable. ZeevoNet is my attempt at fixing that.

Content and Teaching

I also run a YouTube channel (@cheseadev) focused on web development tutorials, and I write blog posts on Medium, LinkedIn, and Dev.to, mostly about web development, freelancing, consistency, and the honest realities of building a skill and a business from very little.

I don't sugarcoat the process in my content. A lot of what I write about comes directly from what I'm living through: working with limited resources, juggling multiple income paths at once, and figuring things out without a team or mentor standing over my shoulder.

Why I Build the Way I Do

I'm motivated less by finding a conventional job and more by building systems that scale, whether that's a platform like ZeevoNet, a freelance business, or a body of content that helps other developers avoid mistakes I had to learn the hard way.

If you're a business owner looking for a developer who understands both the technical and business side of a website, a fellow developer looking for real, unfiltered lessons from someone building in public, or you just came across my name somewhere and got curious, that's who Chesea Dev is.

Feel free to look through the rest of what I've written, or reach out if you're looking to work together.

The Information Isn't Missing. It's Just Trapped in WhatsApp Groups

Chesea — Fri, 24 Jul 2026 09:35:05 +0000

**
**, and I don't know if it's just here or across a lot of places like it. Most young people carry a smartphone every single day, but for most of them, that phone is used almost entirely for entertainment and social media. Rarely anything more.

That same phone can check the weather before someone leaves the house. It can give directions to a place they've never been. It can teach them how to do almost anything, step by step, for free, through YouTube and other content online. It can even help them find a job.

But instead, what actually happens is someone posts in a WhatsApp group asking if anyone knows of a job opening, or a house for rent, or where to find a particular service. And someone replies, if they're lucky, based on whatever they personally happen to know.

The information isn't missing. It's just trapped in personal networks instead of being searchable by anyone who needs it.

As developers, we don't always sit with that. We build platforms assuming people will show up and use them because the platform exists and it solves a real problem. But existing and being used are two very different things.

I learned this firsthand. I built ZeevoNet, a free platform meant to organize exactly this kind of information for people in my area, jobs, services, listings, the things people are currently asking about in WhatsApp groups one message at a time. It's free. It solves a real, specific problem.

And almost no one uses it yet.

Not because it doesn't work. Because awareness doesn't build itself just because a solution exists. People don't wake up one day and think to check a website for something they've always solved by asking a friend. That habit has to be built, and building it is a completely different job from building the platform itself.

This is the part that gets skipped in most conversations about "bridging the digital divide." It's treated like an access problem, like people just need phones and data and the rest solves itself. But access was never really the missing piece. The habit of turning to structured, searchable information instead of word-of-mouth is the actual gap, and no one's phone teaches them that on its own.

So if you're a developer building something meant to genuinely help people, especially in a market like this one, know that shipping the platform is maybe half the work. The other half is showing up in the same spaces where the WhatsApp groups already live, and consistently proving, in small, real ways, that there's a faster, better way to get the same answer.

Free doesn't automatically mean found. Useful doesn't automatically mean used.

Somebody still has to bridge that gap, one visible proof at a time.

A Website Won't Make You Money by Itself

Chesea — Thu, 23 Jul 2026 10:54:28 +0000

A Website Won't Make You Money by Itself. Here's What Actually Will.

A lot of business owners get a website built and quietly expect it to work like magic. Launch it, and somehow revenue jumps 2000% in the first month. It's a nice dream. It's just not how it works.

A website makes money when it's built with intention, not just built. That difference comes down to a handful of decisions most business owners never see happening behind the scenes, and a partnership most of them don't realize they're supposed to be part of.

It Starts With Who You're Actually Talking To

Before a single line of code gets written, a good developer figures out your niche and your audience. Who is this website actually for? What are they searching for? What convinces them to trust a business enough to buy from it? The quality of the design, the tone of the content, even the structure of the pages, all of it should be built around answering those questions, not just built to look nice.

Building It Is Only Half the Job

Here's something a lot of business owners misunderstand: they assume the developer just handles everything alone, and once the site is live, the job is done. In reality, a website that performs is a 50/50 collaboration.

The business owner brings the industry knowledge. What makes your customers buy. What your competitors are missing. What your business actually stands for.

The developer brings the technical execution. Researching what your audience is searching for, choosing the right keywords, structuring the site so it actually gets found, and hosting it properly.

Neither side can do this well alone. A developer without your business insight is guessing. A business owner without technical execution has a nice-looking site that nobody finds.

The Work Doesn't Stop at Hosting

Once the site is live, the job still isn't finished. A properly set up website gets connected to your social media platforms and your Google Business Profile, so customers can find and verify you no matter where they come across your brand first. This is what separates a website that just exists from one that actively works for you in the market.

What This Actually Gets You

Do this correctly, and you're not just another business with a website. You're standing among the businesses in your niche that are actually converting that visibility into revenue. A well-built, well-connected website should reasonably return several times more value than what was spent building it, not overnight, but over time, as it keeps working in the background while you run your business.

And Then Innovation Has to Continue

Nothing in business stays still, and websites are no exception. The businesses that stay near the top of their market are the ones who keep refining their site as their audience, competitors, and industry evolve. That might mean hiring the same developer back periodically, or keeping one on retainer, to keep the site sharp instead of letting it quietly go stale while competitors catch up.

The Bottom Line

A website isn't a lottery ticket. It's a tool. And like any tool, its value depends entirely on how well it's built, how well it's maintained, and how closely the business and the developer actually work together to use it.

Get that partnership right, and a website stops being an expense on your books. It becomes one of the best-performing investments your business makes.

The Giving Up Nobody Notices....

Chesea — Wed, 22 Jul 2026 05:57:57 +0000

The Giving Up Nobody Notices
In my last post, I talked about what real consistency actually looks like, not a perfect calendar, just someone who keeps returning to the work. This post is about the opposite process. The one that happens in reverse, so slowly that most people don't realize it's happening until it's already done.
Most people think giving up is a single moment. You wake up one day and say "I quit."
I don't think that's how it usually happens. I think that's some of the reason a lot of us stay stuck. Because we give up without ever noticing we did.
Here's what giving up actually looks like.
You used to spend real time on your skill every single day. Then, one day, you catch yourself thinking it's impossible to start again. That thought shows up quietly. It doesn't announce itself as "giving up." It just feels like being tired, or busy, or realistic.
Even when you see someone else succeeding at the exact thing you paused on, it still doesn't pull you back in. You'd think seeing proof it works would be motivating. Sometimes it isn't. Sometimes it just confirms the story that they made it and you didn't, so why try again.
That thought is the actual mechanism. Not a dramatic breakdown. Just a quiet decision to not start again today.
And it moves in stages. You go from working on your skill every day, to five times a week, without really deciding to. Then four times. Then twice. Then once a week. At some point, "once a week" quietly becomes "whenever I feel like it," which quietly becomes "not really anymore."
Nobody sends an announcement. There's no final day marked on a calendar. Just a slow fade that only looks obvious in hindsight.
The good news is that the process runs in reverse too. The same way people fade from daily to nothing, you can build the opposite. Once a week becomes twice. Twice becomes four times. Four times becomes every day. And at some point, showing up stops being a decision you have to make and just becomes who you are.
That's really the whole difference between people who make it in web dev, or any skill, and people who don't. It's rarely one dramatic moment of quitting or one dramatic moment of breaking through. It's a thousand small, quiet choices, the kind that don't feel significant on the day you make them.
If you're in that quiet fade right now, the version where you haven't officially quit but you also haven't shown up in a while, that's not a life sentence. It's just the reverse staircase. And you can start climbing it the same way you came down. One small step, not the whole flight at once.

Consistency Doesn't Look Like a Marked Calendar

Chesea — Tue, 21 Jul 2026 22:38:00 +0000

Consistency Doesn't Look Like a Marked Calendar (Part 2)

If you've read my last post about why most people quit in week one, this is the part that comes after. Because surviving week one isn't the finish line. It's just the entry fee. What comes after is the part nobody shows you either.
Consistency isn't what you see on TV. It isn't a calendar with a neat checkmark on it every single day, same time, same energy, like life politely steps aside while you build your dream.
Life doesn't exist like that. Life just exists, right in the middle of everything you're trying to build.
Here's my version of it.
My wake-up call was forex. I started watching tutorials, lifestyle videos, motivational content, and something in me thought, "this could actually change my life." So I started. Most days, trading, studying charts, trying to understand a market that owes you nothing.
I didn't even have data half the time. I was doing this on a broken Samsung S8 back in October 2023. No perfect setup. No perfect conditions. Just a feeling that I had to put in the effort anyway.
Weeks passed. Months passed. I got into university. New lifestyle, new environment, new pressure. And in the middle of adjusting to all of that, I started web development too. Still broke. Still consuming every bit of content I could find. Still trying to get good.
But things weren't as smooth as I'd imagined.
Forex needed more time than I had. Web dev needed more time than I had. And getting clients wasn't easy either, so I added content creation on top of both, mostly to build a portfolio and a presence. That's three things now, each demanding its own hours, its own learning, its own bulk of information to absorb.
Doing this alone makes it heavier. There's no one clocking in beside you. But the alternative, thinking there's no way forward, isn't really an alternative. So I kept learning. Every day, in some form.
What I'm not sure of, even after three years plus of doing this, is showing up exactly the same way every single day. Some days it's depression. Some days it's life. Relationships, responsibilities, just being a person with a full life outside of code and charts.
I can't do it all, all day, every day. I don't think anyone actually can, no matter what their calendar looks like from the outside.
But I make sure I do something toward it at least once a day. High hopes, sure. But realistic ones.
That's what consistency has actually looked like for me. Not a perfect streak. A person who kept returning to the work, even on days the work didn't return the favor.
If you want to understand how people lose that return-to-the-work habit without even noticing, that's exactly what I get into next, in "The Giving Up Nobody Notices."

Nobody Tells You What the First Week Actually Looks Like (part 1)

Chesea — Tue, 21 Jul 2026 18:27:00 +0000

Nobody Tells You What the First Week Actually Looks Like

Everyone online tells you the same thing.

"Find a skill. Stay locked in. Be consistent."

It sounds simple. It sounds like all you need is willpower and a plan.

But almost nobody tells you what the process actually looks like on the inside. What it feels like on day 4. What it feels like when the motivation that got you started is suddenly gone and all that's left is the decision to show up anyway.

So here's what usually happens instead.

You plan for three months. You tell yourself this time is different. You get excited, you set the schedule, you tell people about it.

Then week one happens.

And somewhere in that first week, the energy drops. The thing that felt exciting on day one feels like a chore by day five. You show up less. You skip a day. Then another.

And here's the part nobody warns you about: that drop isn't a character flaw. It's biology.

Humans, like every living thing, don't change habits or environments instantly. Adjustment takes time. A new routine is, to your body and mind, a disruption. Resistance in the first stretch isn't proof that you're weak or unfit for the goal. It's just what change feels like before it becomes familiar.

But when nobody tells you that, you interpret it differently.

You think: "I only lasted a week. I must not be built for this."

You think: "Other people can do this. Why can't I."

You think: "No one can help me here. No one shares my exact dream, so no one can carry this with me."

That thought is where things get heavy. Tiredness plus that kind of isolation is a hard combination to sit with. It's the place where people don't just abandon a habit, they start doubting themselves altogether.

All because they were never given the information clearly in the first place.

They were told what to do. Nobody told them what it would cost, what it would feel like, or that the hard part was expected, not a sign of failure.

If someone had said "the first two to three weeks will feel like fighting your own instincts, and that's normal, not a red flag," a lot of people wouldn't quit. They'd expect the resistance instead of being blindsided by it.

So if you're in that stretch right now. If you started something three weeks ago, or three days ago, and it already feels heavier than you expected.

That's not proof you picked the wrong path.

That's just what week one of change usually feels like for every human being who has ever tried to become someone new.

The people who make it aren't the ones who never feel this. They're the ones who were told, or figured out, that this part passes.

You're allowed to be tired. You're allowed to have a rough week.

What you're not allowed to do is let a rough week convince you of a permanent story about who you are.

Because you got tired. Not because you're incapable.

Keep going. The information was just missing. Now it isn't.

Where Do People Get This From?

Chesea — Mon, 20 Jul 2026 16:11:53 +0000

Where Do People Get This From?

A few nights ago, I wrote a blog post.

The idea was simple: web development isn't dying, it's growing. I posted it on Dev.to, Medium, and LinkedIn, feeling pretty good about it.

Then, that same night, I came across another blog post.

Same topic. Same core idea.

But the way it was written, the way it painted the picture, the way it explained things... it was far better than mine.

I sat there for a moment just staring at the screen thinking, "Where do people get this from?"

This idea. This way of seeing things. This way of putting sentences together so they actually land.

I honestly don't remember the person's name anymore. I think it was on LinkedIn. But I remember exactly how I felt reading it.

Amazed. And a little embarrassed, if I'm honest.

Not because my post was bad. But because theirs made mine look like a rough draft.

My first instinct was to compare. To wonder if I even had anything worth saying if someone else could say it that much better.

But then I sat with it a bit longer, and a different thought showed up.

That person didn't wake up writing like that.

Somewhere behind that one blog post is a pile of other posts nobody ever saw. Drafts that got deleted. Ideas that didn't land. Years of reading, writing, rewriting, and probably getting told their early stuff wasn't great either.

What I saw was the output. I didn't see the process.

And that's the part that's easy to forget when you're the one still early in yours.

Time does something writing tips can't teach you. So does consistency. You can read every "how to write better" article on the internet, but at some point, the only thing that actually improves your writing is writing. A lot of it. Over and over. Badly, at first.

The same thing is true for code. For design. For basically any craft I can think of.

The developer whose code looks effortless wrote a lot of broken code first. The designer whose layouts feel obvious spent years making cluttered ones. The person whose blog post painted a picture so clearly probably has a folder full of posts that didn't.

So here's what I took from that night.

Instead of asking "why can't I write like that yet," I started asking "what would it take for me to write like that eventually."

And the honest answer is: time, reps, and not quitting when my own stuff feels average compared to someone else's.

That's really it. There's no shortcut hiding somewhere that they found and I haven't.

So if you're building something, whether it's writing, code, design, or anything else, and you come across someone doing it better than you right now, let it inspire you instead of discourage you.

They were where you are once too.

You're just seeing them a few thousand hours ahead of you.

Keep writing. Keep building. Keep showing up.

The gap closes slower than you want, but it does close.

Too Many Web Developers? Look Again.

Chesea — Mon, 20 Jul 2026 08:15:03 +0000

You Think There Are Too Many Web Developers? Look Again.

Sometimes, when you're learning web development, it's easy to look around and feel like you're already too late.

You go on platforms like Fiverr, Upwork, and other freelance marketplaces, and you see thousands of developers offering the same services you're trying to offer.

WordPress developers. Frontend developers. Backend developers. Full-stack developers.

And you start thinking:

"Why would anyone choose me?"

"There are already so many developers out there."

"Maybe I'm not good enough."

But here's something I realized recently.

Have you actually taken the time to browse through the websites that are already on the internet?

I mean really browse them.

Not just visit the big websites everyone knows, but visit websites belonging to regular businesses, organizations, stores, and individuals.

I did this for about 30 minutes, and honestly, it changed my perspective.

I came across only a handful of websites that I would genuinely describe as well-structured. Websites that presented useful and accurate information, had a clear purpose, loaded properly, and made it easy to understand what the business actually wanted you to do.

But many of the others had problems.

Some had way too much information crammed onto the landing page.

Some had very little useful information.

Some made it difficult to find the right call-to-action.

Some weren't organized properly.

And some simply didn't feel like they were designed with the user in mind.

That's when I realized something.

There is still a lot of room for good web developers.

The fact that there are thousands of developers doesn't mean there are thousands of developers who can consistently build great websites.

And this isn't me saying I'm already one of the best. I'm not.

I still have a lot to learn.

But I also know that the websites I build today are much better than the ones I built when I was just starting out.

And that's the important part.

I've improved.

I've built websites before that I wouldn't be proud of today. But that's okay. Those websites were part of the process.

Because web development isn't something you master once and then you're done.

You learn.

You build.

You make mistakes.

You look at what you built six months ago and realize you can do it better now.

Then you learn something new and improve again.

That's how you become better.

I think some people stop growing because, at some point, they convince themselves they've reached the maximum level.

They think they already know everything they need to know.

But technology doesn't stop changing.

The internet doesn't stop evolving.

And your clients' expectations don't stop changing either.

The moment you stop learning is the moment you start falling behind.

So, if you're a developer, designer, marketer, writer, entrepreneur, or you're doing anything else you care about, don't spend all your time looking at how many people are doing the same thing as you.

Instead, ask yourself:

"How good can I become?"

Because the goal shouldn't just be to enter the field.

The goal should be to become exceptionally good at what you do.

There is a concept I like to think about: the 1% of the 1%.

The idea isn't that you need to become better than everyone overnight.

It's about constantly pushing yourself to improve until you become someone who is exceptionally good at their craft.

You don't get there by comparing yourself to everyone else.

You get there by practicing.

By learning.

By building.

By studying what works.

By looking at your old work and asking how you can make it better.

So yes, there are a lot of web developers in the world.

But there are still businesses that need better websites.

There are still websites that need to be built.

There are still problems that need to be solved.

And there will always be room for people who are willing to keep improving.

So don't let the competition discourage you.

Keep learning.

Keep building.

Keep practicing.

And whatever you do, don't aim to simply be "good enough."

Aim to become one of the best you can possibly be.

**Because the real competition isn't everyone else.

It's the version of you that existed yesterday.******