Dr. Stark O. Verflo, M.D.
Problem
The patient has a broken leg.
Tips and tricks
Myths about static analysis. The fifth myth – a small test program is enough to evaluate a tool
This is how this statement looks in discussions on forums (this is a collective image):
I’ve written a special program, its size is 100 code lines. But the analyzer doesn’t generate anything although all the warning levels are enabled. This [tool of yours] / [static analysis] in general is just rubbish.
Hire Dedicated Developers: Skills and Factors to Consider
Hiring new people is always a challenge. No matter whether those are your own employees or outsourced workers. However, hiring dedicated developers or team there are certain skills and factors which need to be considered. And that’s where our advices will come in handy for you.
Myths about static analysis. The fourth myth – programmers want to add their own rules into a static analyzer
No, they don’t. They actually want to solve some tasks of searching for particular language constructs. It is not the same thing as creating diagnostic rules.
Myths about static analysis. The third myth – dynamic analysis is better than static analysis
The statement is rather strange. Dynamic and static analyses are just two different methodologies which supplement each other. Programmers seem to understand it, but I hear it again and again that dynamic analysis is better than static analysis.
Let me list advantages of static code analysis.
Myths about static analysis. The second myth – expert developers do not make silly mistakes
Myths about static analysis. The first myth – a static analyzer is a single-use product
While communicating with people on forums, I noticed there are a few lasting misconceptions concerning the static analysis methodology. I decided to write a series of brief articles where I want to show you the real state of things.
What is static code analysis?
Static code analysis is the process of detecting errors and defects in a software’s source code. Static analysis can be viewed as an automated code review process. Let’s speak about the code review now.
C++ pointers: why we need them, when we use them, how they differ from accessing to object itself
Even though most programmers understand what is the difference between objects and pointers to them, sometimes it is not entirely clear, which of the ways of accessing the object to choose. We have tried to answer this question below.
Programming Concepts: The Stack and the Heap
As we continue to use more advanced programming languages, we’re able to get some seriously powerful development done with much less code that does increasingly more awesome stuff, but that comes at a price. Since we don’t deal as often with low-level computation and processing anymore, it’s only normal that we don’t always have a full understanding about topics like what the stack is versus the heap, or how compilation really works, or what static vs dynamic typing is, or type introspection, or garbage collection, etc. Now I’m not saying every developer is ignorant of these, as most of us certainly aren’t, but I do feel like it’s worth revisiting some of the old-school important topics that we may miss out on these days.
