Take aways from the Phoenix project book

-


I completed reading the awesome Pheonix project book and as is normal for the lessons to fade away, I might forget all of it as the days go by, but the summary of what I loved the most in this book is

Every work center is made up of four things. 
The machine. 
The man. 
The method. 
And the measures.
 And one more
First way helps us understand how to create fast flow of work from Dev to Ops. 
Second way shows us how to shorten and amplify feedback ... 
Third shows us how to create a culture that simultaneously foster  experimentation, learning from failure and understanding that repetition and practice are the  prerequisites to mastery.

 Even though it was monotonous at times, and this book could have continued to be interesting until the last page if it could be shortened, but it was a great book and helped me to come across the master piece "The Goal" which I am reading now


Popular posts from this blog

Learning OpenStack - The Easy Way

-
Image
Dear Friends, Our Dream has come true! It takes 9 months for a mother to bring another life. That is the amount of time it has taken me to demystify the otherwise terse and abstract cloud computing concepts. And thanks to Packt Publishing I for helping me impart this knowledge in the most engaging way. The Full video course is out you can get more details about it here . You can get more details about the course here without registering. The Overview video is out for all. It was a tough negotiation with publisher to give out this valuable video for free I hope that it will get you started on your "Infrastructure as Code" journey. Three points I would like to share, which might help you are:- People are watching us! Packt publishing approached me watching the screencasts I had posted on Youtube. (Which until then I was certain that nobody was watching). Good news is Video course royalty is 3 times that of a book! Bad news is because its 3 times the...
Read more

Vagrant on steroids

-
Image
Source This is our life when we are working on automating some really complicated machine building and provisioning procedures. I.e. while developing the playbooks in Ansible, or CookBooks in Chef or manifests in Puppet. It is not easy to fail faster and fix early as the script might have to download all the dependencies again and again. Adding to all the odds, it could be that the dependencies are being downloaded on a low bandwidth. Even though Vagrant makes bringing up VM and their management faster, the provisioning (using Ansible, Chef or Puppet or etc) might take inordinately long times when it involves, and it usually does involve downloading packages on the VMs. And it gets painful when you have to download a full stack of several libraries to test your VM. To help overcome this issue, we can use the following to cache the dependencies and test the configuration scripts or recipes faster, the following should set you up (assuming you have vagrant already installe...
Read more