Lack of challenges

Lack of challenges

Lack of challenges

Does work have to be challenging?

No one likes to do mundane tasks. An ideal task is somewhat challenging and/or includes room for creativity. But really, does it have to be this way? What if it's not?

To expand your skillset and to grow in your career, it is important to constantly challenge yourself with stuff you've never done before. You will stagnate if you keep on doing the same kind of work over and over again without challenging yourself much. When you have the option, it is better for your personal growth to take up a more challenging project.

But what if you either can't or don't want to switch to a different project right now just for the sake of being challenged? How do you keep work interesting?

One thing we need to keep in mind as developers is that we don't build things for ourselves, we build things for users. This applies to both indie developers and big companies. Sure, you might want to use that trending new framework that you always wanted to try. But if the problem you are solving is better off with using the tech that you find boring, you have to use the boring stuff.

We don't want to end up in a state where we lose our productivity if the work we are doing is not challenging enough. Making an Electron app with React and MST is in no way challenging for me, but I still want to deliver an awesome piece of software that will solve users' problems. Even if I'm working on the same tech stack since 4 years, I want don't want this fact to hinder my ability to deliver awesome software.


  • Try to find challenges in other projects to quench your thirst for adventures. Learn a skill in parallel in order to keep things exciting, and use that excitement to fuel the not-so-exiting projects.
  • Gamify your workflow