We’re excited to share news of a very special collaboration that promises to bring new depth and insight to our blog. We have the honor of partnering with a distinguished expert in DevOps and cybersecurity, whose extensive body of work has significantly shaped these fields.
Exploring Groundbreaking Insights Together
Our collaborator is a seasoned author with a wealth of knowledge in DevOps, cybersecurity, and compliance. Their publications serve as essential resources for professionals across the IT spectrum.
The DevOps Collection includes insightful titles such as:
- Building DevOps Essentials: Fundamental practices every DevOps practitioner should embrace.
- Blueprint: Automated Operations: A roadmap for enhancing efficiency through automation.
- Scaling DevOps Impact: Strategies for implementing DevOps principles on a larger scale.
- Agile Meets DevOps: Integrating agile methodologies with DevOps for faster results.
- DevOps Team Dynamics: Understanding the team interactions that drive DevOps success.
The Cybersecurity Collection shifts focus to securing IT environments with titles like:
- The Art of Cyber Defense: Techniques for protecting against modern cyber threats.
- Leadership in Cybersecurity: Cultivating leadership skills within the cybersecurity arena.
- Incident Response Leadership: Handling and recovering from security incidents effectively.
- CISO Essentials: A guide for Chief Information Security Officers leading security initiatives.
The Compliance Collection tackles important regulatory standards:
- SOX Simplified: An accessible guide to the Sarbanes-Oxley Act.
- NIST: Insights into standards set by the National Institute of Standards and Technology.
- PCI-DSS Decoded: Understanding the essentials of Payment Card Industry Data Security Standard.
- HIPAA and SOC 2: Navigating the complexities of healthcare information compliance and security frameworks.
Learning from a Seasoned Professional
We’ll begin our collaboration with a series of blog posts that summarize each book. Our goal is to not only introduce you to the key concepts discussed in these works but also to explore how they can be practically applied to improve your operations and strategic planning.
Additionally, we will conduct in-depth interviews with the author to learn about their professional journey, experiences, and the motivations behind their influential works. These conversations will provide a closer look at how their advice can be leveraged to stay ahead in the rapidly evolving fields of DevOps and cybersecurity.
What Lies Ahead
This partnership marks the start of an exciting phase of shared learning and growth. We look forward to expanding these collections and exploring new topics to keep you informed and equipped with the latest industry knowledge.
Stay tuned to our blog for detailed posts and insightful discussions that will help you refine your practices and strategies. Whether you are deeply embedded in DevOps, cybersecurity, or compliance, this collaboration is geared to enrich your professional journey.
We are truly grateful for this opportunity to bring such valuable insights directly to you through our blog. It’s a partnership we believe will greatly benefit our community, helping us all grow and succeed together.
I hope the series includes flaky test triage and release confidence, not just deployment practices. In a smaller regulated company like mine, a false green build can be more damaging than a slow one.
“Scaling DevOps Impact” sounds useful… but please include database migrations, because they are where cheerful deploy plans meet locks. Strictly speaking, NIST publishes frameworks and standards rather than being a single standard itself. In a mid-sized financial shop, one long-running query can still ruin a Friday, as I have repeatedly demonstrated to myself.
the distinction on nist is worth making, because people at my company use it as shorthand for almost anything compliance-related. i would read something on migrations and rollback planning before another broad automation overview. we are a small health services company, so our database changes are not huge, but a lock at the wrong time still becomes everyone’s problem.
my previous employer called it impact, where’s the evidence?
fair question. i havent tried the material yet but i plan to, and “impact” means nothing unless it shows roadmap cost or something customers actually notice.
we run next.js on github actions, and 42-minute builds have already cost us six shipping hours this month. management will not approve headcount because a book says faster results.
I’m not sure another set of DevOps book summaries will help much on its own, but the interview angle could be really useful. Could you do a follow-up on frontend build times, cache invalidation, and how DevOps teams keep deploys from slowing down as the app grows? I haven’t tried many of these approaches yet but plan too
i’m interested in the team dynamics material, especially how it handles review friction. we had a production outage last year after a rushed approval skipped a test that would have taken 12 minutes to run. somehow the postmortem was longer than the test suite, which felt efficient in its own special way. i disagree with summarizing each book as the main format, because summaries often remove the awkward tradeoffs developers actually need to discuss. at my job, 30% of review delays come from unclear ownership, not a lack of process vocabulary. concrete examples of testing and handoffs would be more useful than polished principles.
Follow-up on 3am pipeline rollback perms… who owns teh pager?