Skip to main content

The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win by Gene Kim and Kevin Behr

This was briefly available for free on December 19th, so I picked it up to read over the holiday, enjoying a good novel.

 I like the pixel art!

It's how a fictional company goes from guesswork to greatwork regarding the many, many facets of its tech departments.

"Processes are there to protect people."

I realized quite a few interesting things: 

High, lofty titles like VP of Technology may be for some people, but not for me. Give me good old, on the ground IT Help Desk or Network Technician any day. This had me rethinking my entire career path - applying for 3 years to possibly get into a company like this?

But every career has its challenges and tough times. Nothing is immune, and if it is, it's not fun!


However, if you'd like to share this blog with others so we get some views and maybe a sponsor, well, I won't be opposed to that.  #AvoidCorporateRigamarole2020




Tech departments are a lot more varied than I thought. There is a segment where a critical server is down, and multiple departments are blaming each other, from Database, to Developers, to Networking. I understand why recruiters may be annoyed at a submission to a role that seems similar to us, but not to them.

There is a reference to the second greatest movie of all time.

The bureaucracy and politics of big business for resources is for other people, not me. There's even a line that says many of the factory workers live paycheck to paycheck. There's not enough money to even help the business run at first.

These are the environments we try so hard to be a part of so we don't starve.

Small startups have their problems (Hi, Away, WeWork, and probably others), but at least it doesn't take 3 weeks to make a change. This does encourage me to ask employers about their change processes for further up the ladder -

Do we need to log our requests / changes in any particular system? Is there one set up?

Your boss isn't listening to you. I hope that's the exception and not the norm.

Of course, this is pre-fixup, before our main character jumps in to reorganize the tech department.It's interesting, and everything is okay! Sure there are challenges, but it's not putting out fires all the time. It's facing new things and learning and making the company better. And that's all we want!

Also; Wes is my favorite. 

A good portion of the book - about 20% - is dedicated to explaining DevOps things in depth, without a narrative blanket. Much of it makes no sense to me yet, but it's a good place to read and start learning from.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory