Mlops
265 bites tagged Mlops — interview questions with model answers, and 60-second explainers.
Slash ML Training Costs with Spot Instances
Spot Instances are like flying standby for compute: you get a massive discount but can be 'bumped' if someone pays full price. Use them for ML training jobs that can be paused and resumed. The footgun is using them for tasks that can't tolerate interruption.
NVIDIA CUDA: General-Purpose GPU Computing
CUDA unlocks a GPU's thousands of cores for general-purpose computing, not just graphics. It's key for accelerating tasks like machine learning by running the same operation on massive datasets in parallel.
Configuration as Code: Version Control for Your Settings
Configuration as Code treats your system settings like source code: defined in files, versioned, and automatically applied. It's used to manage app settings or service credentials across environments, preventing manual errors.
Conda Environments: Isolate Your Project Dependencies
Think of a Conda environment as a separate workshop for each project, with its own tools (packages) and Python version. This prevents dependency conflicts when Project A needs a different library version than Project B.
PMML: The 'Save File' for Machine Learning Models
PMML is like a universal "save file" for ML models, using XML to describe everything needed for prediction: features, preprocessing, and model structure. It enables training in Python and deploying in Java. The footgun: verbose files and partial tool support.
Model Lineage: The Git History for Your AI
Think of model lineage as the `git log` for your AI, tracking every input from data to code that created it. It's essential for reproducing models, debugging failures, and satisfying regulatory audits.
Hydra: Composable Configuration for Complex Apps
Hydra treats configuration like LEGOs. Instead of one monolithic file, you compose small, reusable config pieces for each run. It's ideal for ML experiments where you override settings from the command line.
Model Signature: The API Contract for Your ML Model
A model signature is an API contract for your ML model, defining the exact shape and types of its inputs, outputs, and parameters. It's used by platforms like MLflow to validate requests and enable safe deployments. Forgetting it will block model registration.
MLflow Tracking: A Lab Notebook for Your ML Experiments
Think of MLflow Tracking as a lab notebook for your models. It logs parameters, metrics, and artifacts for every training run, letting you compare results and find the best model. The main footgun is forgetting to set a remote server, trapping logs locally.
TensorBoard: The Dashboard for Your ML Model
TensorBoard is the dashboard for your ML model, showing what's happening inside during training. It tracks key metrics like loss and accuracy, visualizes the model's structure, and helps you debug performance. The main footgun is not logging the right data.
Entity Embeddings: Smart Maps for Categorical Data
Entity embeddings turn categorical data like user IDs into dense vectors, creating a "map" where similar items are neighbors. This is used in neural networks to handle high-cardinality features efficiently, avoiding the memory bloat of one-hot encoding.
Feature Governance: Taming Your ML Inputs
Feature governance treats ML inputs like code, enforcing consistency from training to production. It's a central system of record for what data your models see. This prevents training-serving skew.
Point-in-Time Correctness: Avoiding Data Leakage in ML
A point-in-time correct join is a time-traveling lookup for ML features, grabbing the most recent values known *at the time of an event*. It's vital when building training data from feature tables that update at different rates to prevent data leakage.
Feature Definition Language: Define ML Features as Code
A feature definition language is like infrastructure-as-code for ML features. It lets you define a feature's source and schema once, then use it for both offline training and online serving, ensuring consistency.
Feature Backfilling: Populating Historical Data for ML
Feature backfilling computes a new feature's values for historical data. It's how you generate a complete training dataset after defining a new signal, like a user's 7-day purchase history. The footgun is using future data, causing data leakage.
Online vs. Offline Feature Serving: Two Speeds for ML Data
Offline serving provides large batches of historical data for model training; online serving provides low-latency features for live predictions. This dual system in a feature store prevents training-serving skew, ensuring model consistency from lab to…
Feature Hashing: The Hashing Trick for ML
Feature hashing turns features into vector indices without a lookup table, trading perfect accuracy for speed and memory. It's used for high-cardinality data like user IDs or in online systems.
Data Augmentation: Getting More from Your Data
Data augmentation creates 'new' training data by making small, realistic changes to your existing data. It's used to fight overfitting in ML models when a dataset is small, teaching the model to generalize rather than memorize.
DVC: Git for Data and ML Models
DVC extends Git to version large data files and models without bloating your repo. It stores small pointer files in Git that reference large files in cloud storage.
Great Expectations: Unit Tests for Your Data
Great Expectations brings unit testing to your data, letting you assert what a dataset should look like. It validates data within a pipeline, preventing bad data from corrupting models or reports.
Data Schema Evolution: Changing Your Data's Blueprint
Schema evolution is like updating a building's blueprint while it's occupied. You must change your data's structure without breaking apps or losing data. It's key for adding features that need new DB columns.
ELT: Load Raw Data, Transform in Place
ELT flips the data pipeline: load raw data first, then use the data warehouse's own power to transform it. It's used in ML feature pipelines. The footgun is assuming it's ETL; with ELT, the transformation logic is coupled to the warehouse's SQL engine.
Data Labeling: Teaching Machines What to See
Data labeling gives raw data meaning so a machine learning model can learn. It's used to prepare datasets for tasks like object detection in images or sentiment analysis in text. The footgun: low-quality labels directly limit your model's performance.
ML Metadata: The Logging Layer for ML Pipelines
ML Metadata is the logging layer for your ML pipeline, tracking every dataset, hyperparameter, and model version. It's crucial for debugging failed runs by tracing a model back to its exact data.
Get Mlops bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.