Build and ship a small site that loads fast, reads well, and can be updated, choosing the simplest stack that fits.
Stop user-supplied path components from escaping the directory you meant to confine them to. Use when a filename, path segment, or archive entry from outside the program is joined…
Understand the layers between a request and its response, so latency, connection failures, and timeouts can be attributed to the right layer.
Structure game loops with fixed-timestep simulation, interpolated rendering, and spiral-of-death protection.
Make immutability the default so aliasing bugs turn into compile errors or no-ops instead of action at a distance.
Use window functions to rank, compare to neighbours, and compute running totals without collapsing rows or self-joining.
Replace opaque boolean flags with named enums or split functions so call sites read without the definition open.
Combine result sets with UNION, INTERSECT, and EXCEPT, and know when a join or an exists clause is the better tool.
Reach battery-life targets through sleep-state budgeting, duty cycling, and measured (not estimated) current draw.
Choose batch size understanding its effect on gradient noise, memory, throughput, and generalisation, and adjust the learning rate with it.
Enforce and revoke access on live connections so a permission change takes effect immediately rather than at the next page load.
Plan scalability from a load model and bottleneck math, designing for realistic growth without premature over-engineering.
Deliver webhooks with signatures, retries, and ordering rules consumers can actually build against. Use when adding webhooks to a product or hardening delivery and verification on…
Format numbers, dates, currency, and units by locale using the platform formatter rather than string templates.
Diagnose layout, stacking, and overflow bugs by isolating the failing rule with devtools instead of guessing.
Operate as a backend engineer who designs stable API contracts, guards data integrity, and ships services that are operable on day one.
Force the thread interleavings that expose races by using barriers, stress loops, and linearizability checks instead of hoping the scheduler hits them.
Make message consumers safe under at-least-once delivery with natural idempotency or a transactional dedup store.
Audit third-party packages by pinning resolved versions, scanning against advisory databases, and catching malicious lookalikes before install.
Produce campaigns with agents that research the audience, draft variants against a brief, check claims and brand voice, and leave publishing to a human.
Patterns and strategies for cache invalidation - one of the two hardest problems in computer science.
Write decorators that preserve signatures and compose cleanly, including parameterized and class-applied forms.
Drive API development from an OpenAPI spec as the contract, with linting, codegen, and drift detection.
Run a game day that injects a real failure on purpose under safety rails, then captures what monitoring, runbooks, and responders actually did.
Explain something to someone with no background, without condescension and without jargon that quietly requires prior knowledge.
Improve RAG answer quality by reranking retrieved candidates so the most relevant chunks reach the model.
Find dependency cycles between modules and break them with layering, interface extraction, or dependency inversion.
Operate as a principal architect who owns the boundaries between systems, curates the technology set, and spends veto power sparingly.
Write a north-star architecture document that sequences migrations and guides decisions without pretending to be a roadmap.
Join data between sheets reliably using modern lookup functions, handling missing matches and duplicates explicitly. Use when combining data from more than one table.
Read research papers efficiently in passes, separating claims from evidence and assessing reproducibility.
Coalesce a flood of small operations into fewer larger ones with batch windows, debounce, or throttle, chosen by whether you need the last event or a steady rate.
Expose data through MCP resources with stable URIs, useful listings, and sizes that fit a context window. Use when an agent needs to read data rather than perform an action.
Decide what you are, who for, and against what alternative, then say it in words customers use. Use when nobody can explain the product in one sentence or the same product is…
Use Tailwind-style utilities with discipline, extracting components at the right threshold and keeping class lists readable.
Assert hard-to-specify output by reviewing a human-readable snapshot once, approving it, then failing on any later diff.
Write subject lines that get emails opened and found later: specific, honest, and action-signaling. Use when the subject line decides whether your email is opened, prioritized, or…
Interview as an Amazon-style bar raiser who holds an independent veto and judges each candidate against the long-term hiring bar.
Catch fencepost bugs by writing down the boundary convention and testing the endpoints instead of the middle.
Handle plurals, grammatical gender, and agreement using locale plural categories rather than an if-else on count.
Use CTEs to name intermediate steps so a complex query reads as a sequence rather than a nest, and know when they cost performance.
Run a security audit as agents that map the attack surface, review each surface in parallel, skeptic-test every finding, and assemble one report.
Lay out the network for distributed training so collectives run on the fastest link that spans them, using NVLink, InfiniBand, and topology-aware placement.
Make mobile forms and controls fast to use with correct keyboards, reachable touch targets, and restrained haptics.
Decide rollback versus fix-forward, handle migrations safely, and rehearse rollbacks so they work under pressure.
Group and aggregate correctly, understanding what GROUP BY collapses, how HAVING differs from WHERE, and how nulls and empty groups behave.
Reason about how model performance improves with parameters, data, and compute, to allocate a training budget sensibly.
Present merge conflicts to users so they can resolve them confidently, rather than resolving silently and losing work. Use when concurrent edits cannot be merged automatically.
Display, store, and reason about money across currencies without rounding errors or implied conversions.
Build multiplayer with an authoritative server, client prediction, reconciliation, and lag compensation. Use when adding networking to a game or fixing rubber-banding and desync.
Grow engineers through goal-anchored mentoring, calibrated stretch work, and questions before answers. Use when mentoring individuals or building a team's growth practice.
Design each handoff between two agents as an explicit artifact contract with a context budget and a rule for what must survive the crossing.
Read a diff for security by tracing attacker-controlled input to dangerous operations and checking every trust boundary it crosses.
Move new users to their first value moment fast by defining activation, instrumenting the funnel, and cutting time-to-value. Use when signups do not become engaged users.
Model warehouse tables with explicit grain, conformed dimensions, and deliberate SCD handling. Use when designing analytics schemas or fixing double-counted metrics and unjoinable…
Improve LCP, CLS, and INP by measuring field data, tracing each metric to its specific cause, and applying the fixes known to move that number.
Choose embedding models and chunking by evaluating retrieval on your own corpus, not by leaderboard rank.
Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.
Comprehensive guide to data quality validation, testing frameworks, anomaly detection, and data observability for production data pipelines
Direct an agent through a refactor in verifiable steps with tests as the safety net, rather than one large rewrite. Use when restructuring code with agent assistance.