Our website uses cookies to enhance your browsing experience.
Your message has been sent. We will email you at
If you haven't received our response, please do the following:
check your Spam/Junk folder and click the
"Not Spam" button for our message.
This way, you won't miss messages from our team in the future.
Our team regularly posts educational articles, describes errors in open-source projects, and makes entertaining content. So, you can find many curious and useful things there. However, aren't we going around in circles, discussing the same topics? Sometimes we need an outsider's perspective to see the big picture. If you wish, you can share what kind of articles you'd like to read on our blog.
For now, we can divide our blog content into 4 main categories:
The categorization is very rough. One and the same post can be entertaining and educational. The "60 terrible tips for a C++ developer" book is such an example.
Let's go through categories that we've discussed above. So, you can get an impression of them and maybe find something interesting.
The educational articles are mainly related to the programming languages C, C++, C#, and Java. This isn't surprising, is it? After all, we're developing the PVS-Studio analyzer to detect errors in the code in these languages.
Some of the entertaining articles are related to the bugs we've found. However, errors described in such articles are more collectables or rarities.
To popularize the static code analysis methodology, we've been checking various open-source projects and writing articles about this for years. Describing the real cases where the analyzer finds bugs, we can fully demonstrate its capabilities.
Disclaimer: a one-time use of the analyzer is wrong. It's better if developers regularly use the tool and fix errors in the development process. The earlier an error is detected, the cheaper it's to fix. We check projects one time because our goal is to demonstrate the capabilities of analyzers using PVS-Studio as an example. It's a good way to make code analyzers more known, but one-time checks don't help enhance the quality of the development process.
Here are some of the articles on this topic:
These articles are mostly related to the PVS-Studio analyzer and its development. However, you can also come across off-topic articles.
That's what we have now. What do we lack? What programming articles would you like to read on our blog?
If you have ideas for articles and want to share them with us, you're welcome in the comments. It'll be cool if they're related to the C, C++, C# languages. If there's an open-source project you'd like us to check, feel free to suggest it. Thank you!
The Show Must Go On!
0
0
0
7
0
0