You might be wondering A) what the shark reference is about, and B) why I chose to put Gregor Blanco (hint: he's who the shark reference is about) as practically an equal contributor with Madison Bumgarner when "MadBum" had a one-hit shutout. I can explain.
For those who don't know, Blanco's nickname is "white shark." ("Blanco" is Spanish for "white", by the way. You learn something new everyday!). While I was watching tonight's game against the Reds, the great Giants broadcasters Mike Krukow and Duane Kuiper were talking about a conversation they overheard between Blanco and Pablo Sandoval before the game. Sandoval was telling Blanco that he should put his hand on the top of his head in the shape of a shark fin whenever he got a hit.
Blanco hit a triple in the bottom of the 7th inning, and as you can see at 0:24 in the clip, he flashes the fin. He and Sandoval do more fin-tastic stunts after Blanco scores and comes back into the dugout. Pablo must be so boring to play with...
Anyway, to make a short story long, I thought this shark fin stuff was fun. Also, my favorite animal has always been the shark, so Blanco and Sandoval's shenanigans struck a special cord with me.
All this being said, I didn't let the shark fun distract me from the shellacking Bumgarner put on the Reds' lineup. One hit, 2 walks, 8 Ks, and an impressive first-to-home sprint on Blanco's triple made this what has to be Bumgarner's best game as a professional, other than Game 4 of the 2010 World Series. The craziest part: he's only 22!
This game was also the 4th straight shutout for the Giants, as well as 36 straight shutout innings, which are both SF Giants records. This is a hot pitching staff right now, and the lineup is providing more than enough runs, which I'm sure makes the pitchers ever more confident.
As long as the injury bug doesn't bite the Giants too hard for the rest of the season, there's no reason this team shouldn't win the division. I worry about Arizona (the Dodgers need more than Matt Kemp being healthy to pose a real threat in this division), but the Giants have a much better lineup than last year's even when Buster Posey was healthy. I'm by no means declaring the Giants NL West winners this early in the season, but making the playoffs is definitely a realistic expectation.
Excuse me while I go knock on some wood.
Thursday, June 28, 2012
Monday, June 25, 2012
Misusing Casilla
I don't want to blame Bruce Bochy, Brian Sabean, or other members of Giants' management for the walk-off home run Santiago Casilla gave up against the A's yesterday, but it gets hard to watch Casilla be continually saved (pun semi-intended) for save situations. You might ask, "Shouldn't the closer always and only be used in save situations?"
No, he shouldn't, and I've got plenty of reasons why.
First off, let me just say that the save statistic is one of the most annoying, meaningless stats in baseball. If you're not sure why this is, click on the previous link and read the part where Wes Littleton "earned" a save in a 30-3 game. Looking at the box score, you might understandably be wondering how Littleton earned a save when he entered the game with a 14-3 lead. According to the save rules, if you pitch effectively for at least three innings with a lead, you get a save. I think it's pretty clear why this stat is so dumb.
So why do managers act like save situations are so damn important?
Well, sometimes these situations actually are vital, like if it's the bottom of the ninth inning with bases loaded and one out in a one-run game. You want your best reliever in that situation, and the closer is (or, at least, should be) your best reliever.
But most save situations aren't as dire as the previous scenario. For instance, yesterday was the first time since May 8th (14 saves ago) that Casilla entered a game in a save situation with only a one-run lead to protect. Casilla's two blown saves? Both when he entered the game with a one-run lead. Now, to be fair, Casilla hasn't had too many "Hoffmans" (saves when giving up at least one run), so he's been a shut-down guy in save situations with 2-3 run leads, but it's easy to see how the save stat can make an average reliever look elite.
So why else do managers value save situations so much? Well, because they're misguided.
If the scenario were bottom of the ninth inning, bases loaded, one out, but a tie game, many managers would be reluctant to use their closer there. Unless the manager is simply resting his closer for that game, there's zero reason why he shouldn't use his closer in that situation. If you're trying to win the game, you need to get two outs without giving up a run, so you want your best reliever (your closer) in this spot. If you don't think your closer is the best guy in the bullpen to do the job, he shouldn't be the closer.
This saving the closer for save situations is the main problem I have with how Bochy has been using Casilla this season.
Casilla pitched in all three games against the A's this weekend. In the first game, he pitched the ninth inning with a 5-3 lead when he entered. No issue there. It had been two games since he'd pitched, so he had plenty of rest and there hadn't been any situation earlier in the game where he would've been more helpful. However, he was misused in the second game. The Giants had a four-run lead with two outs and runners on first and second base when Casilla came in. A "save situation". It's as if a siren went off in Bochy's brain that was screeching "SAVE SITUATION!!" before he replaced Shane Loux with Casilla. Bochy should have brought in Clay Hensley or Javier Lopez, both whom had pitched less than Casilla the night before. If one or both of those two pitchers gave up some runs, and the situation became tense, then Casilla would be a good choice to bring in but why waste your closer in a four-run game just because he had a chance to record a save?
If Bochy would just use Casilla (and Sergio Romo, who many think is the best reliever on the Giants) in the tightest spots and ignore the save stat, he would almost certainly see results in the win column. Instead, he risks overusing his closer because the Giants play so many close games where they have small leads in the ninth inning. Maybe Brian Wilson wouldn't be out for the year if Bochy used this method in the previous seasons (only speculating because no one knows if Wilson's arm would've broken down regardless of how he was used).
Get rid of the save!
No, he shouldn't, and I've got plenty of reasons why.
First off, let me just say that the save statistic is one of the most annoying, meaningless stats in baseball. If you're not sure why this is, click on the previous link and read the part where Wes Littleton "earned" a save in a 30-3 game. Looking at the box score, you might understandably be wondering how Littleton earned a save when he entered the game with a 14-3 lead. According to the save rules, if you pitch effectively for at least three innings with a lead, you get a save. I think it's pretty clear why this stat is so dumb.
So why do managers act like save situations are so damn important?
Well, sometimes these situations actually are vital, like if it's the bottom of the ninth inning with bases loaded and one out in a one-run game. You want your best reliever in that situation, and the closer is (or, at least, should be) your best reliever.
But most save situations aren't as dire as the previous scenario. For instance, yesterday was the first time since May 8th (14 saves ago) that Casilla entered a game in a save situation with only a one-run lead to protect. Casilla's two blown saves? Both when he entered the game with a one-run lead. Now, to be fair, Casilla hasn't had too many "Hoffmans" (saves when giving up at least one run), so he's been a shut-down guy in save situations with 2-3 run leads, but it's easy to see how the save stat can make an average reliever look elite.
So why else do managers value save situations so much? Well, because they're misguided.
If the scenario were bottom of the ninth inning, bases loaded, one out, but a tie game, many managers would be reluctant to use their closer there. Unless the manager is simply resting his closer for that game, there's zero reason why he shouldn't use his closer in that situation. If you're trying to win the game, you need to get two outs without giving up a run, so you want your best reliever (your closer) in this spot. If you don't think your closer is the best guy in the bullpen to do the job, he shouldn't be the closer.
This saving the closer for save situations is the main problem I have with how Bochy has been using Casilla this season.
Casilla pitched in all three games against the A's this weekend. In the first game, he pitched the ninth inning with a 5-3 lead when he entered. No issue there. It had been two games since he'd pitched, so he had plenty of rest and there hadn't been any situation earlier in the game where he would've been more helpful. However, he was misused in the second game. The Giants had a four-run lead with two outs and runners on first and second base when Casilla came in. A "save situation". It's as if a siren went off in Bochy's brain that was screeching "SAVE SITUATION!!" before he replaced Shane Loux with Casilla. Bochy should have brought in Clay Hensley or Javier Lopez, both whom had pitched less than Casilla the night before. If one or both of those two pitchers gave up some runs, and the situation became tense, then Casilla would be a good choice to bring in but why waste your closer in a four-run game just because he had a chance to record a save?
If Bochy would just use Casilla (and Sergio Romo, who many think is the best reliever on the Giants) in the tightest spots and ignore the save stat, he would almost certainly see results in the win column. Instead, he risks overusing his closer because the Giants play so many close games where they have small leads in the ninth inning. Maybe Brian Wilson wouldn't be out for the year if Bochy used this method in the previous seasons (only speculating because no one knows if Wilson's arm would've broken down regardless of how he was used).
Get rid of the save!
Wednesday, June 13, 2012
Subscribe to:
Posts (Atom)