All Skills
25,835 skills
snoodleboot-io Iac Best Practices
State is the map between your code and real resources.
2
snoodleboot-io Slo Sli Definition
**SLO (Service Level Objective):** What we promise (99.9%)
2
snoodleboot-io Test Mocking Rules
Comprehensive guidelines for when and how to use mocks, stubs, and fakes in tests
2
snoodleboot-io Testing Strategies
Three shapes get argued about as if one were correct.
2
snoodleboot-io Feature Engineering
Cardinality and model family jointly determine the encoding.
2
snoodleboot-io Dimensional Modeling
**Structure:**
2
snoodleboot-io Feature Store Design
The pitch is often "a central place to store features," which undersells it into
2
snoodleboot-io Idempotency Patterns
**Pattern:**
2
snoodleboot-io Root Cause Five Whys
1.
2
snoodleboot-io Test Data Strategies
These three are not interchangeable, and picking the wrong one is the root of a
2
snoodleboot-io Code Review Practices
The single highest-leverage convention in code review is prefixing every comment
2
snoodleboot-io Edge And Cdn Delivery
A CDN is a cache that obeys your origin's instructions.
2
snoodleboot-io Mlops Pipeline Design
Software CI assumes a git sha plus a lockfile determines the build.
2
snoodleboot-io Problem Decomposition
A stakeholder asks to make search faster.
2
snoodleboot-io Flaky Test Remediation
A flaky test is one that produces different results on unchanged code and an
2
snoodleboot-io Model Interpretability
"Make it interpretable" is four different requests.
2
snoodleboot-io API Versioning Strategy
Versioning exists because you cannot deploy your clients.
2
snoodleboot-io Message Queue Selection
Messaging systems fall into three fundamental shapes, and most bad choices come
2
snoodleboot-io Object Storage Patterns
Almost every object-storage mistake comes from carrying filesystem instincts into
2
snoodleboot-io Python Typing And Async
Type hints are checked by a separate tool (`mypy`, `pyright`), never by CPython
2
snoodleboot-io Cloud Migration Strategy
There is no such thing as "the migration." An estate is a collection of
2
snoodleboot-io Cloud Provider Tradeoffs
Compute, object storage, block storage, a managed relational database, a message
2
snoodleboot-io Component Design Systems
A design system has three token layers, and conflating them is what makes systems
2
snoodleboot-io Multiagent Orchestration
Run a genuinely-parallel multiagent implementation with detailed guidance - plan, gate on environment, spawn subagents concurrently, aggregate, and debug/retry
2
snoodleboot-io Nosql Database Selection
Relational modelling lets you defer query design: normalize the entities, and
2
snoodleboot-io Performance Optimization
The instruction to profile before optimizing survives because intuition about
2
snoodleboot-io Verbose
API Security (Verbose)
2
snoodleboot-io Batch Vs Realtime Scoring
The choice is not about scale or sophistication.
2
snoodleboot-io Data Validation Pipelines
A validation *boundary* is any point where data crosses from a system you do not
2
snoodleboot-io Technical Debt Management
Debt that exists only in engineers' heads cannot be prioritised, funded, or
2
snoodleboot-io Technical Decision Making
The single most useful question before analysing anything is: *what does it cost
2
snoodleboot-io Time Series Preprocessing
Almost every downstream bug traces back to an index that was assumed regular and
2
snoodleboot-io Distributed Caching Design
The default, because it fails open: when the cache is unavailable, reads still
2
snoodleboot-io Incident Timeline Creation
**Server Logs:**
2
snoodleboot-io Incremental Implementation
Comprehensive guide for implementing code incrementally following established patterns, conventions, and quality standards
2
snoodleboot-io Slowly Changing Dimensions
**When:** Not important (contact info)
2