When you create software, you have a lot of documentation that you have to read. There is just no way to get around it. If you want to be a professional developer being able to code is just part of the job requirements. There is a lot more that you have to do and doing a lot reading is one of them. You should be able to get to know your platform in and out over time and the only way that you can do that is by reading the documentation that comes with it. You can either do that or by reading several books about the proposed subject. Sure you might be able to gain a lot of your education through blog post but you will never gain enough knowledge where you could call it “definitive”.
The documents that you have to read are spread out both over the language that you use and the technology that you work with. So you should read both of them. You want to be able to master both as much as possible. And one of the main documentation that you want to read is the security guide that most professional languages and platforms have.
When you are dealing with a language or a platform, security is essential. So to make sure that you are secured, the developers of both of these important tools make sure that there are usually good professional practices that you can follow. Well this is true for most professional languages and platforms that are out there. Sometimes you are dealing with a newer language that does not have these devices in place. That is why you rarely want to go with a language or platform that does not have much real life professional use. You do not want to chart the course for other developers when it comes to an area like security. This means that you will be the one that is attacked first.
When you are dealing with a platform such as IOS, Android, Windows, Linux, OS X and others, you will always have different aspects of each that you have to worry about. None of these platforms do jobs just the same way as the others. So you have to realize how each one is done and how you can do it in the most secure way possible. This is where security document on that specific platform really comes in handy.
When you are dealing with a language then you have to take into account what the main domain of that language really is. While a lot of languages out there are able to go into several different domains, they are still usually better at one domain than the other. For example, if you are dealing with a language like PHP then you know that you are dealing with the web domain. So now you also know that most of the security practices that a security guide would tell you is going to be about protecting yourself from the web. But with a language like Python, you are dealing with both the web and the desktop. So the security guide might be about both or you might have to look in the library documentation for certain security information. For example if you use DJango the information on the best security practices will be included in it and not the main Python documentation.
Overall it is very important that you read the security documentation to both the platform that you are using and the language that you are using. It will help you become a better developer in the end.