Stephen Magill - Do's and Don't's of Code Analysis Patterns and Metrics
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
Do you feel like your company's security / approval / development requirements are slowing everyone down?
Do you struggle to find the right balance of tending to legacy code versus supporting new development?
In this interview, we will discuss various methods of integrating code analysis and code metrics into the development process.
We’ll cover the best practices for code analysis integration that were pioneered by Google and Facebook and contrast these with various “anti-patterns” that often occur.
We’ll also discuss important metrics to track as you integrate code analysis into your workflow and talk about good and bad uses of these metrics. Learn about:
-
How to improve code security and reliability without decreasing productivity.
-
Uses and misuses of code analysis metrics.
-
The different uses of code analysis and how static analysis tools can help with more than just security.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.