Skip to main content

You still have not read Phoenix Project

I started at a new company and the people that I interviewed with had read the Phoenix Project.  That was exciting and I could relate to their goals.  After a few weeks of working there it was clear, they were the only ones that had read it.  You should already see the red flags going off about what I got myself into.

I have made presentations to everyone from senior leaders to individual contributors.  The last slide in every presentation is a picture of the Phoenix Project and Web Operations.  I will talk about Web Operations in the future.  Every time I get to this slide, I see people just hang their heads. (Maybe it is just because I present badly)  Some of the people have heard how good it is but just have not made it a priority to read.

I told my team it is mandatory to read it and I think any IT company should make it mandatory.  I bought 4 copies this week on Amazon to bring to work and start farming them out.  If you want to start creating a change in culture, this may be an easy way to start.   In the future, I don't think I will hire anyone that has not read it.  I think you have to read this book to believe there is hope in the future of IT.

Comments

Post a Comment

Popular posts from this blog

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Post a Comment
Read more

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

How AI is Transforming DevSecOps: A New Era of Secure, Agile Software Delivery

 As software delivery accelerates and attack surfaces grow, traditional DevSecOps practices are being pushed to their limits. The integration of artificial intelligence (AI) into DevSecOps workflows is not just a trend—it’s a strategic imperative. AI is driving a seismic shift in how we manage code quality, automate security, respond to threats, and enable secure innovation at scale. In this post, we’ll explore the key ways AI is improving DevSecOps and why forward-thinking organizations are embedding it deeply into their pipelines. 1. Proactive Threat Detection and Response In modern CI/CD pipelines, code moves fast—sometimes too fast for human eyes to catch every vulnerability or misconfiguration. AI helps shift security left and right by: Analyzing code and dependencies with natural language processing and ML to detect hidden vulnerabilities, insecure APIs, or anomalous changes during commits. Real-time anomaly detection in production environments using AI-powered o...
Post a Comment
Read more