#Time Series
Articles about Time Series — exploring patterns, best practices, and real-world implementations in production systems.
8 posts tagged with time series. ← All posts
Knowing the methods is the easy part; building a forecasting system that's accurate, honest, and maintainable is the real job. This closing post assembles the series into practical judgment — how to choose a method, how to ship forecasts that keep working, and the hard-won lessons (start simple, respect baselines, monitor for drift) that no single technique teaches. It turns the series into something you can actually run.
Knowing the methods is easy; shipping accurate, honest, maintainable forecasts is the job. The complexity ladder (naive → classical → ML → deep, stopping when complexity stops helping), the production realities (honest backtesting, calibrated uncertainty, monitoring for drift and shocks), and the hard-won lessons: start simple, respect baselines, stay humble.
A forecast of "1,000 units next week" is almost useless without knowing whether the real range is 950–1,050 or 200–1,800. The future is uncertain, and a point forecast that hides that uncertainty leads to confidently wrong decisions. Probabilistic forecasting predicts the distribution of outcomes, not just a single number — and for most real decisions, that uncertainty is more valuable than the point estimate itself. This post is about forecasting honestly.
A point forecast hides the thing decisions need: how uncertain it is. Probabilistic forecasting predicts the distribution — prediction intervals, quantiles — via classical analytic intervals, quantile regression, or simulation. Uncertainty grows with the horizon, and calibration checks whether your stated confidence is honest.
Deep learning conquered images and language, and it's made real inroads into forecasting — RNNs, then transformers, then specialized foundation models for time series. But forecasting is also where deep learning's dominance is most contested, because simple classical methods keep holding their own. This post covers the deep-learning approaches to time series, what they're genuinely good for, and the honest, humbling reality of when they actually beat the simpler alternatives.
Deep learning made inroads into forecasting — RNNs/LSTMs, temporal CNNs, transformers, and emerging time-series foundation models — and genuinely shines with many long related series and complex multivariate dynamics. But the humbling reality: for individual modest-length series, classical methods and simple ML often match or beat it. Not a default.
When classical methods aren't enough — many related series, rich external drivers, complex nonlinear patterns — you can bring the full machine-learning toolkit to forecasting. But you can't just feed a time series to a standard model; you have to reframe forecasting as a supervised learning problem through the right features. This post is about that reframing, where ML genuinely helps, and the time-specific traps that make it easy to get wrong.
When classical isn't enough — many series, rich drivers, complex patterns — reframe forecasting as supervised learning via lag, rolling, calendar, and driver features, then train (often) gradient-boosted trees. Where ML beats classical (global models across many series), and the time-specific traps: feature leakage, awkward multi-step, and trees that can't extrapolate trend.
The single most common way to build a forecaster that looks brilliant and fails in production is evaluating it wrong — and time-series evaluation is riddled with ways to accidentally let the future leak into the past. Getting evaluation right, through proper backtesting that respects time order, matters more than the choice of model. This post is about measuring forecast quality honestly, which is the skill that separates real forecasters from people who fool themselves.
The #1 way to build a forecaster that looks brilliant and fails in production is evaluating it wrong. Why random train/test splits are catastrophic (future leakage), how backtesting (walk-forward validation) respects time order, and why you must always compare against naive baselines. Evaluation matters more than the model.
Before neural networks, two families of methods dominated forecasting for decades — and they still win surprisingly often. Exponential smoothing and ARIMA are the classical workhorses: well-understood, fast, interpretable, and shockingly hard to beat on many real series. This post explains both without heavy math, and makes the case that for a lot of forecasting, the right answer is still a classical model, not a deep one.
Before neural networks, two families dominated — and still win surprisingly often. Exponential smoothing (weighted memory of the past; Holt-Winters) and ARIMA (modeling autocorrelation directly). Why classical methods remain state-of-the-art for much real forecasting (strong on limited data, fast, interpretable, hard to beat — the M-competition result).
Almost every time series, however complicated it looks, is a combination of a few simple components: a long-term trend, repeating seasonal cycles, and irregular noise. Decomposition is the act of pulling them apart — and it's the single most clarifying thing you can do with a time series, because once you see the components, both understanding and forecasting become far easier. This post is about the anatomy of a time series.
Almost every series is trend + seasonality + noise (or their product). Decomposition pulls them apart — the single most clarifying thing you can do — revealing what you're predicting, how predictable it is (signal-to-noise), how to transform it, and which method fits. The foundation under every forecasting method.
Forecasting the future from the past is one of the oldest and most valuable things data can do — predict demand, traffic, revenue, load, prices. But time-series data breaks the assumptions most machine learning is built on, and treating it like ordinary data is the fastest way to build a forecaster that looks great in testing and fails in production. This series builds forecasting from first principles, starting with why time is different.
Forecasting the future from the past is one of data's oldest, most valuable jobs — but time-series data breaks ML's i.i.d. assumption (order matters, observations are dependent, the data is non-stationary). Why that dependence makes forecasting both possible and hard, and the vocabulary (trend, seasonality, noise, stationarity, horizon).
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.