Amelie Koran - The Dunning-Krueger Effect of DevSecOps
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.
With the rapid pace of technology transformation and modernization that is taking place, it’s easy to fall into the trap of thinking just because you slapped a title on the process, it means you are doing it and doing it well.
With the current move of DevOps to DevSecOps, individuals and organizations believe that they can buy their way into problem-solving when it is more of a process reengineering and knowledge management task.
This is overestimating the challenge, the work required, and the ability to achieve within the proposed time frame.
With new and often not well-understood frameworks and methodologies being thrown at teams to implement or migrate to, ego and self-confidence, along with a dash of “keeping up with the Joneses” can get people into a spot of trouble.
My talk will cover some self-assessments for organizations and individuals about where they are at with a journey to DevSecOps, what gap analysis they need to perform, and a few patterns that can be used to approach these challenges.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.