A Field Guide to Site Topics Fundamentals 5

Use direct, ordinary language. For example, ask, “Would you like to continue?” or “Are you comfortable with this?” A clear spoken answer can reduce guesswork, especially when you are unsure how to read someone’s response. Consent can be communicated in different ways, but a practical approach is to check verbally rather than infer agreement from silence, body language or the absence of resistance.

Queue Design: Periodic jobs should be safe to run twice, because they will be. You rarely need a new component to fix a boundary problem. That applies to queue design as well. In practice, queue design behaves differently: The signal you want is often already logged, just not aggregated.

Consent requires the ability to make and communicate a choice. Someone who is asleep or unconscious cannot agree at that time. Alcohol or other drugs can affect judgment and communication, but the legal rules for assessing capacity vary. The relevant question is not simply whether someone has consumed a substance; it is whether they can understand the choice and make it freely. If that is unclear, do not proceed.

You can often replace a coordination problem with an idempotency key. The same reasoning holds for api design. For api design, the constraint matters more than the feature list. Anything that grows without a bound will eventually hit one. Teams working on api design usually discover this the hard way. Documentation that is not tested tends to describe the previous version.

A queue smooths spikes but also hides how far behind you are. This is most visible in log analysis. Consider log analysis specifically. Retries without jitter turn a small outage into a large one. Log Analysis: Separating the reads from the writes buys room to change either side.

Search Indexing: A design that cannot be rolled back is a design that cannot be changed safely. Search Indexing: Latency budgets are easier to defend when every hop has a stated ceiling. Search Indexing: Caching helps only until the invalidation rules become the bottleneck.

If the rollback plan needs a meeting, it is not a rollback plan. The same reasoning holds for backup strategy. For backup strategy, the constraint matters more than the feature list. Small pages that stay small are easier to keep fast than large ones made fast. Teams working on backup strategy usually discover this the hard way. Write the invariant down; otherwise it lives only in someone's memory.

A respectful response acknowledges the limit and follows it. A partner may ask a clarifying question, provided the question is not a way to wear someone down. Repeated requests after a clear no, guilt, anger used to secure agreement, or threats to end the relationship can undermine consent. Silence or lack of resistance should not be treated as agreement.

A queue smooths spikes but also hides how far behind you are. This is most visible in release process. Consider release process specifically. Retries without jitter turn a small outage into a large one. Release Process: Separating the reads from the writes buys room to change either side.

Schema Markup: Configurations should be reviewable in a diff, not only in a console. The best time to add an index is before the table gets large. That applies to schema markup as well. In practice, schema markup behaves differently: Failures are usually correlated, so plan for the shared dependency.

Release Process: If a metric has no owner, it will drift until it causes an incident. Release Process: The cheapest optimisation is usually removing work nobody asked for. Release Process: Aggregating at write time trades flexibility for predictable read cost.

Cloud Infrastructure: You can often replace a coordination problem with an idempotency key. Cloud Infrastructure: Anything that grows without a bound will eventually hit one. Cloud Infrastructure: Documentation that is not tested tends to describe the previous version.

Teams working on data pipelines usually discover this the hard way. The interesting number is not the average, it is the 99th percentile. Adding a cache in front of a slow query is a fix; fixing the query is a cure. This is most visible in data pipelines. Consider data pipelines specifically. Every abstraction you add is a place where behaviour can differ from intent.

For cloud infrastructure, the constraint matters more than the feature list. A queue smooths spikes but also hides how far behind you are. Teams working on cloud infrastructure usually discover this the hard way. Retries without jitter turn a small outage into a large one. Separating the reads from the writes buys room to change either side. This is most visible in cloud infrastructure.

Load Balancing: Configurations should be reviewable in a diff, not only in a console. Load Balancing: The best time to add an index is before the table gets large. Load Balancing: Failures are usually correlated, so plan for the shared dependency.

Queue Design: If a metric has no owner, it will drift until it causes an incident. Queue Design: The cheapest optimisation is usually removing work nobody asked for. Queue Design: Aggregating at write time trades flexibility for predictable read cost.

Data Pipelines: If the rollback plan needs a meeting, it is not a rollback plan. Data Pipelines: Small pages that stay small are easier to keep fast than large ones made fast. Data Pipelines: Write the invariant down; otherwise it lives only in someone's memory.

Teams working on release process usually discover this the hard way. Serving static bytes is the cheapest thing you can do at the edge. A schema is an interface; changing it is a migration, not an edit. This is most visible in release process. Consider release process specifically. Track the denominator as carefully as the numerator.

Consider edge caching specifically. Serving static bytes is the cheapest thing you can do at the edge. Edge Caching: A schema is an interface; changing it is a migration, not an edit. Track the denominator as carefully as the numerator. That applies to edge caching as well.

Access Control: If the rollback plan needs a meeting, it is not a rollback plan. Access Control: Small pages that stay small are easier to keep fast than large ones made fast. Access Control: Write the invariant down; otherwise it lives only in someone's memory.

If a metric has no owner, it will drift until it causes an incident. This is most visible in monitoring alerts. Consider monitoring alerts specifically. The cheapest optimisation is usually removing work nobody asked for. Monitoring Alerts: Aggregating at write time trades flexibility for predictable read cost.

The interesting number is not the average, it is the 99th percentile. The same reasoning holds for edge caching. For edge caching, the constraint matters more than the feature list. Adding a cache in front of a slow query is a fix; fixing the query is a cure. Teams working on edge caching usually discover this the hard way. Every abstraction you add is a place where behaviour can differ from intent.

Serving static bytes is the cheapest thing you can do at the edge. The same reasoning holds for cloud infrastructure. For cloud infrastructure, the constraint matters more than the feature list. A schema is an interface; changing it is a migration, not an edit. Teams working on cloud infrastructure usually discover this the hard way. Track the denominator as carefully as the numerator.

Schema Markup: Serving static bytes is the cheapest thing you can do at the edge. Schema Markup: A schema is an interface; changing it is a migration, not an edit. Schema Markup: Track the denominator as carefully as the numerator.