diff options
| author | EuAndreh <eu@euandre.org> | 2020-10-14 00:25:39 -0300 |
|---|---|---|
| committer | EuAndreh <eu@euandre.org> | 2020-10-14 00:25:39 -0300 |
| commit | f33cb06c7bda61657a324c2f4d54644a2673feb7 (patch) | |
| tree | 3568bb667f94ac08d8b9727898c3b6f27f577d48 | |
| parent | assert-spelling.sh: Actually show unique mispelled entries (diff) | |
| download | euandre.org-f33cb06c7bda61657a324c2f4d54644a2673feb7.tar.gz euandre.org-f33cb06c7bda61657a324c2f4d54644a2673feb7.tar.xz | |
Spelling of feature flags article
Diffstat (limited to '')
| -rw-r--r-- | _articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md | 8 | ||||
| -rw-r--r-- | scripts/spelling/en.txt | 3 | ||||
| -rw-r--r-- | scripts/spelling/international.txt | 1 |
3 files changed, 8 insertions, 4 deletions
diff --git a/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md b/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md index 2fa0104..4cc41e9 100644 --- a/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md +++ b/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md @@ -25,15 +25,15 @@ acquired when using them in production. ## Why feature flags Feature flags in general tend to be cited on the context of -[continous deployment][cd]: +[continuous deployment][cd]: -> A: With continous deployment, you deploy to production automatically +> A: With continuous deployment, you deploy to production automatically > B: But how do I handle deployment failures, partial features, *etc.*? > A: With techniques like canary, monitoring and alarms, feature flags, *etc.* -Even though adopting continous deployment doesn't force you to use feature +Even though adopting continuous deployment doesn't force you to use feature flags, it creates a demand for it. The inverse is also true: using feature flags on the code points you more obviously to continuous deployment. @@ -49,7 +49,7 @@ application in runtime, without doing any code changes. Sometimes this added complexity may tilt the balance towards not using a feature flag, and sometimes the flexibility of changing behaviour on runtime absolutely -is worth the added complexity. This can vary a lot by codebase, feature, but +is worth the added complexity. This can vary a lot by code base, feature, but fundamentally by environment: its much cheaper to deploy a new version of a service than to release a new version of an app. diff --git a/scripts/spelling/en.txt b/scripts/spelling/en.txt index 3899718..f7128b1 100644 --- a/scripts/spelling/en.txt +++ b/scripts/spelling/en.txt @@ -1,6 +1,7 @@ Patches Rollout Slides +analytics aren autocommit backend @@ -10,6 +11,7 @@ chargeback couldn cronjobs curation +dataset declaratively decrypting didn @@ -26,6 +28,7 @@ oday portuguese portuguse pre +preventively programmatically realising reimplementation diff --git a/scripts/spelling/international.txt b/scripts/spelling/international.txt index 5d59ebf..8b0851f 100644 --- a/scripts/spelling/international.txt +++ b/scripts/spelling/international.txt @@ -129,6 +129,7 @@ jemoji js k8s kramdown +kubernetes libre lockfile lockfiles |