-
Hybrid search: combining BM25 keyword and dense vectors
Dense vector retrieval is excellent at matching meaning.
-
Fine-tuning vs LoRA vs prompting: choosing the cheapest path that works
The cheapest model-customization strategy is not the one with the smallest training invoice. It is the one that reaches the required quality level with the lowest total lifecycle cost.
-
Forecasting with XGBoost: turning a time series into a supervised problem without cheating
XGBoost does not know what a time series is.
-
RuleFit and skope-rules: mining crisp rules out of a trained ensemble
Tree ensembles are excellent at discovering nonlinear thresholds and feature interactions. A boosted classifier can learn that a large order is suspicious only when the account is young, or that a dis
-
Keeping an XGBoost model honest: drift monitoring, champion/challenger, and retraining cadence
An XGBoost model can remain perfectly healthy from an infrastructure perspective while becoming operationally wrong. The endpoint still returns 200 OK . Latency stays flat. CPU and memory look normal.
-
Reproducible XGBoost: seeds, pinned versions, and a validation protocol you can defend
A reproducible training run and a trustworthy validation score are related, but they are not the same guarantee.
-
Squeezing more out of XGBoost: feature engineering, custom objectives, and constraints
Once learning rate, depth, regularization, subsampling, and early stopping are sensible, another search rarely creates a step-change. The next gains usually come from changing one of three things:
-
Debugging a boosted model: learning curves, tree dumps, and plots that explain a prediction
A boosted-tree model can post an attractive validation score while still being wrong for the reasons that matter: leakage, an unrepresentative split, a brittle interaction, or one small segment carryi
-
XGBoost pitfalls: the mistakes that quietly wreck a boosted model
A boosted-tree model can look healthy while being wrong in ways ordinary metrics do not expose. It may overfit after the useful trees were built, leak the test set into tuning, scramble columns at inf
-
XGBoost in production: GPU training, out-of-core data, model persistence, and fast inference
Productionizing gradient-boosted trees is not one decision. It is a chain of decisions about compute, memory, serialization, and request handling: