• Symmathesetic Aretê
Home
12 Factors
3 Steps of Software: Encoding Knowledge
A Spoonful of Convention Makes the DevOps Go Down
API Design for Humans
API Tokens
Actionable Zettel Note Taking Advice
Adopting DevOps
Adulting App
Always Green Master
App - Reclaiming My Time
App CLI - git gud
Applying to Jobs the Smart Way
Aretê
Automation With a Human Touch - Jidoka
Bazel
Bespoke Infrastructures
Blameless post-mortems
Blog Ideas
Bootstrapping People
Branch By Abstraction
Build It Once
Build Quality In
Build System Correctness
Build System Rebuilders
Build System Schedulers
Build Systems
Build Systems Suck
Build Systems in terms of DAGs and CFGs
CAP Theorem
CAP Theorem for Software Engineering
CD Thoughts
CI for Haskell
CI/CD Failure Strategies and Conditional Execution
CI/CD Platform Ergonomics
Capability Based RPC
Career
Chaos Engineering
Cloud Design Patterns
Collaborative Web
Combining Simplicity and Complexity
Common Vocabulary for Build Systems
Communities of Practice
Comparing Learning Systems
Concrete Goals of CI/CD/CC
Concurrency
Configuration
Configuration Drift
Constructive Traces
Context
Context Switching
Continuous Compliance
Continuous Delivery
Continuous Delivery and Continuous Compliance
Continuous Integration
Continuous Learning
Continuous Monitoring
Continuous Reasoning
Continuous Testing
Convention over Configuration
Correct by Construction
Cover Letter
Culture Influences Infrastructure
Customer Focus
Dark Debt
Data Fetching
Decision Making Models
Declarative DSLs for infrastructure
Deferred Compliance
Demarcation Problem
Dependencies
Deploy is not Release
Deployment Pipelines
Design Systems
Detecting Agile BS
DevOps
DevOps Maturity Timeline
DevOps Topologies
DevOps Topology Type 1: Dev and Ops Collaboration
DevOps Topology Type 2: Fully Shared Ops Responsibilities
DevOps Topology Type 3: Ops as Infrastructure-as-a-Service
DevOps Topology Type 6: DevOps Advocacy Team
DevOps Topology Type 7: SRE Team (Google Model)
DevOps Topology Type 8: Container-Driven Collaboration
DevOps and SRE Reading
DevOps for Embedded
DevSecOps
Developing Good Explanations
Development Environments
Dhall as a service
Differences Between Build Systems, Package Managers, Compilers, and IDEs
Discoverable Knowledge
Disposability
Distributed Systems
Divergent, Convergent, and Congruent Infrastructures
Documentation
Don’t Special Case Administrative Tasks
Dynamic Cross-project Pipelines
Effective Organizational Culture
Empower Across Boundaries
Empowering Environments
Enabling team
Engineering Concerns of Build Systems
Entropy
Environment
Environment Parity
Environment and Context
Erase Your Darlings
Expression Problem
Expressiveness of Build System Operation DSLs
FRP and Build Systems
Faster Feedback Loops Pay for Themselves
Feedback Loops
Financial Fragility
Flow Metrics
Flow: Systems Thinking
Focus, Flow, Joy
Formally Verified DNS
Forwards and Backwards Compatible
Four Type of Documentation
Futamura Projection
Git Changed Files
GitHub Actions
Golden Rule of Software Quality
Good Explanation
Habit Tracker on a Display Board
Haskell testing an exe from a test stanza
Home Automation
Ideas
Ignorance
Immutable Infrastructure
Implicit Social Structures
Improvement of Daily Work
Incidential Complexity
Incremental Change
Infrastructure as Code
Infrastructure as Data
Inter Process Communication (IPC) Landscape
Interviewing the Company
Jepsen Notes
Joy at Work
KISS Secrets
Karl Popper’s Three Worlds
Keyboards
Kolb’s Learning Cycle
Law of Requisite Variety
Link Dump
Live Database Migrations
Local Environments and CI
Local Reasoning
Locality / Simplicity
Logging
Low Energy Audio (and Hearing Aids)
Low Risk Releases
Macaroni and Cheese
Mapping out Build Systems in terms of Rebuilder + Scheduler Strategies
Media Matrix
Memory
Metrics
Metrics Charts
Metrics from the correct point of view
Metrics of Software Delivery
Multi Room Audio
Myron’s Maxims
Negative vs Positive Hyperbole
Neovim
Nerdsnipe
Nix vs Docker
OODA loop
Observability
Old Linux New Compiler
Ops Meta-Metrics
Opt-In vs Opt-Out
Overriding nvidia-persistenced for NixOS
PARA
Package Management
Paradox of Tolerance
Pareto Principle
Performer Metrics
Phoenix Project: 3 Ways
Picking a DevOps Topology
Platform
Platform Strategy
Plus/Minus/Interesting
Port Binding
Practical Implementation Tips for Secrets
Processes
Project Metrics
Prometheus Monitoring
Properties of Build Systems.
Properties of CI/CD/CC
Psychological Safety
Q4
Quality vs Resilience vs Reliability
Questions about Build Systems
RAPID Decisions
Release Engineering
Release Strategies and Versioning
Representing Zettels as a Graph
Reproducible Builds
Resiliance
Responsibility
Resume
Reusable Pipelines
Reuse
Rules of Thumb
Running CI Locally
Scorched Earth
Secret Management Engineering Concerns
Secret Management Solutions
Secrets
Secrets as a Secret
Security Considerations
Self-Service as a Service
Self-Validating Good Explanations
Service - House Finding
Services
SignWriting
Signs of a Highly Effective Architecture
Simplest, But No Simpler
Software Architecture
Software Delivery
Software Engineering as a Discipline
Software Engineering as a Team Focus
Spaced Repetition
Static Analysis
Stream-aligned team
Symmathesy
Taking Care of Code… More and More Code
Taskwarrior Workflow
Team Topologies
Test Suites
Testing Styles
The DevOps Handbook
The Developer Coefficient
Theories Under Test
Theory of Constraints
Thought Management
To Read and Digest
Tools vs Solutions
Tracking Change
Translating FRP and Redux into Optics and Recursion Schemes
Trunk Based Development
Typed Configuration
Types of Notes
Unicorn Project: 5 Ideals
Universal Accessability
Variational Typing
Versioning
Web Design / CSS
Weird Build Systems
Well Designed Abstractions
What Defines High Quality Work for DevOps?
What Will The Next 10 Years Of Continuous Delivery Look Like?
What is the Value of DevOps?
Windows Dev VMs
Workflow Models
Workflow Patterns
YAML as a DSL
Zero Trust Model
eudaimonia
kubernetes
service mesh tracing stuff

Immutable Infrastructure

https://grahamc.com/blog/erase-your-darlings https://mt-caret.github.io/blog/posts/2020-06-29-optin-state.html

Links to this page
  • Project Metrics
    Reset an environment (Immutable Infrastructure, Erase Your Darlings)
  • Erase Your Darlings

    Instead, practice Immutable Infrastructure (but to an even greater degree). Seek out things that cause Configuration Drift and root them out of the system. Culturally, this also makes state Opt-In vs Opt-Out.

    https://grahamc.com/blog/erase-your-darlings, better than Immutable Infrastructure. https://mt-caret.github.io/blog/posts/2020-06-29-optin-state.html

  • Configuration
    Immutable Infrastructure