No projection this week
DJ doesn't have a projection right now — either his team is on a bye, the week's slate hasn't been simulated yet, or he isn't in a position to draw usage. His game log and the usage read below are the real record either way, and this page picks him back up as soon as there's a game to simulate.
How much he's on the field
DJ has averaged 43% of his team's snaps across 20 games. That's a limited role, and it caps everything else on this page. A player on a third of the snaps can't produce like a starter no matter how efficient he is, and the projection reflects the opportunity rather than the talent. Opportunity is the first thing the model reads and the last thing it gives up on — production without snaps is noise, and snaps without production usually corrects.
What kind of defensive lineman he is
DJ has 0.5 sacks and 41 tackles across 20 games. Sacks are the stat everyone quotes and the least stable one on this page — they arrive in bunches, they depend on coverage holding up behind him, and a lineman can win every rep for a month without one. Snap count and pressure rate describe a pass rusher far better than a sack total does, which is why his projection moves less on a big game than you'd expect.
His last 5 games
Over that stretch DJ has 9 tackles. In a sport with seventeen games, a five-game window is closer to an anecdote than a trend — which is why usage, not this, anchors the number.
How the model reads him
The number on DJ is a share of a simulated game. First the matchup: possessions, field position, how each offense is likely to move. Then his slice of it, set by usage rather than by reputation. How those pieces are weighted is ours and gets re-tuned against results; the output is published and graded, which is the half you can check.
What we'd flag
Football's sample sizes are brutal — seventeen games a season means a "trend" is often four data points. Injuries and game script move usage more than talent does week to week, and a blowout can erase a starter's second half.