Curated articles, resources, tips and trends from the DevOps World.
It used to be so easy. Never, ever open a DOC of an XLS file from someone you don’t know. Ah well, those simple, early days of phishing are long gone. Mind you, people still fall for those attacks, but now phishing attacks have a new, novel way of getting on your PCs.
The rise in cyberattacks and the critical role that software plays in our lives has brought to light the need for increased transparency and accountability in the software supply chain.
When software developers are building their microservices for use inside Docker containers, it saves a great deal of time and effort for them to also test for various dependencies in parallel instead of starting from scratch after the app is done.
DevOps is full of buzzwords, jargon and abbreviations. DevOps itself has only been around for a little more than a decade, so some of these concepts are relatively new. However, some are quite old, and their definitions and uses have changed over time.
Does data for artificial intelligence and machine learning need their own workflows and orchestration system? It does, according to Union.ai, which offers an open source solution called Flyte that provides workflow and orchestration to fit the unique demands of data, not software.
For the closing keynote of the Southern California Linux Expo, 80-year-old Unix pioneer Ken Thompson delivered the tale of his 75-year project that combined his technologist’s spirit and his sense of humor — as well as his love of music.
Have you ever tried to deploy a local Docker registry, build a Docker image, push the image to that local registry, and use the image for a new container deployment? If you have, you know how challenging and time-consuming that task can be. Get one thing wrong and nothing will work.
I was amused to hear this on a recent episode of The Changelog podcast. Nathan Sobo was talking about work on his company’s new code editor project, Zed. This is described as a “high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
The Computer-Security Incident Notification Rule requires US federal banking organizations and banking service providers to notify the Office of the Comptroller of the Currency (OCC) that a cybersecurity incident has occurred.
NIST 800-161 — also identified as NIST Special Publication (SP) 800-161 — was published in April 2015 as Supply Chain Risk Management Practices for Federal Information Systems and Organizations.
Have valuable insights to share with the DevOps community? Submit your article for publication.
Get the latest DevOps news, tools, and insights delivered to your inbox.
Made with pure grit © 2026 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com