Remembering when people who knew shit wrote guides online for people trying to learn to code called:
"Learn python the hard way"
And sure there's some performative nonsense in there. Programming isn't "hard" in some inaccessible sense. Hardship isn't the only route to building skills. But you do need some challenges and productive friction to get your brain engaged with independently problem solving not just borrowing answers
[language] for dummies would tell you how different common language features worked but it wouldn't get people to the point of being able to write their own programs even a lot of the time because it's so busy trying to be so accessible it's not engaging the learner in solving their own problems.
Programming languages are so easy that once you've learned a few a new one usually takes a few weeks to get a working grasp of. They're not intrinsically hard.
But that's like saying bike racing isn't so difficult you just got to get out and ride every day and practice racing craft.
If people don't set out to actually do it, explaining how it works in a book or whatever is not enough on its own to build that skill.
Friction matters.
And the whole point was that there's a lot of "python for dummies" stuff that did not explain how programming works, whereas creating a series of problems that people wrestle with inherently helps build the kind of problem solving mindset that gets you to being a competent expert.