Run one-on-ones the report owns, splitting career growth from status, with notes that compound. Use when establishing 1:1 practice as a manager or getting more from 1:1s as a…
Make switch and match statements provably total so adding a case forces every site to handle it, with no default that hides the gap.
Draw honest conclusions from samples using hypothesis tests, confidence intervals, and significance read correctly.
Move between API versions or providers without downtime, using parallel running and staged cutover. Use when a provider deprecates a version or you are replacing a service.
Explain the failing code line by line in writing until the sentence you cannot finish exposes the false assumption.
Run a lean startup team of agents (builder, marketer, analyst) through one disciplined weekly loop of ship, promote, and measure.
Give a coding agent the right files and background at the start of a task, so it works from the real system rather than from assumption.
Share one physical GPU across several small workloads using MIG, MPS, or time slicing, and pick the mode whose isolation matches the risk.
Virtualize long lists so only visible rows mount, with correct handling of dynamic heights and scroll anchoring.
Connect MCP servers into an application with lifecycle management, capability negotiation, and graceful degradation when a server is unavailable.
Redistribute work across desks and workers as load shifts, so one bottleneck does not stall the company while others idle.
Keep and present document history so users can see what changed, who changed it, and restore safely. Use when edits are shared or when accidental loss must be recoverable.
Walk hierarchies and graphs with recursive CTEs, with a termination condition and cycle protection so the query ends.
Maintain a living register of business risks with agents that surface new ones, track mitigations, and force stale entries back to a decision.
Build reusable reply templates that speed common answers without making replies feel automated. Use when agents retype the same explanations daily.
Define what gets escalated, to whom, and how fast, so problems reach a decision maker at the right moment rather than too early or too late.
Place assertions where invariants are established or must hold: constructors, public boundaries, and loop bodies.
Fit firmware into kilobytes with static allocation, measured stack sizing, and linker-map budgeting. Use when developing on microcontrollers or debugging overflows and…
Write Kotlin that uses null safety, data classes, and coroutines as designed, with clean Java interop. Use when writing Kotlin or migrating Java code and habits to it.
Make a working local environment reachable in minutes from a clean machine, and keep it close to production.
Keep running discovery rounds until several consecutive rounds find nothing new, rather than stopping at a fixed count.
Frame ML problems around a decision, a measurable target, and honest error costs before touching models. Use when scoping an ML project or reviewing whether one should exist.
Change untested legacy code safely using characterization tests, seams, and the sprout method. Use when you must modify code that has no tests and you cannot prove your change is…
Lower the cost of a first contribution with a working setup, a clear scope, and a fast review so people come back.
Understand unfamiliar code quickly by tracing real execution paths rather than reading files in order.
Send at times that respect the recipient's local hours and working pattern, deferring anything non-urgent. Use when notifications reach people at night or on weekends.
Operate as a mobile engineer who plans around release trains, a real device matrix, and app-store rules that a web engineer never faces.
Recover revenue from failed recurring charges with retries, clear notice, and a graceful path back, without harassing customers.
Assess a high-risk processing activity before it ships, documenting risks, mitigations, and the decision.
Choose names that carry meaning so readers grasp intent without chasing definitions. Use when naming variables, functions, types, or files, or when a name reads as vague.
Write tutorials that take a learner from zero to a working result through tested steps with checkpoints and recovery.
Ship mobile releases through phased rollouts with hotfix paths and a forced-upgrade policy that never strands users.
Staff a pipeline with agents that research accounts, qualify leads against explicit criteria, draft outreach for human sending, and keep the CRM honest.
Build forms with associated labels, identified errors, clear instructions, and autocomplete attributes. Use when creating or auditing forms for accessibility.
Reject excess work deliberately under overload so the system serves some requests well instead of failing all of them.
Prevent server-side request forgery by constraining where a user-influenced URL can make the server connect.
Review model errors by hand, discover failing slices, and decide whether data or model fixes pay more.
Configure rules that stop unreviewed or broken code reaching the default branch, without making routine work impossible.
Choose between processes, threads, and asynchronous concurrency based on isolation, memory sharing, and failure behaviour. Use when deciding how to run work concurrently.
Convert uploaded video into the renditions needed for reliable playback across devices and bandwidths. Use when accepting user video or delivering video that must play everywhere.
Manage a code freeze with a scoped declaration, risk-classed changes, a fast exception process, and a planned thaw.
Understand how files, directories, and durability actually work, so data written is data that survives a crash.
Follow up on unanswered emails effectively: the right timing, adding value, and knowing when to stop.
Choose between local stdio and remote HTTP transports for an MCP server based on trust, deployment, and who runs it. Use when deciding how a server will be hosted and reached.
Have agents argue opposing positions from the same evidence, then synthesize, so the strongest case for each option is heard before deciding.
Understand how gradients flow backward through a network so vanishing gradients, dead units, and exploding losses become diagnosable.
Decide how much reliability to buy, given that each additional nine costs disproportionately more than the last.
Choose between active-passive and active-active multi-region architectures with eyes open to data, cost, and failover reality.
Build dashboards that answer specific questions at a glance, rather than displaying every available metric. Use when a team needs shared visibility into an ongoing situation.
Choose between pulling changes on a schedule and receiving pushed events, based on latency needs, reliability, and control.
Minimize, classify, mask, and expire personal data so any leak or legal request reaches as little of it as possible.
Configure transport layer security with modern protocol versions, automated certificate renewal, and strict transport enforcement.
Work with immutable data in JavaScript through structural updates, readonly types, and freeze where it earns its cost.
Diagnose and fix slow spreadsheets by reducing volatile formulas, whole-column references, and unnecessary recalculation. Use when a workbook takes seconds to respond to an edit.
Keep a retrieval corpus current as source documents change, with incremental updates, deletion propagation, and a stated staleness budget.
Implement OAuth 2.0 and OpenID Connect flows that bind the request end to end with PKCE, state, and exact redirect allowlists.
Suggest queries as the user types, fast enough to feel instant and relevant enough to be worth reading.
Decide what an AI system forgets and when, through expiry, decay, and explicit deletion, so memory stays current and lawful.
Run a team of documentation agents that finds the gaps, drafts the pages, gets them reviewed against the code, and sweeps for staleness on a schedule.
Write benchmarks that do not lie, controlling warmup, isolation, and statistics so the number reflects the code and not the environment.