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.
It's how a fictional company goes from guesswork to greatwork regarding the many, many facets of its tech departments.
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 -
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.
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
Post a Comment