Quote:
Originally Posted by Chargem
My take on this is that generally, people have researched players more that actually might be Chiefs next year, so the positions of actual need for the Chiefs get way over drafted and it makes whoever has the Chiefs job almost impossible.
The Chiefs are not interested in CB/S this year, and oh look loads of them fell.
I don't really see it as ****ing up, I see it as part of the fun of the draft, rubbing my hands together with glee when I see a great talent falling to me because he's not really on Chief's fans radar.
I can understand that this is especially frustrating when you're picking for the Chiefs though. Maybe that explains the terrible record on 1st round picks over the years
|
You're probably correct and maybe I'm just overreacting. I just want it to be realistic. I don't care who falls to the Chiefs, honestly.
I'm not bitching about DE because the Chiefs need one, hell there are plenty to draft this year and I can get one. As I said, there are a few I'm plenty happy with sitting there yet and the chances all 3 are gone at 63 are slim. And it could very well be the group of players and the situation (not taking DE at 31) the Chiefs end up in.
I am complaining because it's not me who's getting screwed or whoever mocks for the Chiefs each year.
Everyone does because we end up creating an unrealistic pile of garbage that has players and positions going to teams that simply will go in another direction in the draft, and certainly won't double down in the top 35 picks.
It's simply not a competition to see who can out-draft the other guy with the best players. If it is, this is my last year. It should be to put some level of thought into what teams have done in the offseason (which is why this shouldn't start until at least after the 1st week of FA), gauge their current and near-future needs beyond just the primary standout need, and draft accordingly with the best players at the right times.