1 The more code you write the better your code will be. Having an inexperienced C/C++ programmer's code running in production environments is likely to result in memory access violations of all kinds.
2 There are many safeguards that you as the programmer can employ to protect your product from yourself. The most effective one is using your brain. If you notice that you tend to have access violations around loops or memcpy/memcmp operations then triple check those regions of your code. Once after writing it and twice on two different days a week after writing it.
3 The problem isn't the language. The problem is people's egos and their unwavering confidence in developing something that they aren't qualified to develop. If it's your first time writing code to complete a specific task then you aren't qualified.
4 You must be willing to write code that you are willing to throw away just for the practice to gain a greater understanding of the scope of your goal. You must also be willing to completely rewrite/re-architect your initial attempt as your initial implementation is likely lacking the foresight for specific implementation details that can be done in a better way. If you aren't willing to do what I mentioned previously. You are likely one of the many bad programmers/engineers.
5 It's astounding how people lack the common sense that the tool cannot make you better at your job if you are bad at the job in the first place. It can only amplify how bad or good you are at your job. If you don't agree then you better be able to use a scalpel better than a surgeon otherwise we may need to deem scalpels too unsafe to be used.