You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/docs/Ways-of-Working/continuous-x-and-continuous-ai.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
The cleanest authoritative taxonomy. From [DevOps Dojo White Belt Foundation](https://learn.microsoft.com/en-us/training/paths/devops-dojo-white-belt-foundation/):
| 2 | Continuous Integration | Trunk-based dev, automated build & test on every commit |
13
13
| 3 | Continuous Delivery | Every commit potentially releasable; automated pipeline to prod |
@@ -20,7 +20,7 @@ The cleanest authoritative taxonomy. From [DevOps Dojo White Belt Foundation](ht
20
20
### Full inventory with provenance
21
21
22
22
| Practice | Origin / canonical source |
23
-
|----------|--------------------------|
23
+
|----------|--------------------------|
24
24
|**Continuous Integration**| Coined in Grady Booch's 1991 method; popularised by XP and [Martin Fowler's 2006 article](https://martinfowler.com/articles/continuousIntegration.html). |
25
25
|**Continuous Delivery**| Jez Humble & David Farley, [*Continuous Delivery*](https://continuousdelivery.com/), 2010. |
26
26
|**Continuous Deployment**| Every passing build deploys to prod with no human gate (vs. CD which only makes it *deployable*). |
@@ -73,7 +73,7 @@ Continuous AI tasks are: **automatable, repetitive, collaborative, integrated, a
73
73
### Continuous AI vs. its cousins
74
74
75
75
| Term | What it is |
76
-
|------|-----------|
76
+
|------|-----------|
77
77
|**Continuous AI**| AI participating *in* the SDLC continuously (review, docs, triage, fault analysis). The AI is the actor. |
78
78
|**MLOps**| CI/CD/CT *for* ML models — training, evaluation, deployment, monitoring. The model is the product. |
Copy file name to clipboardExpand all lines: src/docs/Ways-of-Working/devops-reference.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ A curated synthesis of authoritative sources, frameworks, and practices.
9
9
### The Canon (Books)
10
10
11
11
| # | Title | Author(s) | Year | Why it matters |
12
-
|---|-------|-----------|------|----------------|
12
+
|---|-------|-----------|------|----------------|
13
13
| 1 |**The Phoenix Project**| Gene Kim, Kevin Behr, George Spafford | 2013 | The novel that introduced DevOps to mainstream. Source of the Three Ways. [itrevolution.com/product/the-phoenix-project](https://itrevolution.com/product/the-phoenix-project/)|
14
14
| 2 |**The Unicorn Project**| Gene Kim | 2019 | Sequel from the developer's perspective; flow state, psychological safety, Five Ideals. |
15
15
| 3 |**The DevOps Handbook** (2nd ed.) | Gene Kim, Jez Humble, Patrick Debois, John Willis | 2016/2021 | Practical companion to Phoenix Project. The reference implementation guide. |
@@ -57,7 +57,7 @@ All available at **[sre.google/books](https://sre.google/books/)**
57
57
The evidence-based standard for DevOps performance. Source: Forsgren/Humble/Kim research, now part of Google Cloud.
58
58
59
59
| Metric | What it measures | Elite performance |
60
-
|--------|------------------|-------------------|
60
+
|--------|------------------|-------------------|
61
61
|**Deployment Frequency**| How often you deploy to prod | Multiple per day / on-demand |
62
62
|**Lead Time for Changes**| Commit → production | < 1 hour |
0 commit comments