Read on Twitter
Inspired by @levlaz, I'm publicly committing to a 100DaysOfDevOpsChallenge starting today!
#100DaysOfDevOps https://twitter.com/levlaz/status/1257904694749323264?s=20
#100DaysOfDevOps https://twitter.com/levlaz/status/1257904694749323264?s=20
1/
1st 1-1 chat with a SE (Solutions Engineer) today! He rec'd this primer on CI/CD
https://bit.ly/2xZ5rKz
TIL
Deployments are decided by the sought-after, magical CTO co-founder
Releases should be decided by "I'll handle the business side" people
#100DaysOfDevOps
1st 1-1 chat with a SE (Solutions Engineer) today! He rec'd this primer on CI/CD
https://bit.ly/2xZ5rKz
TIL
Deployments are decided by the sought-after, magical CTO co-founderReleases should be decided by "I'll handle the business side" people#100DaysOfDevOps
2/
Sales leader @LaunchDarkly rec'd "The Phoenix Project" to me
Finished Ch. 5.
TIL
Sucks to be in IT Ops cleaning up messes of Dev team
This book is written like stressful reality tv show at 2x speed
#100DaysOfDevOps
Sales leader @LaunchDarkly rec'd "The Phoenix Project" to me
Finished Ch. 5.
TIL
Sucks to be in IT Ops cleaning up messes of Dev team This book is written like stressful reality tv show at 2x speed#100DaysOfDevOps
3/
cont. "The Phoenix Project"
Finished Ch. 9
TIL
The
Ways
How to â
1. create a fast flow of work.
2. shorten and amplify feedback loops; fix quality at the source and avoid rework.
3. create a culture of experimentation & learning from failure.
#100DaysOfDevOps
cont. "The Phoenix Project"
Finished Ch. 9
TIL
The
Ways How to â
1. create a fast flow of work.
2. shorten and amplify feedback loops; fix quality at the source and avoid rework.
3. create a culture of experimentation & learning from failure.
#100DaysOfDevOps
4/
cont. "The Phoenix Project"
Finished Ch. 13
TIL
One person should not hoard all the knowledge
Careful documentation is necessary!
smoke tests & circuit designers
âNovember 1999 Thanksgiving Toys R Usâ train-wreck
FUBAR
#100DaysOfDevOps #100DaysOfX
cont. "The Phoenix Project"
Finished Ch. 13
TIL
One person should not hoard all the knowledge Careful documentation is necessary! smoke tests & circuit designers âNovember 1999 Thanksgiving Toys R Usâ train-wreck FUBAR#100DaysOfDevOps #100DaysOfX
5/
cont. "The Phoenix Project"
Finished Ch. 19
TIL
"Itâs not the upfront capital that kills you, itâs the operations and maintenance on the back end.â Like free
Taking needless work out of the system is > putting more work into the system.
#100DaysOfDevOps #100DaysOfX
cont. "The Phoenix Project"
Finished Ch. 19
TIL
"Itâs not the upfront capital that kills you, itâs the operations and maintenance on the back end.â Like free
Taking needless work out of the system is > putting more work into the system.
#100DaysOfDevOps #100DaysOfX
6/
cont. "The Phoenix Project"
Finished Ch. 25
TIL
âWhat that graph says is that everyone needs idle time, or slack time. If no one has slack time, WIP gets stuck in the system. Or more specifically, stuck in queues, just waiting.â
#100DaysOfDevOps #100DaysOfX
cont. "The Phoenix Project"
Finished Ch. 25
TIL
âWhat that graph says is that everyone needs idle time, or slack time. If no one has slack time, WIP gets stuck in the system. Or more specifically, stuck in queues, just waiting.â
#100DaysOfDevOps #100DaysOfX
7/
cont. "The Phoenix Project"
Finished Ch. 28
TIL
Always improve
âIf you are not improving, entropy guarantees that you are actually getting worse, which ensures that there is no path to 0 errors, 0 work-related accidents, and 0 loss.â
#100DaysOfDevOps #100DaysOfX
cont. "The Phoenix Project"
Finished Ch. 28
TIL
Always improve
âIf you are not improving, entropy guarantees that you are actually getting worse, which ensures that there is no path to 0 errors, 0 work-related accidents, and 0 loss.â
#100DaysOfDevOps #100DaysOfX
8/
cont. "The Phoenix Project"
Finished Ch. 35
TIL
âIn ten years, every COO will have come from IT. Any COO who doesnât intimately understand the IT systems that actually run the business is just an empty suit, relying on someone else to do their job.â
#100DaysOfDevOps
cont. "The Phoenix Project"
Finished Ch. 35
TIL
âIn ten years, every COO will have come from IT. Any COO who doesnât intimately understand the IT systems that actually run the business is just an empty suit, relying on someone else to do their job.â
#100DaysOfDevOps
9/
cont. "The Phoenix Project"
Finished.
TIL
THE FOUR TYPES OF WORK
Business projects
Internal IT projects
Changes
Unplanned work or recovery work (most wasteful, comes at the expense of planned work that will need to be replanned)
#100DaysOfDevOps #100DaysOfX
cont. "The Phoenix Project"
Finished.
TIL
THE FOUR TYPES OF WORK
Business projectsInternal IT projectsChangesUnplanned work or recovery work (most wasteful, comes at the expense of planned work that will need to be replanned)#100DaysOfDevOps #100DaysOfX
10/
DevOps Tools
- Continuous Development (Git)
- Continuous Integration (Jenkins)
- Continuous Deployment
--> Virtualization & Containerization (Docker)
--> Configuration Management (Puppet)
- Continuous Testing (Selenium)
- Continuous Monitoring (Nagios)
#100DaysOfDevOps
DevOps Tools
- Continuous Development (Git)
- Continuous Integration (Jenkins)
- Continuous Deployment
--> Virtualization & Containerization (Docker)
--> Configuration Management (Puppet)
- Continuous Testing (Selenium)
- Continuous Monitoring (Nagios)
#100DaysOfDevOps
11/
"While @LaunchDarkly makes testing in production possible, [they need] to test their own code as thoroughly as possible at the integration stage.
LaunchDarkly uses @CircleCI to safely manage
circular dependencies while deploying hundreds of times daily."
#100DaysOfDevOps
![11/"While @LaunchDarkly makes testing in production possible, [they need] to test their own code as thoroughly as possible at the integration stage.LaunchDarkly uses @CircleCI to safely manage circular dependencies while deploying hundreds of times daily." #100DaysOfDevOps](https://pbs.twimg.com/media/EYun2e_WAAcqars.jpg "11/\"While @LaunchDarkly makes testing in production possible, [they need] to test their own code as thoroughly as possible at the integration stage.LaunchDarkly uses @CircleCI to safely manage circular dependencies while deploying hundreds of times daily.\" #100DaysOfDevOps")
"While @LaunchDarkly makes testing in production possible, [they need] to test their own code as thoroughly as possible at the integration stage.
LaunchDarkly uses @CircleCI to safely manage
circular dependencies while deploying hundreds of times daily."#100DaysOfDevOps
