All categories
Business & Operations
Operations, strategy, finance, sales, support, management, and planning
- 35,234
- 1,469
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse business & operations skills
Showing 16,465–16,488 of 35,234 skills
- MinimalDefine metrics precisely enough that two people computing them independently get the same number, and that moving one cannot quietly damage the business.Votes: 0GitHub stars: 2
- VerboseThe single highest-leverage decision is recognizing that most of what teams call "state" is not client state at all.Votes: 0GitHub stars: 2
- MinimalDecide where each piece of application state lives, so you don't end up with a global store that is 80% cached server responses.Votes: 0GitHub stars: 2
- VerboseA stakeholder is anyone whose plans change based on what your team does. That is a longer list than the people in your standup: the PM, the support lead who absorbs the complaints, the partner team building against your API, the finance analyst whose forecast assumes a launch date, the two design-partner customers.Votes: 0GitHub stars: 2
- MinimalKeep the people who depend on your work informed on their terms — impact and dates, not mechanism — so they never have to ask, and never learn of a slip late.Votes: 0GitHub stars: 2
- MinimalCompute per-row values across a set of related rows — rankings, running totals, row-to-row deltas — without collapsing rows or writing self-joins. And name query steps with CTEs.Votes: 0GitHub stars: 2
- VerboseAlways start with EXPLAIN ANALYZE to understand execution: ```sql EXPLAIN ANALYZE SELECT o.order_id, o.total, c.name FROM orders o JOIN customers c ON o.customer_id = c.id WHERE o.created_at > '2026-01-01' ORDER BY o.total DESC LIMIT 100; ```Votes: 0GitHub stars: 2
- VerbosePrioritization arguments are usually capacity arguments in disguise. Start by publishing the real number for the quarter:Votes: 0GitHub stars: 2
- MinimalTurn a list of things everyone wants into an ordered sequence you can defend, and make the cost of every "yes" visible as a specific "no".Votes: 0GitHub stars: 2
- MinimalWrite requirements a stranger could implement and a tester could falsify, so "done" is a fact rather than an argument in review.Votes: 0GitHub stars: 2
- VerboseType hints are checked by a separate tool (`mypy`, `pyright`), never by CPython at runtime. Their value is proportional to how much a tool can prove. Annotate public signatures, return types, and data structures; leave obvious locals bare.Votes: 0GitHub stars: 2
- MinimalInstrument a product so the numbers survive contact with a real question — consistent names, stable definitions, and a source of truth you can bill against.Votes: 0GitHub stars: 2
- VerboseEvery metric encodes an opinion about which mistake hurts. Start from the decision the model drives, then pick the metric that penalizes the costly error.Votes: 0GitHub stars: 2
- VerboseEvery synchronous call does two things beyond transferring data: it adds the callee's latency to yours, and it makes your availability the product of both.Votes: 0GitHub stars: 2
- MinimalFind where a system's latency curve bends, and why, rather than proving it passed a number someone invented in a planning meeting.Votes: 0GitHub stars: 2
- VerboseThe central pattern. Data is encrypted with a short-lived Data Encryption Key (DEK); the DEK is encrypted ("wrapped") by a Key Encryption Key (KEK) held in a KMS or HSM. Only the wrapped DEK is stored, next to the ciphertext.Votes: 0GitHub stars: 2
- MinimalManage the lifecycle of encryption keys — generation, storage, rotation, revocation — so that a key compromise is survivable and rotation does not require re-encrypting the world.Votes: 0GitHub stars: 2
- VerboseThreads do not automatically see each other's writes. The compiler, JIT, and CPU may reorder instructions and cache values in registers, so a write in one thread can be invisible to another indefinitely. The Java Memory Model defines *happens-before*: if action A happens-before action B, then A's effects are visible to B. You get those edges only through synchronization.Votes: 0GitHub stars: 2
- VerboseA severity level is a commitment about response — who wakes up, how fast, and who is told. Write the definitions so that a tired engineer can classify in under a minute, using customer impact rather than technical cause.Votes: 0GitHub stars: 2
- MinimalDecide before the outage who does what, how severity is judged, and when to escalate — so response is a procedure to execute rather than a decision to argue about at 3am.Votes: 0GitHub stars: 2
- Minimal**Idempotent:** Same operation repeated = same resultVotes: 0GitHub stars: 2
- MinimalSearch hyperparameter space efficiently, and get an honest estimate of how the tuned model will actually perform.Votes: 0GitHub stars: 2
- MinimalCoordinate goroutines with channels and `context`, and choose channels vs. mutexes so concurrent code stays correct and leak-free.Votes: 0GitHub stars: 2
- MinimalDefine how much data loss and downtime the business can survive, then choose the cheapest recovery pattern that meets those numbers — and prove it works.Votes: 0GitHub stars: 2