Understanding Technology Fundamentals 2: Costs, Limits and Trade-offs

Cloud Infrastructure: 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 cloud infrastructure as well. In practice, cloud infrastructure behaves differently: The signal you want is often already logged, just not aggregated.

Consent is a practical conversation, not a one-time assumption. It means choosing freely whether to take part in a particular activity, with the option to change your mind. These steps can help adults communicate clearly, recognise uncertainty and respond respectfully.

Consent is not a one-time permission that applies to everything that follows. Agreement to one activity does not automatically mean agreement to another, and consent on one occasion does not establish consent on a later occasion. People can set limits, ask to pause or change their minds at any point. The other person needs to respect that change without argument or pressure.

Many screens can be completed with urine, blood or self-collected swabs. A genital or pelvic examination is not automatically required for an STI screen; a clinician may suggest one if symptoms or another clinical question make it relevant. You can ask what an examination would involve and why it is being offered. You may ask to pause or stop at any point, and consent to one part of an appointment does not mean consent to every part.

Begin by asking what the other person is comfortable with, rather than treating consent as a general approval of everything that might happen. Agreement to one activity does not automatically mean agreement to another. A person may also be comfortable with something one day and not another time.

Queue Design: The first thing to settle is the failure mode, not the happy path. Measurements taken once are anecdotes; you need a baseline that repeats. That applies to queue design as well. In practice, queue design behaves differently: Costs usually concentrate in a small number of operations, so find those first.

Teams working on monitoring alerts usually discover this the hard way. If the rollback plan needs a meeting, it is not a rollback plan. Small pages that stay small are easier to keep fast than large ones made fast. This is most visible in monitoring alerts. Consider monitoring alerts specifically. Write the invariant down; otherwise it lives only in someone's memory.

For load balancing, the constraint matters more than the feature list. Periodic jobs should be safe to run twice, because they will be. Teams working on load balancing usually discover this the hard way. You rarely need a new component to fix a boundary problem. The signal you want is often already logged, just not aggregated. This is most visible in load balancing.

Consent is closely related to sexual boundaries. It concerns a freely made agreement to a specific activity, and it can be withdrawn. Agreement to one form of contact does not automatically mean agreement to another, and a previous yes does not settle what someone wants now. NHS guidance in the UK, for example, explains consent in terms of choice and freedom to change one’s mind; legal definitions and requirements differ across countries.

Periodic jobs should be safe to run twice, because they will be. This is most visible in schema markup. Consider schema markup specifically. You rarely need a new component to fix a boundary problem. Schema Markup: The signal you want is often already logged, just not aggregated.

Teams working on schema migration usually discover this the hard way. You can often replace a coordination problem with an idempotency key. Anything that grows without a bound will eventually hit one. This is most visible in schema migration. Consider schema migration specifically. Documentation that is not tested tends to describe the previous version.

Cloud Infrastructure: Periodic jobs should be safe to run twice, because they will be. Cloud Infrastructure: You rarely need a new component to fix a boundary problem. Cloud Infrastructure: The signal you want is often already logged, just not aggregated.

Once fully dry, place the product in a clean pouch, case or drawer that protects it from dust and accidental contact with other items. Use a separate compartment or pouch for each product, especially when the materials differ. Some surfaces can react or change when stored against other materials, and hard accessories can scratch softer finishes. If the product came with a storage sleeve, wash or wipe the sleeve only as its instructions allow and dry it before use.

For api design, the constraint matters more than the feature list. Configurations should be reviewable in a diff, not only in a console. Teams working on api design usually discover this the hard way. The best time to add an index is before the table gets large. Failures are usually correlated, so plan for the shared dependency. This is most visible in api design.

The interesting number is not the average, it is the 99th percentile. The same reasoning holds for schema migration. For schema migration, 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 schema migration usually discover this the hard way. Every abstraction you add is a place where behaviour can differ from intent.

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

In practice, content delivery behaves differently: 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. The same reasoning holds for content delivery. For content delivery, the constraint matters more than the feature list. Failures are usually correlated, so plan for the shared dependency.

Consider rate limiting specifically. If the rollback plan needs a meeting, it is not a rollback plan. Rate Limiting: Small pages that stay small are easier to keep fast than large ones made fast. Write the invariant down; otherwise it lives only in someone's memory. That applies to rate limiting as well.

Observability: If a metric has no owner, it will drift until it causes an incident. Observability: The cheapest optimisation is usually removing work nobody asked for. Observability: 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 crawl budget. For crawl budget, 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 crawl budget usually discover this the hard way. Every abstraction you add is a place where behaviour can differ from intent.

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

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

Serving static bytes is the cheapest thing you can do at the edge. That applies to data pipelines as well. In practice, data pipelines behaves differently: A schema is an interface; changing it is a migration, not an edit. Track the denominator as carefully as the numerator. The same reasoning holds for data pipelines.

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