Yes, absolutely. Particularly early on, there are a lot of minor hurdles that you won't have a clue about. Silly things like versions not matching, missing semi

Yes, absolutely. Particularly early on, there are a lot of minor hurdles that you won't have a clue about. Silly things like versions not matching, missing semicolons, documentation that is outdated. These are all things that have you tearing your hair out if you're new to it. One problem is the idea that you've ever "learned to program". It creates an expectation that you'll know whatever it is that you need. In reality, I've never coded anything where I knew everything about what to do. It's all an exploration: learning git, learning how to compile c++, learning how to deploy things in containers. There's always a new piece to learn about, and that's the real skill. It's both intellectual and psychological: you need to be smart, and you have to force yourself to learn things. The problem with being new at anything is you don't have the map. There's a bunch of terms describing your space, but you don't know which ones are important. You can google anything, but you don't know what to google. When you get dropped into a working team, you at least end up with something that works, and people who can tell you how they think about it.