The DevSecOps movement aims to bridge the gap between Security and Development teams by blurring their lines and sharing goals and accountabilities. However, many organizations struggle with this due to misalignment caused by different languages, priorities, and approaches. The current status quo often results in a reactive and inefficient process, where security is periodically assessed and passed back to Dev for analysis and resolution, leading to inflated workloads and increased risk of exploitation. To improve this, it's essential to start at the bottom by understanding the root causes of the chasm, which is often due to different languages and priorities. The solution lies in creating a common language, automating processes, and educating teams on secure coding practices. By doing so, Security and Development can work together more effectively, reducing friction and improving productivity. Ultimately, shared foundations and clear understanding are key to building great relationships between these two teams.