Static Code Analysis
Podcast: Play in new window | Download (63.8MB) | Embed
Subscribe: Apple Podcasts | Spotify | Email | RSS | More
Static code analysis is a way of debugging that automatically examines source code before it compiles or is run. It does this by comparing the code code to a set of rules or standards. It is a way of automating code reviews and can be used in conjuncture with peer reviews.
Yuri Minaev is working in the PVS-Studio company as one of developers of the C++ static analyzer. His primary responsibility is to keep low-level stuff in order and add new features to the core module. It’s been almost 2 years since he joined the team after about 12 years of IT experience. Apart from that, he periodically gives talks at various conferences – mainly on topics related to static analysis and C++.
PVS-Studio is cross platform, working on Windows, Linux and MacOS 64-bit environments. It can analyze code designed for 32-bit and 64-bit systems as well as embedded ARM platforms. It generates reports that help developers to find and fix bugs before they become a problem.
Keeping a codebase clean and detecting problems before they occur will make your life better as a developer. When you can avoid getting nailed by simple problems, you can think about your software at a higher level, vastly improving your effectiveness as a software developer. It’s not just about avoiding bugs, although that’s important, but about what you can do with the time, money, and attention you save.
Remote Work: The Complete Guide.
Chapter 10 – The Ultimate List of Remote Work Resources. This last chapter of the book lists out a ton of resources for remote work. This includes tools for automation, books, blogs, podcasts, career resources, and other things that will help you on your remote work journey. While you can do it all the hard way, you’ll get a lot further a lot faster if you learn from other people and use what they know. This section will help you do that.
Tricks of the Trade
It can be hard to let things go. Especially when it’s a project you’ve been the primary developer on for a while. You don’t want to let other people in to mess with the patterns and paradigms you’ve set up. However, in order to move forward we have to move on from our old code. There are developers who spend years building a large intricate system, but don’t allow anyone else to touch it. This means they spend the next few decades maintaining it. If you don’t want to spend your career updating and maintaining something you wrote early on, then you have to allow others to make changes in your code.
Remote Work Book
Yuri lives in Russia so the audio from the call is not the best.