There’s a million frameworks to choose from. For learning purposes I would say build a full stack todo list app using the least amount of frameworks and tooling as possible. Vanilla.js a nodejs backend and mongodb. Then rewrite it using different tools and technologies. Different UI frameworks, different backends like dotnet and sql server. Make notes of all the new terminology, design patterns etc and use chatgpt to speed run your education. More on reddit.com

OP lets flip this. You are a construction engineer, now that could be anywhere from an architect to brick layer and everything in between. There are dozens of roles and different skills in construction and its like a matrix of those skills and roles to make successfull construction. Bi is exactly the same with (up for debate) 5-10 roles and 5(ish) distinct skills. Then it depends on what you are building. A full stack dev is the equivelent to a home self builder, usually working for a small to mid size company or a large company (who don't know what they are doing). In larger companies all the way up to global organisations you have more separating of those roles just like in construction. If you are building a skyscraper you need specialist. What is it the most valuable BI skill? Where should you start? Id argue you already have a very valuable skill in BI which is construction engineer(or any other specialist real world domain knowledge). You know what is important and what construction engineers need to see and how to present it to make good decisions. So if i was you I would concentrate on the report visualisation/end user end of BI and use your previous career. Then work outwards into the data storage/ETL world. More on reddit.com

You're missing the backend (database) stuff. More on reddit.com

Imo full stack doesn't necessarily have any work/life implications. I work currenty in a full stack role and it just means that some days I'll work on frontend tasks, some days I'll work on backend tasks and some days I'll work on server/orchestration tasks. Its not like I need to do multiple people's work in a day. The pro of this way way on a personal level is there is a lot of variety so it's harder to get bored. The con is that you probably won't reach the level of expertise as someone doing just one thing (thought it happens). From an organisation point of view full stack Devs are super useful because work generally doesn't break down equally across the stack for any given deliverable, so some days there will be more frontend and others more backend. Having people who can switch roles avoids hotspots in the team's workload (e.g. frontend Devs overloaded and backend getting bored). More on reddit.com