I get your point @isaqueprofeta
What I describe is a workflow that I have found most efficient and most fun. Mediocrity in outcome and lack of wisdom is not an endpoint that I recognise. But maybe there is a price to pay for edgy, impatience, who knows. There are so many other places than devops where I want and need to invest clock cycles.
I like a fast to working system and then pick around and learn organically. Play and poke the system from within. And yes swap frameworks entirely when required but with a live working reference, that being my traditional comfort zone. (Maybe one day a more scholarly approach might work better for me, who knows?)
PS Testing iterations based on assumptions is a way to test with more certainty if you have it right or not. This has been my experience. It is partly because I often find documentation difficult to interpret and ambiguous. My issue.
/rant
I am now going to dive into your links and see if I can play puppeteer and bring something up. Exciting.
Thanks friend.
E