How a Payment Problem Unexpectedly Changed My Career Path in Tech

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

Sometimes the biggest turning points in a career don’t come from success.
They come from the problems you didn’t expect to face.

When I first started learning web development, the thing that fascinated me most wasn’t just the code itself.

It was the transformation.

You start with a blank page on localhost. Nothing exists yet. No layout, no colors, no interactions. Just an empty canvas.

Then slowly things begin to appear.

A navigation bar.
A section layout.
A carefully chosen color palette.

Buttons start responding. Animations begin to move. Eventually the page that once looked empty becomes a real website that someone might actually use.

That process never stopped feeling magical to me.

Because of that, I imagined a very clear path for my career.

I wanted to become a freelance web developer working with international clients from home. At this stage of my life, staying close to my family is important, so remote freelance work felt like the perfect balance.

So I prepared for that path.

I built projects.
I improved my skills.
I started reaching out to potential clients.

Eventually, conversations began happening. Some people liked my work, and collaborations started to look possible.

But then an unexpected problem kept appearing at the worst possible moment.

The payment discussion.

The Problem I Never Expected

Most international clients prefer paying through PayPal.

Normally, that wouldn’t be a problem.

Except PayPal doesn’t work in my country right now.

So the conversation often went like this:

Client: “We usually pay via PayPal.”
Me: “Unfortunately PayPal isn't available in my country.”

And suddenly the conversation became complicated.

Many clients preferred not to deal with alternative payment methods. Over time, I realized that more than 90% of potential clients relied on PayPal, and that single limitation was enough to block many collaborations before they even started.

It was frustrating, because the problem had nothing to do with my skills or the quality of my work.

It was purely logistical.

---

When Bank Transfers Became Another Obstacle

At first, I thought bank transfers could solve the problem.

Some clients were open to the idea, which gave me hope.

But when I asked my bank about receiving international transfers, the explanation wasn’t encouraging.

If the transfer exceeded around $500, the payment could easily get stuck in administrative procedures.

The bank might ask questions like:

• Where did this money come from?
• Do you have an invoice?
• Are you officially registered for this work?
• Can you provide documentation for the service?

Even after providing everything, there was still a strong chance the payment might not go through smoothly.

Trying to build a freelance career while constantly worrying about whether you will actually receive the payment is exhausting.

---

The Partial Solution That Rarely Worked

The only practical workaround I found was Upwork.

The platform allowed me to withdraw earnings in smaller amounts instead of one large transfer, which helped avoid the banking issues triggered by bigger payments.

Technically, it worked.

But in practice, another problem appeared.

Most clients I spoke with had never used Upwork before, and they simply weren’t interested in creating an account, setting up contracts, and managing payments through a platform.

For them, it felt like an unnecessary extra step.

So even when I found a possible solution, it rarely worked in real situations.

After losing several opportunities because of these complications, the frustration started building up.

That period was probably the closest I came to feeling burned out.

For a while, it made me question whether freelance development was even a realistic path for me.

---

When Writing on DEV Became My Escape

Around that time, I started writing on DEV Community.

Not because I had a strategy.

Not because I was trying to build a career from it.

I simply needed a place to release some of the frustration I was feeling.

Writing about programming, lessons I learned, and my experiences in tech became a small way to clear my mind.

At first it felt like I was just sharing thoughts into the void.

But slowly something surprising happened.

People started reading.

They left comments.
They shared their own experiences.
Sometimes they even thanked me for explaining things clearly.

Some of my articles reached over 20,000 readers, which I never expected.

That’s when I realized something unexpected:

I genuinely enjoy writing.

---

The Message That Changed Everything

The funny part is that I wasn’t even looking for writing clients.

But one day someone contacted me after reading one of my articles and asked if I would be interested in writing technical content for them.

That moment changed how I saw writing online.

Publishing articles isn’t just about sharing knowledge.

Sometimes it quietly opens doors you didn’t even know existed.

That opportunity became the beginning of my technical writing journey.

And interestingly, that first collaboration also solved a problem that had been blocking many of my earlier freelance opportunities.

The client was open to paying through Upwork.

For the first time, the payment conversation didn’t end the project before it even started.

After that experience, things slowly began to improve.

Over time, I met more clients who were open to flexible payment solutions.

Some were comfortable working through Upwork.

Others were fine sending via direct bank transfers.

Since writing an article will obviously never exceed the $500 threshold that usually triggers complications with my bank 😅, those collaborations became much easier to manage.

Because of that flexibility, I had the chance to work with some wonderful clients and build collaborations that I’m genuinely proud of.

But the reality is that the limitation hasn’t disappeared completely.

Even today, I still lose many opportunities simply because the payment conversation eventually comes back to PayPal 😥.

Still, that first writing opportunity changed something important for me.

Once things started becoming more serious, I realized that writing professionally involves much more than simply explaining technical topics.

I started learning about:

• SEO
• Content strategy
• Article structure
• Writing for both readers and search engines

Little by little, writing became more than a hobby.

It became a craft I wanted to improve.

---

Discovering an Unexpected Creative Side

One of the biggest surprises about technical writing was how creative it actually is.

When I finish writing an article, I don’t only think about the text.

I start looking at the entire experience:

• Is the story easy to follow?
• Does the structure feel natural?
• Are the images placed in the right places?
• Do the colors feel pleasant?
• Do the call-to-actions appear naturally?

Sometimes I even spend time deciding which emoji fits best in a section 😅

Because a great article isn’t only about information.

It’s also about how enjoyable it is to read.

---

But My Love for Programming Never Disappeared

Even though writing became a big part of my work, my passion for building things never disappeared.

I still love the process of turning an idea into a real website.

That’s why I also started exploring local clients inside my country.

The budgets and number of projects are obviously different compared to international freelance work, but the satisfaction of building something from scratch is still the same.

Recently, I started working on a website for a Tunisian high school, which is my first full website project with a local client.

And honestly, watching that project slowly come to life feels incredibly rewarding.

---

The DEV Challenges That Kept Me Building

The DEV community has also been a place where I continue practicing my coding skills.

From time to time, I join coding challenges just for the joy of building something creative.

So far I’ve joined the Frontend Challenge twice.

I didn’t win either of them 😅

But the experience was still incredibly positive.

The encouraging comments, the community support, and even the private messages I received after submitting my projects meant a lot.

In many ways, that encouragement felt just as valuable, if not more, than the prize itself.

If you’re curious, you can check out my submissions for the Halloween Edition challenge and the Office Edition challenge.

I’d genuinely love to hear your thoughts about them; your feedback always means a lot to me.

---

When Design Became Another Passion

Along the way I also learned Figma.

That completely changed how I approach projects.

Designing the interface before writing the first line of code makes the whole process smoother.

Sometimes I even feel like I enjoy the design phase slightly more than the coding itself.

That interest eventually led me to accept other creative work occasionally, such as:

• LinkedIn banners
• social media visuals
• small visual branding pieces

It’s a different type of work, but it taps into the same creativity that made me fall in love with web development in the first place.

---

What This Journey Taught Me

When I first imagined my career in tech, I expected a very straightforward path:

Freelance developer → international clients → remote work.

Instead, my journey looked more like this:

• Learning web development
• Losing clients because of payment limitations
• Feeling frustrated and burned out
• Starting to write on DEV just to clear my mind
• Discovering technical writing opportunities
• Working with new types of clients
• Exploring design and visual work
• Building projects locally

It wasn’t the path I originally planned.

But in many ways, it helped me discover skills and interests I might never have explored otherwise.

---

A Moment I Never Expected

Today I’ve been working as a technical writer for about a year.

And the journey has already given me moments I never expected when I started writing just to release some frustration.

At the moment I’m publishing this article, my blog on DEV has just passed 250,000 total views and 15,000 followers.

Reaching those milestones is something I could never have imagined when I wrote my first posts.

Honestly, it’s a moment when I couldn’t be prouder.

So I want to take a small moment here to say thank you to every single person who has:

• read an article
• left a comment
• shared feedback
• or simply supported my work

Whether inside the DEV community or outside it, your support has been a huge part of this journey 💙.

And it means more than you might think.

---

The Journey Is Still Ongoing

Today my work sits somewhere between several things I love:

• programming
• design
• storytelling

Each one supports the others.

Writing improves how I explain technical ideas.
Design improves how I structure content visually.
Programming keeps me connected to the craft that started everything.

The payment challenges haven’t disappeared completely.

Sometimes they still cost me opportunities.

But they also pushed me toward experiences I never expected to have.

And strangely enough…

I’m grateful for that.

Because sometimes the obstacles that seem to block your path end up leading you somewhere even more interesting.

---