Anything beyond this is usually a play to trap you into an ecosystem. No reason to adopt any of these frameworks, especially if you already have a mature workflow system.

This is why an org should have skip-levels. You can't put anyone on an island with that kind of unchecked authority and expect good results.

Back in early 2000s, before hackerrank and similar coding sites, this is what my professors recommended for training programming skills.

Given that this space is so rapidly evolving, these kinds of posts are helpful just to make sure you aren't missing anything big. I've caught myself doing something the hard way after reading one of these. In this case, the framing is basically man pages for CLIs was a helpful description of sills that gives me some ideas about how to improve interaction with an in-house CLI my co. uses.

As a technologist, you should always avoid MS. Even if they have a best-in-class solution for some domain, they will use that to leverage you into their absolute worst-in-class ecosystem.