Yes, though there's a lot more detail to it than "just trying", mostly about good ways to get there: shortening the feedback cycle of improvement through peer feedback, getting past the fear of failure by lowering the cost of mistakes through blameless review. And that "being smart" is the wrong criterion, which I think is the "growth mindset".
I really wanted to like this essay but I'm having a hard time with the fact that it basically overlooks how important feedback style is to mindset. The sixth paragraph in particular struck me as full of fixed-mindset thinking.
I think it better to believe oneself junior, but competent for that level, than an incompetent senior.
A slow ease into unfamiliar tasks, with initial supervision from someone already familiar, is what might be best practise, but given current demand for programmers, is often not what you end up in. "Hit the ground running" can be the euphemism...
It's the shift from a fixed mindset to a growth mindset a la Carole Dweck. That is quite a tough shift to make however when you've been conditioned with lots of feedback from school and university telling you are good and then suddenly that feedback disappears when you start work. Indeed I imagine most programmers aren't actually especially good when they first start - certainly if I looked back at the code I wrote 10+ years ago, I'm sure I would cringe.