06-01-2021, 08:51 AM
(06-01-2021, 04:12 AM)TheLeonardLeap Wrote: I'm ignoring the Seattle game because you specifically said the Baltimore game which you said he did a "damn fine job" at. Only later did you randomly make mention of "Wilson" as some kind of moving goalpost.
The Seattle game was Week 1 of the 2019 season, man. That was 632 days ago. In a year where the Bengals went 2-14 on the backs of the 29th overall/25th scoring (and 32nd rushing) defense.
I'm sorry, but trying to talk up Lou Anarumo with "flashes of brilliance" and doing "damn fine jobs" is just nonsense. He is legitimately just terrible.
My original post, including the Seattle game, which I mentioned first:
I remember after Lou's first game at Seattle being so excited as the defensive line sacked Wilson (a tough tackle) a ton of times and kept them down in yardage as well, but then the following week, SF exploited the lack of outside containment time and time again and it seemed like there were no adjustments and it was just maddening to watch.
I don't know where Lou ranks. He has shown flashes of brilliance (he actually did a damn good job against the Ravens in their first meeting last year) and times where they just look lost. I'm going to give the guy the benefit of the doubt with a better, deeper roster and hope he can start to get some players on his side. I give the Bengals credit for not doing the easy thing and just signing WJIII and Lawson, but going out and signing guys that they feel better fit their scheme. Awuzie (sp?) could end up being a massive bargain over what we were talking about with a franchise tag for WJIII.
My later post that broke down the game on defense:
I wish this game were replayed on the NFL network so you could watch it again. Though painful, you would see that despite doing absolutely nothing on offense, the defense held Baltimore in check for most of the early part of the game and at the very least kept Cincy in the game:
Bengals punt, Ravens get the ball at their 20 and get a FG
Bengals turnover on downs, Ravens get the ball at their 37. Ravens drive the field for a TD
Bengals throw INT, Ravens get the ball on Cincy's 31 yard line. Ravens drive 31 yards (with the help of a Dunlap PF) for a TD.
This is where the game could have gotten completely out of hand. Here is what happened next:
Bengals fumble, Ravens recover at the 50 yard line. Ravens get 4 yards on 4 plays and turnover on downs.
Bengals go backwards 10 yards and punt. Ravens get the ball on their 21.
Ravens get 14 yards on 5 plays and punt. Bengals get the ball on on their 25.
Bengals go backwards 1 yard on three plays and punt. Ravens get the ball at their 30 yard line with 2 minutes to go in the half. We all know where this is going, right?
Wrong, the Ravens throw an INT and Bengals get the ball on their 24 yard line.
The Bengals go 3 yards on 3 plays and use up 22 seconds on the clock and punt the ball back to the Ravens.
The Ravens quickly drive 34 yards and get a FG right before the half (in 51 seconds)
The Ravens next four drives (the rest of the game's possessions in the 2nd half for them) go as follows:
Punt
Punt
FG
[b]Punt.
[/b]
Sorry, I still believe with the talent he had on the roster, he did a damn fine job against the Ravens in their first meeting. The offense did absolutely nothing and seems to get a pass. He kept them in that game against a very strong and versatile offense. The score wasn't indicative of his unit's performance as there was a defensive TD. The Raven's offense scored 20 points. And in one case they got the ball at the Cincy 31 off an INT.