Jump to content

Dr. Who

Community Member
  • Posts

    6,885
  • Joined

  • Last visited

Everything posted by Dr. Who

  1. There's no way in Hades Beane would take 3 WRs in a row. McD would go ballistic, and Cowing at #99 makes no sense with the holes on D. It's very unlikely Beane would take WR with the first two picks, though I think Thomas and Legette would be an outstanding start to the draft. Here's one that goes heavy on D after the same first two. 28. Brian Thomas Jr. WR LSU 60. Xavier Legette WR South Carolina 99. DeWayne Carter DT Duke 128. Javon Solomon EDGE Troy 158. Tykee Smith S Georgia 161. Keith Randolph Jr. DT Illinois 197. Jaylon Carlies S Missouri 201. Sundiata Anderson EDGE Grambling State 205. Garret Greenfield OT South Dakota State 245. Kendall Milton RB Georgia
  2. Volume II of Iain McGilchrist's The Matter with Things. It's really quite brilliant, though hard to categorize. Part neurological science, part philosophy and cultural criticism.
  3. I'm afraid to respond and start an epidemic of down turned thumbs. Sorry, I missed the witticism. Distracted by a book I am trying to read through on a rare Monday off.
  4. It was just a joke, but have fun with that.
  5. Just gave you the "thumbs down" for fun. I agree about the preferences.
  6. Yeah, I just pointed out that in a mock, I took DT in the second, and S in the third, with 2 DT, 1 Edge, and 2 S each selected in the draft as a whole. There's no way FA will cover all the defensive holes. Hopefully, it does enough to provide the capacity for some flexibility in what is prioritized in the draft. All the same, I expect as I have said repeatedly now, WR, DT, and S to be the first three picks. Had to edit, as I went back and saw I only took 1 Edge. It's not a great draft at the position. Still, that is the most plausible path. All I add is that if a really good WR falls to #60, even if we grabbed one in the first, I'd like to think Beane could find a way to take advantage, and employ the rest of the draft to supplement the D. Whether or not that is actually possible is another matter.
  7. I just put a mock in the simulator thread. I think it's reasonable, though obviously just playing out various possible scenarios. No doubt the valuation of specific players is going to change a lot, and the actual boards of NFL teams will doubtless differ greatly from these simulator lists. It goes WR, DT, S, DT, WR, S, Edge, RB, OT, WR. In short, it follows the most likely heuristic based on need and past proclivities at OBD. Regardless, I expect Beane will find a way to finagle the cap sufficiently to bring back enough vets to lessen overall dependence on rookies.
  8. Tiny trade back with Detroit that allowed a move up in the third. 29. Brian Thomas Jr.WR LSU 60. T'Vondre SweatDT Texas 73. Cole BishopS Utah 128. DeWayne CarterDT Duke 158. Jacob CowingWR Arizona 161. Jaylon CarliesS Missouri 197. Mohamed KamaraEDGE Colorado State 201. Ray DavisRB Kentucky 205. Garret GreenfieldOT South Dakota State 245. Marcus Rosemy-JacksaintWR Georgia
  9. I believe Rachad Wildgoose is currently a free agent. We really need to draft Storm Duck and at least get Wildgoose on our practice squad. I'm not sure how that benefits us, but my poetic sense intuits positive cosmic karma implications. Not enough attention is given to the possibility of puns based off of the names of potential professional athletes.
  10. You have to be willfully obtuse to fail to recognize that Beane has not invested at WR early in a manner commensurate with positional value. He's been counting on Josh Allen elevating mid-level picks and modest free agents for the most part. It's not a sound strategy.
  11. He can post a picture of Taylor Swift on IG for all I care. He's not going to walk away from a big payday, and I don't think he has enough trade value to be able to force his way out if that were his inclination.
  12. I just don't think Diggs is tradeable for that kind of value given his age and contract. I am still inclined to go WR in round 1 and again early. If the right player was there in the second, I would do it, even if that means risking having some holes on D. But I'd be shocked if Beane does that. I think he will go WR early, then DT and S, and then in a deep draft, maybe take another WR in the fourth. (And to be clear, that is also a rational plan.)
  13. My surmise is he takes time to build up to that speed. If he runs well at the Combine, I can't see how he isn't a lock for the first. One of the things I like about him is he has very reliable hands. It's a big plus.
  14. I like him more than most here. Some of those whose opinion I value don't see him as a first rounder. I guess that is because he lacks explosive speed. He's definitely someone I would consider at #28.
  15. I think there's a pretty good chance he will go in the first, actually. We might take him at #28.
  16. I understand your argument, and I did not interpret your view as anti-WR. I believe you can probably get a few decent DTs at #99 and later. I think you can get a pretty good S later as well. Because of the quality at WR, I am inclined to get multiple players at the position in this draft. I would gamble I could get decent rookie replacements for the D later in the draft. DT doesn't have an elite one I would "have to have" in the first, but there are a few who are round 2 and 3 candidates. I think there are quite a few who will still be there on day 3. There are a bunch of safeties I like who will be gone before #99, so if I want one of that group of about five, I think I have to move up from my third rounder to ensure I get one of them. (#60 is too rich a cost, in my estimation.) I also think I can wait till the 4th to get a reasonable safety. If I end up trading my 4th to move up earlier for a WR, I think I can package a fifth and some of my sixths to get back into the 4th. Lots of different ways it could play out.
  17. Yes, it's just speculative, and a lot can change, and there's a decent chance both teams miss out on WR4.
  18. I did begin by contextualizing the Chiefs' move as "supposedly" and that Elam was our "likely" target, which is meant to indicate surmise, rather than declarative fact. Regardless, I don't think it is wrong to suspect the Chiefs will be interested in the same type of WR as we are looking for, nor that they have an acquisitive habit of moving up in the draft to get the player they want. It would be foolish to stand pat and expect them not to get ahead of you if there is a specific WR you want. If there are a group of relatively equal rated players on your board, that concern goes away.
  19. Well, I recollect @GunnerBill making the argument otherwise, and I thought he had some inside info that confirmed such, but I may be mistaken on the latter. It was just a joke, but I got a green checkmark. There's no point in telling a joke if you have to explain it.
  20. The straw man is the claim that lots of folks who are clamoring for an elite WR believe that acquiring such are saying that holes on D are nullifed by that fact. It's literally the first sentence. If you think that after the tier 1 top 3 WRs, that all those others are in the same grouping, then it doesn't matter which of them you get, and there's no point in blocking the Chiefs from a "tier" with numerous players in it. For certain, one of them is likely to be there for the Chiefs, no matter what you do. My view differs, so the strategy differs. I specifically think Thomas is better than the rest, and I would calculate on that basis.
  21. Well, that is just a surmise. We both apparently wanted a CB. McDuffie has short arms, and his metrics don't match up with what McD's defenses typically look for.
  22. Ah, well, I also don't want them to get Mims, who might be there for them. In fact, I don't think they should be allowed to draft any players.
  23. Sorry, but that's a straw man. I don't think it is a common argument that finding a WR with elite potential means the holes on D don't matter. What folks remember as terribly frustrating is that after spending a ton of draft capital and FA investment on D, the results were consistently disappointing in the post-season. Granted, injuries played a huge role, and I believe we could have a ring this year with better fortunes on that front. Nonetheless, my view is you are replacing largely mediocre players on the DL. Jones is good, but long in the tooth. Epenesa finally became a solid addition in his contract year. The rest can walk. It's not a great year for edge players, and usually isn't. Those are rare birds. Beane will likely bring in a vet Safety, they don't command high dollars in free agency, and it's a buyer's market at the position this year. If you are looking for serviceable DL, you can find them in the middle rounds. There's enough wiggle room to move up. I don't think Beane should be so constrained by the cap that he needs to proceed as if he can't sign free agents, and also can't move picks to maneuver beyond the odd fifth or sixth rounder. And it's possible he won't have to move, or move much. The broader argument is that the WR room needs to be replenished for the overall flourishing of the team. Our offense should be more potent with Josh Allen at qb, and if that happens, it makes the job of defense that much easier. The D can afford to be aggressive if the other team is frequently playing catch-up, and the opponent becomes much more predictable. The talent this year is stacked at WR, so need and opportunity make a serendipitous match.
  24. A fifth might move you up one spot. I have Rice and Polk as second round targets. Seems like Legette may be available then, too. The rest you mention are probably first rounders. I am willing to pay more, including possibly something from 2025, to keep the Chiefs from grabbing Thomas, who I think is WR4 in this draft.
  25. Because the Chiefs are smart, and have proven to be tactically clever. The price they paid us to get Mahomes was light, relatively speaking. And then they supposedly jumped us to grab McDuffie, though I agree with GunnerBill that Elam was our likely target. Regardless, KC wants the same type receiver as we do, and they would also like to prevent us from getting that player, so you have to be wary of that.
×
×
  • Create New...