Published on

When Your Motivation Burns Out as a Frontend Engineer

Authors
  • avatar
    Name
    Laksmita Widya Astuti
    Twitter

The Everyday FE Grind

Here is what frontend folks juggle every day:

  • Kick-off meetings to understand the project
  • Requirements and design walkthroughs with PMs, BAs, and designers
  • Design reviews
  • API contract definitions with the backend team
  • Development, testing, deployment, delivery, and maintenance

But here is the thing. Most of the time, FE has zero visibility into the deployment part. We do not understand the cloud dictionary. Docker? Kubernetes? AWS? Might as well be speaking another language.


The Junior Dev Trap

When I was running as a junior dev, I understood my role clearly: focus on code, understand the stacks. That was it.

But as I grew into a mid-level position, I realized code alone is not enough. And here is the frustrating part: no one gives you a chance to see how Docker, Kubernetes, AWS, or cloud stuff actually works from scratch.

The situation usually looks like this:

  • Your system is super secure
  • No playground or sandbox account available
  • No clear direction to follow
  • FE and QA teams have no idea how your apps get delivered into the client's hands

The Real Impact

When an incident happens during deployment? No one can help. Especially when leadership, or seniors take leave.

What can you do in that situation? Nothing. Your motivation burns out because you start feeling like an impostor.

The knowledge gap is not just a personal problem. It becomes a team problem the moment something goes wrong in production.


The Turning Point

Until someday, you find a someone that actually helps you grow.

They give you an admin account. They tell you: "Do whatever you want in the playground account."

And the result?

  • Overwhelming pressure? Yes.
  • Stressful? Definitely.
  • The learning gap is huge.

But someone gives you trust to use the tools without treating you like a security risk. You learn how to:

  • Drop data in the database
  • Patch records
  • Create your own deployment stacks
  • Destroy them and rebuild from scratch

Getting Your Motivation Back

At the end of it all, your motivation as a FE comes back. You learn the system development as a whole. You get trusted.

In API contract discussions, you can actually contribute ideas because you understand what the team wants to achieve. At least you understand a bit of the technical stuff they are talking about without feeling completely lost.


The Lesson

Trust unlocks growth.

When someone treats engineers like they cannot be trusted with production-like environments, they are not protecting their systems. They are killing motivation and creating knowledge gaps that hurt everyone when things go wrong.

Give people a sandbox. Let them break things in a safe space. Watch them grow.


Disclaimer: Please don't take this too seriously. This is just my own reflection. When that time comes, it'll be my turn to give people a safe space to grow if I were in their shoes 😅

And to my fellow FEs still struggling with "what even is a pod in Kubernetes?", we're all gonna make it. One day we'll confidently talk about containers and everyone will think we know what we're doing. Fake it till you make it, right?