# What C\+\+, C\# or Java article would you like to read on our blog? 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\. ![1082_articles/image1.png](https://import.viva64.com/docx/blog/1082_articles/image1.png) For now, we can divide our blog content into 4 main categories: 1. educational articles 1. infotainment articles 1. checks of open\-source projects 1. other\. The categorization is very rough\. One and the same post can be entertaining and educational\. The "[60 terrible tips for a C\+\+ developer](https://pvs-studio.com/en/blog/posts/cpp/1053/)" 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\. ## Educational articles ![1082_articles/image2.png](https://import.viva64.com/docx/blog/1082_articles/image2.png) 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\. 1. [What's new in C\#12: review](https://pvs-studio.com/en/blog/posts/csharp/1074/) 1. [Common patterns of typos in programming](https://pvs-studio.com/en/blog/posts/cpp/1064/) 1. [Does C\# always have boxing with string concatenation and interpolation?](https://pvs-studio.com/en/blog/posts/csharp/1060/) 1. [XSS vulnerability in the ASP\.NET application: examining CVE\-2023\-24322 in mojoPortal CMS](https://pvs-studio.com/en/blog/posts/csharp/1054/) 1. [Under the hood of SAST: how code analysis tools look for security flaws](https://pvs-studio.com/en/blog/posts/cpp/1028/) 1. [Help the compiler, and the compiler will help you\. Subtleties of working with nullable reference types in C\#](https://pvs-studio.com/en/blog/posts/csharp/1017/) 1. [Virtual function calls in constructors and destructors \(C\+\+\)](https://pvs-studio.com/en/blog/posts/cpp/0891/) ## Infotainment articles ![1082_articles/image3.png](https://import.viva64.com/docx/blog/1082_articles/image3.png) Some of the entertaining articles are related to the bugs we've found\. However, errors described in such articles are more collectables or rarities\. 1. [Oh my C\! How they wrote code back in the Quake days](https://pvs-studio.com/en/blog/posts/cpp/1066/) 1. [Interview with developers of Flipper Zero — a multi\-tool for hackers and pentesters](https://pvs-studio.com/en/blog/posts/1075/) 1. [Top Reddit communities for Devs and ITs: from beginners to advanced](https://pvs-studio.com/en/blog/posts/1040/) 1. [Top 3 open\-source games written in C\#: searching for bugs](https://pvs-studio.com/en/blog/posts/csharp/1056/) 1. [Christmas holidays with PVS\-Studio](https://pvs-studio.com/en/blog/posts/1018/) 1. [Challenge: can you spot an error in C\+\+ code?](https://pvs-studio.com/en/blog/posts/cpp/0960/) 1. [The most interesting blogs and websites for C\+\+ developers](https://pvs-studio.com/en/blog/posts/cpp/0906/) ## Checks of open\-source projects ![1082_articles/image4.png](https://import.viva64.com/docx/blog/1082_articles/image4.png) 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: 1. [FreeCAD and undefined behavior in C\+\+ code: meditation for developers](https://pvs-studio.com/en/blog/posts/cpp/1072/) 1. [Typos, null pointers, and treacherous TAB: 33 fragments in the GTK library](https://pvs-studio.com/en/blog/posts/cpp/1076/) 1. [Checking the GCC 13 compiler with the help of PVS\-Studio](https://pvs-studio.com/en/blog/posts/cpp/1067/) 1. [Heroes of Code and Magic: VCMI game engine analysis](https://pvs-studio.com/en/blog/posts/cpp/1058/) 1. [Examining suspicious code fragments in AWS SDK for \.NET](https://pvs-studio.com/en/blog/posts/csharp/1057/) 1. [ONLYOFFICE Community Server: how bugs contribute to the emergence of security problems](https://pvs-studio.com/en/blog/posts/csharp/0783/) 1. [The check of the Rhino JavaScript engine or how the unicorn met the rhino](https://pvs-studio.com/en/blog/posts/java/0990/) ## Other ![1082_articles/image5.png](https://import.viva64.com/docx/blog/1082_articles/image5.png) These articles are mostly related to the PVS\-Studio analyzer and its development\. However, you can also come across off\-topic articles\. 1. [A tale of how PVS\-Studio reimagined the bug](https://pvs-studio.com/en/blog/posts/0977/) 1. [DefectDojo and PVS\-Studio: tracking errors and vulnerabilities](https://pvs-studio.com/en/blog/posts/1062/) 1. [Top 10 C\# conference talks 2019–2022](https://pvs-studio.com/en/blog/posts/csharp/1050/) 1. [Is ChatGPT good enough at spotting bugs in code?](https://pvs-studio.com/en/blog/posts/1035/) 1. [1000 eyes that don't want to check open\-source code](https://pvs-studio.com/en/blog/posts/cpp/0900/) 1. [Wave Function Collapse for procedural generation in Unity](https://pvs-studio.com/en/blog/posts/csharp/1027/) 1. [How deep the rabbit hole goes, or C\+\+ job interviews at PVS\-Studio](https://pvs-studio.com/en/blog/posts/cpp/0722/) ## Tell us: what article would you like to read? ![1082_articles/image6.png](https://import.viva64.com/docx/blog/1082_articles/image6.png) 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\!