developer-roadmap VS data-engineer-roadmap

Take off the gloves, get your hands dirty and do what you gotta do. You should be building stuff. Look at this site. Start from the top and work your way down for your chosen path.

As u/amablenderaa pointed out, taking a look at a roadmap like https://roadmap.sh which is split into different categories may be the best place to start.

link: https://roadmap.sh/

Small tasks and real goals help a lot. Check this out, https://roadmap.sh

Head over to https://roadmap.sh and checkout the frontend and backend tracks (maybe even devops if that's your thing). See if something catches your fancy and start working on it (along with DSA of course)

A community effort by the name of roadmap.sh has an exhaustive list of guides for multiple different paths into the software development world.

Should I spend my time learning more about Recursion, watch some condensed lectures on SICP 6.037 - Structure and Interpretation of Computer Programs (mit.edu) , go through this Developer Roadmaps?

Some time ago I stumbled across a roadmap on the topic of Data Engineering, that I found helpful for gathering an aggregated overview over tools and strategies.

"Jack of all, master of none" is not necessarily a bad situation. It indicates that you are capable of working with multiple technologies. If it is any help, have a look at this data engineering roadmap available on Github. This will give you a learning path should you choose to transition into data engineering.

This might be a good starting point: https://github.com/datastacktv/data-engineer-roadmap

You can have a look at the data engineering learning path shown here. IMO, following it should help you develop DE skills.