Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the podcast-player domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/birdseye/public_html/wp-includes/functions.php on line 6121
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
Warning: Cannot modify header information - headers already sent by (output started at /home4/birdseye/public_html/wp-includes/functions.php:6121) in /home4/birdseye/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":6175,"date":"2016-03-10T21:56:29","date_gmt":"2016-03-11T02:56:29","guid":{"rendered":"http:\/\/www.birdseyeviewbaltimore.com\/?p=6175"},"modified":"2016-03-10T21:56:29","modified_gmt":"2016-03-11T02:56:29","slug":"april-what-to-watch-for","status":"publish","type":"post","link":"https:\/\/www.birdseyeviewbaltimore.com\/april-what-to-watch-for\/","title":{"rendered":"Five Games to Circle on the Orioles’ April Schedule"},"content":{"rendered":"Spring Training is unbearable sometimes. I’m not referring to the fact that Hyun Soo Kim has one hit. Or about the fact that the Orioles’ best two results\u00a0in their Grapefruit League games have been a pair of ties. This Spring Training is unbearable because I don’t want to have to talk about those two things. Or the fact that some starters have gotten shelled. Or the fact that the Orioles have been grossly outscored in these games – you know, an offense that is supposed to win games 8-6 this year.<\/p>\n
None of it matters. Well, maybe some of it matters, but as Scott will tell us, the correlation between Spring Training results\u00a0and the following\u00a0season is not very strong. I’m not going to waste time caring about things that aren’t going well now, because come April 4th, they won’t be relevant. And to be fair, I wouldn’t be crowing if the Orioles were having a Jake-Fox-esque spring, either.<\/p>\n
Instead, I’m trying to focus on the season to come.\u00a0Here are a few highlights I will enjoy from the\u00a0first month of the\u00a0season.<\/p>\n
<\/p>\n