Josh Freeman

That Didn’t Take Long

January 02, 2012 at 01:31pm by Scott   •  6 Comments »

I said last month that Raheem Morris would not get fired after the season because it would show a lack of conviction on the part of the Glazers and their dedication to the youth movement.

Okay, I wrote that line and then had to leave for a little while. When I came back, Raheem had been fired. So I need to come up with a different entry, which I will do shortly. In the meantime, your thoughts and predictions in the comments.

6 Comments to “That Didn’t Take Long”

mr.smith

mr.smith (January 02, 2012 at 01:37pm:

No comment

manbearpig

manbearpig (January 02, 2012 at 02:03pm:

I don’t know what to think. I feel like they are starting all over again. I want some continuity. How Dom gets a pass I have no idea. I know he’s hit on some draft picks but let’s look at some obvious fails. Cut Brooks, sign Ward, extend Black, miss an astounding amount of chances at key free agents this past off season. I know this team is going to look very different next year. I still think Freeman can be the fanchise qb the Bucs have needed, I just hope the offensive carousel of coaches and coordinators he’s having to deal with won’t stunt his growth. I’ve been reading a lot of message boards today and the pure delight people are showing about Raheem being fired is disgusting to me. I keep reading shit like “look at the 49ers”, “bring on Cowher”. Give me a fucking break with that shit….
Having to basically start over in the NFL is not good news. I’m all for being positive and hopeful but I’m not an idiot either.

Matt Price

Matt Price (January 02, 2012 at 02:19pm:

Raheem was in way over his head and the more the players claimed to love him but then refused to actually play, the more impossible it became to keep him.

And then he added to that by saying really stupid things like talking about whether or not he would keep his job is for “mental midgets.” There was no way they could keep him after the clusterfuck of his latest set of press conferences.

Plus, frankly, this team shit the bed so consistently in the last few weeks that I honestly don’t think I’ve ever seen any worse team in the NFL. They could have lost each of the last 3-4 weeks by 100 points if the other teams didn’t let up.

Louie

Louie (January 02, 2012 at 02:28pm:

Morris had to be fired. Nobody can survive 10 straight losses to end a season — especially one with 5 straight blowouts. Let’s just hope the Glazers are more serious this time and hire a qualified head coach who can get this train wreck turned around quickly.

@manbearpig, I’m with you, I don’t know how Dom survived this abortion. He’s made a lot of mistakes and his draft picks aren’t looking that great. Of course, poor coaching could be holding those guys back.

Finally, it will be interesting to see where Morris lands. I wish him the best, but with his performance as DC, I don’t see how he can get anything other than a DB coaching position. It’s going to take him a while to resurrect his resume.

cubsandbucsfan

cubsandbucsfan (January 02, 2012 at 03:08pm:

I have been saying for some time here that Raheem had to go, despite the claims of some players-he just couldn’t get them to produce for him.

But having said all that and watching Turner look like a hall of famer yesterday, I am left with this question…was Ruud better than we thought and was it a mistake to let him go and start Foster somewhere else? Was that the beginning of the end? Didn’t Steve White love Ruud and continually defend him? Maybe we will never know.

BaldBuc4055

BaldBuc4055 (January 02, 2012 at 04:44pm:

I’ve defended Raheem, but when you lose 10 in a row, most of them in horrifying fashion, a move had to be made. If the Bucs had been competitive in those losses, he might have stayed. Keeping him around would’ve been like saying, “The train wreck that just took place is perfectly acceptable.” I just don’t know who they’ll hire. I wonder how many delusional people will be calling for the team to hire Bill Cowher, as we know that’s not gonna happen.

Comment on this post:

You must be logged in to post a comment.