Jump to content
  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

In your opinion, how did we fair in certain areas in comparison to last year?


mbarbour21
 Share

Recommended Posts

These are some issues that I believe we typically had last year and how we faired yesterday in comparison:

- Bridgewater was not making deep throws ↗️(We had one good completion. To be fair, our 0-line is still severely limiting our ability to go deep. I feel like we did see better arm talent though, and it isn't because our QB is unwilling, isn't capable, or is ignoring/not seeing a wide open Moore.)

- No CMC for most of the year ⬆️‼️(This is obviously improved. Maybe a bit too much improved. Most agree we over used CMC and need to find a way to spell him. The season didn't get any shorter, that's for sure.)

- No TE production for the majority of the year 🔂(More of the same. Would have loved to see Tremble get some targets, even if it was from out of the back. Tremble should not come off field for Ricci.)

- Very poor play in the red zone 🔂 (More of the same again. Turnovers, bad throws, getting stuff.....rinse and repeat. Offense did well when they were spread out. Darnold could have crawled in the end zone. Turnover was a stupid fluke play. Hopefully the miscues in the red zone will not be the norm.

- Slye on FGs 🔂 (More of the same yet again. Yes Slye did well for the Texans, but he didn't do well for us. It's very possible he played no better than Santoso if he was still rocking the black and blue.....or the white ice cream uniforms....whatever. In case you have been hiding under a rock, WE PUNTED ON THEIR 33 YARD-LINE.)

- Defense could not execute on 3rd down to save their life ⬆️ (Very much improved! We made them look almost as bad as us on 3rd downs. It was mentioned before somewhere on this site that we would have lost this game last year. This is exactly why we didn't. We got them off the field, and that is refreshing.)

- Defense could not stop the run ⬆️ (I feel like this goes without saying. Last year we would have given up more yards on a single rush TWICE, than we gave up all game. Held them to 45. If this continues and we keep the improved pass rush we are gonna be a force.)

- Raw rookies starting in the secondary ⬆️ (We had a rookie in the secondary, but he def wasn't raw. He gave up that TD late, but that was mostly the result of a perfect pass. They went his way 3 times. Horn balled. Chinn was def an upgrade at the safety position. There just seemed to be one major issue with that completion to Mims. But the unit looked much improved over Jackson/Douglas, Pride, Burris, and Franklin....or whatever group we had most often.

***How do you guys think we faired in the areas we performed poorly in last year?***

  • Pie 5
Link to comment
Share on other sites

I still think Sam is playing pretty similar to Teddy.   I think that is the plan.  Overall, in preseason and week 1 is basically playing with just about 10 yards of field.   I would expect that to continue. 

The offense I don't think completed a single intermediate pass.  10-20 yards downfield.   He did hit Robby deep...but that was the type deep play Teddy would randomly hit too.  Where the WR was just so wide open he would take it.   Then that one crazy DJ toe tap play. 

 

  • Pie 2
  • Beer 2
Link to comment
Share on other sites

2 minutes ago, CRA said:

I still think Sam is playing pretty similar to Teddy.   I think that is the plan.  Overall, in preseason and week 1 is basically playing with just about 10 yards of field.   I would expect that to continue. 

The offense I don't think completed a single intermediate pass.  10-20 yards downfield.   He did hit Robby deep...but that was the type deep play Teddy would random hit too.  Where the WR was just so wide open he would take it.   Then that one crazy DJ toe tap play. 

 

Toxic Teddy ran the offence the way Brady and Rhule want it to be run - attacking teams horizontally with quick passes to keep the chains moving and providing receivers with YAC opportunities. 

One of two reasons why Bridgewater is no longer here is because he refused to hit the deep shots. He can't make that throw Darnold made to Anderson - that was all arm. Much like the Saints O with Brees, the plan is to consistently hit the short completions then, if you overcompensate to defend that, hit you with the shot play. It's absolutely by design - we'll experience lots of Bridgewater deja vu this year - except Darnold will hit those chunk plays. 

  • Pie 6
  • Beer 1
Link to comment
Share on other sites

too. many. fuging. drops. also, when they started creeping back is when i was not seeing cmc involved. We have him, we use him, there's a reason for that. This isn't the NBA, it's the NFL. The main difference in this game than any other last year was CMC and a pass rush. 

Drops are why preseason is important, but people fear getting hurt. You need those reps, not when the regular season starts. a lot of sloppy football across the board yesterday, esp in buffalo. 

  • Pie 1
Link to comment
Share on other sites

6 minutes ago, CRA said:

I still think Sam is playing pretty similar to Teddy.   I think that is the plan.  Overall, in preseason and week 1 is basically playing with just about 10 yards of field.   I would expect that to continue. 

The offense I don't think completed a single intermediate pass.  10-20 yards downfield.   He did hit Robby deep...but that was the type deep play Teddy would random hit too.  Where the WR was just so wide open he would take it.   Then that one crazy DJ toe tap play. 

 

Do you think that is the plan BECAUSE our offensive line isn't good? Or do you think we would still have the same plan if they were better? 

Link to comment
Share on other sites

I agree that the primary improvements were on the defensive side of the ball which shouldn't be shocking given our considerable investments in the defense since Rhule was hired.

I also agree that so far, the offense basically looks the same as last year with the same issues present with Darnold throwing the ball at a higher velocity than Teddy did. Hopefully as he settles in and gets more comfortable we'll see a more dynamic offense. The offense can't just be feed CMC and rely on the QB simply not to lose the game. There has to be more to it than that, particularly with the WRs we have.

  • Pie 2
Link to comment
Share on other sites

It’s impossible to make a judgement after week 1. Go back last year to week 1 when we lost to the raiders, Teddy played about the same as Darnold going up against a much more talented team (on paper at least). We lost 30-34 our D got ran over, as of now vs a bad team our defense looked great, our offense looks about the same.

 

To me it seems like the coaches are micromanaging Darnold, they are scared he’s gonna starting throwing picks. That was the least talented most inexperience secondary we will face all season and mostly dinked and dunked, when we should of been attacking down field.

Link to comment
Share on other sites

39 minutes ago, OldhamA said:

Toxic Teddy ran the offence the way Brady and Rhule want it to be run - attacking teams horizontally with quick passes to keep the chains moving and providing receivers with YAC opportunities. 

One of two reasons why Bridgewater is no longer here is because he refused to hit the deep shots. He can't make that throw Darnold made to Anderson - that was all arm. Much like the Saints O with Brees, the plan is to consistently hit the short completions then, if you overcompensate to defend that, hit you with the shot play. It's absolutely by design - we'll experience lots of Bridgewater deja vu this year - except Darnold will hit those chunk plays. 

I mean, Teddy hit them too when they were as wide open as Robbie was.   That was the only time he pulled the trigger deep. 

you have to be able to attack at the intermediate level.  The offense failed to complete a pass there the entire game.  It was largely just attacking within 10 yard downfield. 

From a passing attack perspective, it was very similar to Teddy IMO.   Which is fine week 1 for Sam.  But we will have to get better.  Especially vs better teams.  Especially the 10-20 range downfield.  Which we haven't shown yet in preseason or week 1 we can really do that.   

The intermediate throws will be what makes or breaks it for Darnold IMO.  That's where it gets hard for him. 

  • Pie 2
Link to comment
Share on other sites

47 minutes ago, mbarbour21 said:

Do you think that is the plan BECAUSE our offensive line isn't good? Or do you think we would still have the same plan if they were better? 

you don't need crazy time to attack 10-20 yards downfield.  

We didn't complete one Sunday.  I think Sam had 1 in the preseason.  And reports out of camp were repeatedly that Sam was going short and it stuck out.   I would assume Sam is just being coached to do that for the time being.  

That was Teddy's DNA. 

 

  • Pie 2
Link to comment
Share on other sites

Setting aside the “deep throws”, the medium and short throws had more zip and urgency than Teddy’s. Teddy’s inability to throw deep wasn’t the only problem, it was his timid decision making and floaters at all levels, as well as throws that were technically catchable but often behind, low or otherwise not accurate.  Darnold had none of those problems outside two or three bad passes. QB has been significantly upgraded this season, based on this game and the preseason game. 

  • Pie 5
Link to comment
Share on other sites

26 minutes ago, JawnyBlaze said:

Setting aside the “deep throws”, the medium and short throws had more zip and urgency than Teddy’s. Teddy’s inability to throw deep wasn’t the only problem, it was his timid decision making and floaters at all levels, as well as throws that were technically catchable but often behind, low or otherwise not accurate.  Darnold had none of those problems outside two or three bad passes. QB has been significantly upgraded this season, based on this game and the preseason game. 

Yeah if Darnold settles into the offense nicely like I think he will, we may have our QB situation solved for a while.  Still need significant investment in the o line though. 

  • Pie 4
Link to comment
Share on other sites

25 minutes ago, JawnyBlaze said:

Setting aside the “deep throws”, the medium and short throws had more zip and urgency than Teddy’s. Teddy’s inability to throw deep wasn’t the only problem, it was his timid decision making and floaters at all levels, as well as throws that were technically catchable but often behind, low or otherwise not accurate.  Darnold had none of those problems outside two or three bad passes. QB has been significantly upgraded this season, based on this game and the preseason game. 

yeah, see, I just can't get down with stuff like that.  QB has been significantly upgraded?  I mean, we can't actually declare that.  

 

  • Pie 1
Link to comment
Share on other sites

2 hours ago, CRA said:

I mean, Teddy hit them too when they were as wide open as Robbie was.   That was the only time he pulled the trigger deep. 

you have to be able to attack at the intermediate level.  The offense failed to complete a pass there the entire game.  It was largely just attacking within 10 yard downfield. 

From a passing attack perspective, it was very similar to Teddy IMO.   Which is fine week 1 for Sam.  But we will have to get better.  Especially vs better teams.  Especially the 10-20 range downfield.  Which we haven't shown yet in preseason or week 1 we can really do that.   

The intermediate throws will be what makes or breaks it for Darnold IMO.  That's where it gets hard for him. 

Bridgewater can't make that throw.

  • Pie 2
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • Texas listed him as playing at 207. https://texassports.com/sports/football/roster/jonathon-brooks/12405 216 may have been a combine weight, and those are of course always reflective of real-world     
    • 1855-INTUIT-TFN QuickBooks Payroll Support (𝟏𝟖𝟓𝟓)-𝟔𝟎𝟒-𝟖𝟓𝟓𝟔 would be a valuable resource for users navigating the intricacies of payroll management within the QuickBooks ecosystem. Here’s a breakdown of how such an article might be structured: Introduction to QuickBooks Payroll Support: This section would offer an overview of QuickBooks Payroll Support (𝟏𝟖𝟓𝟓)-𝟔𝟎𝟒-𝟖𝟓𝟓𝟔, highlighting its significance for businesses managing payroll processes. It would stress the importance of accurate payroll management and the role QuickBooks Payroll Support plays in ensuring smooth operations. Common Issues Addressed: The FAQ section would outline common problems or queries users might encounter with QuickBooks Payroll (𝟏𝟖𝟓𝟓)-𝟔𝟎𝟒-𝟖𝟓𝟓𝟔. This could include issues related to setting up payroll, processing payroll runs, handling payroll taxes, generating reports, and resolving errors or discrepancies. How to Contact QuickBooks Payroll Support: Clear instructions would be provided on how users can reach QuickBooks Payroll Support. This might include phone numbers, email addresses, live chat options, or links to online support portals dedicated specifically to payroll-related inquiries. Availability and Hours of Operation: Users would be informed about the availability of QuickBooks Payroll Support, including standard business hours, weekend availability, and any variations based on geographical regions or holidays. Response Times: Information on average response times for different types of inquiries would be helpful for users managing their expectations. This section might also cover factors that could affect response times and offer tips on how users can expedite the resolution of their issues. Tips for Efficient Support: Users would be provided with practical tips on how to prepare for contacting support, such as gathering necessary information beforehand (e.g., employee details, payroll history, error messages) to streamline the troubleshooting process. Alternative Support Resources: In addition to direct support channels, users might be directed to alternative support resources such as online help articles, video tutorials, or community forums where they can find answers to common questions or seek assistance from other users. Feedback and Satisfaction: Encouraging users to provide feedback on their support experience would be important for improving service quality. This section could outline how users can share their feedback and suggestions for enhancing QuickBooks Payroll Support. Security and Privacy: Reassuring users about the security and privacy measures in place when contacting QuickBooks Payroll Support would help build trust. This might include information on data encryption, secure communication channels, and compliance with relevant privacy regulations. In essence, an article with an FAQ section about QuickBooks Payroll Support would aim to provide users with comprehensive guidance on how to address payroll-related issues and effectively engage with QuickBooks’ support team for assistance.
    • Call Us Global 1855-SAGE-TFN-𝟏𝟖𝟓𝟓*𝟔𝟎𝟒-𝟖𝟓𝟓𝟔 Sage 100 support is a comprehensive business management solution designed for small and medium-sized enterprises (SMEs) to streamline their operations, manage finances, track inventory, and facilitate growth. While Sage 100 offers powerful features and functionalities, users may encounter technical issues, require assistance with software implementation, or need guidance on optimizing their workflows. Sage 100 Support 𝟏𝟖𝟓𝟓*𝟔𝟎𝟒-𝟖𝟓𝟓𝟔 provides dedicated assistance and resources to help users overcome challenges, maximize the benefits of the software, and ensure smooth business operations. In this comprehensive guide, we’ll delve into the various aspects of Sage 100 Support, including its features, benefits, common issues, troubleshooting techniques, and support options. 1. Understanding Sage 100 Support Sage 100 Support is a specialized service offered by Sage, the developer of Sage 100 ERP software, to assist users with technical issues, software implementation, training, and ongoing support. Whether users encounter software errors, require guidance on configuration settings, or need assistance with system integration, Sage 100 Support offers comprehensive assistance tailored to the needs of SMEs. Let’s explore the key features and benefits of Sage 100 Support: 1.1. Features of Sage 100 Support Technical Assistance: Sage 100 Support 𝟏𝟖𝟓𝟓*𝟔𝟎𝟒-𝟖𝟓𝟓𝟔 provides technical assistance to help users troubleshoot software issues, resolve errors, and optimize performance. Implementation Services: Support agents assist users in implementing Sage 100 software, including installation, configuration, data migration, and system setup. Training and Education: Sage 100 Support 𝟏𝟖𝟓𝟓*𝟔𝟎𝟒-𝟖𝟓𝟓𝟔 offers training programs, workshops, and educational materials to help users understand the software’s features and functionalities. Customization and Development: Support agents help users customize Sage 100 to meet their specific business needs, including developing custom reports, workflows, and integrations. Ongoing Maintenance and Updates: Sage 100 Support provides ongoing maintenance and updates to ensure that users have access to the latest features, bug fixes, and security patches. 1.2. Benefits of Sage 100 Support Expert Guidance: Users have access to Sage 100 experts who can provide accurate solutions to technical issues and offer personalized assistance. Time Savings: Sage 100 Support helps users resolve software-related tasks quickly, minimizing downtime and allowing them to focus on core business activities. Optimized Performance: By addressing software issues and providing guidance on best practices, support agents help users optimize the performance of Sage 100 ERP software. Enhanced Productivity: Sage 100 Support empowers users to leverage the full capabilities of the software, improving efficiency and productivity across their organization. 2. Common Issues with Sage 100 Despite its robust features and capabilities, users may encounter various issues when using Sage 100 ERP software. Here are some common issues that users may face: 2.1. Software Errors and Bugs Users may encounter software errors, glitches, or unexpected behavior when using Sage 100, which can impact their ability to perform critical tasks. 2.2. Performance Degradation Performance issues such as slow response times, system crashes, or unresponsiveness may occur due to factors such as system overload, inadequate hardware resources, or software configuration issues. 2.3. Data Integrity and Corruption Data integrity issues or data corruption may occur due to factors such as improper data entry, software bugs, or hardware failures, leading to inaccuracies in financial reporting or operational inefficiencies. 2.4. Integration Challenges Integrating Sage 100 with other systems or applications may pose challenges such as data synchronization issues, compatibility issues, or configuration conflicts, impacting the seamless flow of information across the organization. 3. Troubleshooting Sage 100 Issues Sage 100 Support offers various troubleshooting techniques to help users resolve common issues and optimize their experience with the software. Here are some general troubleshooting steps for Sage 100: 3.1. Verify System Requirements Ensure that your hardware and software environment meets the minimum system requirements for running Sage 100 ERP software, including operating system version, processor, memory, and disk space. 3.2. Update Software Check for updates to Sage 100 ERP software and install any available updates to access new features, bug fixes, and performance improvements. 3.3. Review Configuration Settings Review and validate configuration settings in Sage 100 to ensure that they are set up correctly and align with your business requirements. 3.4. Data Cleanup and Maintenance Perform regular data cleanup and maintenance tasks, such as purging old data, optimizing database indexes, and running data integrity checks, to ensure data accuracy and system performance. 3.5. Monitor System Performance Monitor system performance metrics such as CPU usage, memory utilization, and disk I/O to identify potential bottlenecks or performance issues and take corrective actions as needed. 3.6. Engage Sage 100 Support If you encounter issues that you cannot resolve on your own, contact Sage 100 Support for assistance. Provide detailed information about the issue, including error messages, steps to reproduce the problem, and any troubleshooting steps you have already 4. Contacting Sage 100 Support If users encounter issues with Sage 100 that they cannot resolve independently, they can reach out to Sage 100 Support for assistance. Here are some ways to contact support: 4.1. Phone Support Call the Sage 100 Support phone number to speak with a support agent who can provide personalized assistance and guidance. 4.2. Email Support Send an email to Sage 100 Support describing the issue, and a support agent will respond with instructions or troubleshooting steps. 4.3. Online Support Portal Access the Sage 100 online support portal to submit a support ticket, browse knowledge base articles, and engage with the community forums for additional assistance and resources. 4.4. On-Site Support Depending on your support plan and service level agreement (SLA), Sage 100 Support may offer on-site support where a technician visits your location to troubleshoot issues or provide hands-on assistance. 5. Best Practices for Sage 100 Support To maximize the effectiveness of Sage 100 Support and ensure a smooth operation of your ERP system, consider implementing the following best practices: 5.1. Stay Informed Stay informed about updates, patches, and new releases for Sage 100 ERP software by subscribing to newsletters, following official Sage 100 channels, and participating in user forums and communities. 5.2. Document Issues Keep detailed records of any issues, errors, or challenges encountered with Sage 100, including error messages, steps to reproduce the problem, and any troubleshooting steps taken. This information can help expedite the resolution process when contacting support. 5.3. Train Users Provide comprehensive training to users on how to use Sage 100 effectively, including navigation, data entry, reporting, and troubleshooting common issues. Well-trained users are better equipped to identify and resolve minor issues on their own, reducing the reliance on support resources. 5.4. Regular Maintenance Implement a regular maintenance schedule for Sage 100, including database backups, software updates, data cleanup, and performance tuning. Proactive maintenance helps prevent issues before they occur and ensures optimal performance of the ERP system. 5.5. Review SLA Review your service level agreement (SLA) with Sage 100 Support to understand the level of support you are entitled to, including response times, resolution times, and escalation procedures. Ensure that your SLA meets your business needs and expectations. 6. Conclusion Sage 100 Support plays a critical role in helping businesses maximize the benefits of their ERP investment, troubleshoot issues, and ensure smooth business operations. By understanding the features, benefits, and support options available, users can effectively leverage Sage 100 Support to address challenges, optimize their ERP system, and achieve their business objectives. Whether users encounter technical issues, require assistance with software implementation, or need guidance on best practices, Sage 100 Support offers comprehensive assistance and resources to help businesses succeed. With proactive maintenance, regular training, and effective communication with support resources, businesses can harness the full potential of Sage 100 ERP software and drive growth and success in their organization.
×
×
  • Create New...