Welcome! You've just started out on the path off mastery. The first step is deciding to take ownership of your growth and to begin independent study.

But... All the practice in the world won't help if you don't know what you want to learn. Before you pick a project, decide what skill(s) you want to learn in particular.

A list of a few candidates for skills considered "backend"

• software design patterns
• <any given language/web framework>
• infrastructure tools (dbs, docker, etc)
• api design
• SOA vs Monolith tradeoffs

I recommend picking a specific topic and build your project around that. Pick anything you like! It doesn't even need to seem useful - everything you learn will make you a better dev - and doing fun side projects is much more motivating than doing "homework".

As an example, here are some of my past side projects and what I learned from them:

• A terminal multiplexer for a head-mounted PC ** Rust; ANSI escape codes; async software design

• A CNN to identify Lego bricks ** keras; NN layer types;

• A Ruby gem of useful language abuses ** edgecases of the ruby language; interface design; a little FP

• A match 3 game ** Godot game engine; gdscript; ux and game design

• a python FP wheel ** Functional Programming concepts

• an LLM-based software writing agent ** LLMs - how do they work?

Each of these was targeted to help me dive into a specific area and improve my skills there.