Many companies and teams focus on technical security solutions that lock down development and innovation to avoid risk. To protect their systems, they often end up making it harder for developers to do their jobs (and less secure in the process). What if I told you there was a better way? If you start with people and process first, you can create a secure CI/CD pipeline that balances safety and speed.

So many times, teams use “it should work” as the reason why their software or processes don’t require testing. For example, the code is so simple, it should work. Or, the code was tested on Linux, so it should work on Windows. In reality, this can be dangerous at best … and fatal at worst.

Unlocking the power of GitOps means learning to use Git as the source of truth for deployments. Key to that is understanding the three models used for defining your GitOps practices.

You might be less secure than you think! In a crowded market of security tools, developers are being sold a dream that quickly turns into a nightmare.

Your Azure Active Directory account has a special domain name associated with it. Learn how to create users in this domain to manage Azure more effectively.