Pages

Tuesday, September 17, 2013

NFL Week 2 Snap Judgments

Week 2 has already come and gone, and here are my thoughts...

1. Stop me if you heard this before, but an entire division stunk except for a single wide receiver.  Last week it was the AFC North; this week was the NFC East's turn.  If not for a crazy day from Dez Bryant, the entire division laid an egg.  Oh sure, the Eagles put 30 points up on the board thanks to big days from LeSean McCoy and DeSean Jackson, but the defense gave up 419 yards passing to Philip Rivers.  Not many football teams will win a game while giving up that kind of yardage.  The Giants continued turning over the ball which led to their demise, and the Redskins couldn't save a turkey from becoming Thanksgiving dinner.  In fact, speaking of the Redskins...

2. What do the Redskins do with RGIII?  From a fantasy football perspective, I wanted nothing to do with drafting RGIII as my quarterback on any of my teams.  He hadn't played a down in any football game since January, and spent the entire off-season rehabbing his knee.  He didn't play at all during the preseason either, so there were bound to be cobwebs and rusty play for at least the first week or so.  Still, yesterday he looked very uncomfortable throwing the football and avoiding any hits.  Tony Dungy even said on Sunday Night Football that the Redskins should consider benching him after next week if he continues to play poorly.  Personally, I think that's extremely premature, but the Redskins also can't afford to continue digging a deeper hole for them while waiting for RGIII to get back into playing shape.

3. The Patriots are in serious trouble.  When was the last time those words found themselves in the same sentence?  I expected the Patriots to take a step backwards this season given their extremely weak group of receivers, but even I was surprised at how bad they looked last Thursday night against the Jets.  I'm a firm believer in the Bill Parcells philosophy of "You are what your record says you are," but barely squeaking by the Bills and Jets is a huge concern for a team who was in the Super Bowl two years ago, and was in the AFC Championship Game last year.  Miami is looking really good after their first two games, which puts the Patriots in the position of someone actually breathing down their necks.  That's a very foreign situation for them.

4. The rest of the NFC could face a daunting task if the Seahawks wind up with the #1 seed in the playoffs.  The Seahawks' home field advantage has always been somewhat skewed due to how sound travels in their stadium.  I don't know much about the mechanics or engineering of it, except that the stadium's design and location near water makes sound much louder than most other NFL stadiums.  It showed Sunday night thanks to Seahawks fans aiming for setting new noise records during a game.  That would disrupt any opposing team's communication from the sidelines to the field.  Even though we're a long way off from January, the Seahawks have shown over the last few years they are extremely tough to beat in their own house.

5. The Goat of the Week Award goes to the CBS affiliate station WKMG in Orlando.  This is a really outside the box pick, but check this out.  How pathetic is that if a station in the Jaguars' home market has to apologize for the "inconvenience" of showing the Jaguars game instead of the Broncos/Giants game?  Maybe the more appropriate goat is the Jaguars for being as awful a team as they are, but I think it's pretty telling if a local network knows how bad the team is and feels ashamed for being contractually obligated to televise them.

6. The Cardiac Kodiaks have been pretty remarkable so far.  Seeing how the Bears have made two fairly big comebacks in the first two weeks of the season, I'm reminded of a two-week stretch for the Bears way back in 2001:



Incidentally, how much better was NFL Prime Time with only Chris Berman and Tom Jackson?  Man, those were the good ol' days.  Sigh....

7. Ron Rivera can't last much longer in Carolina.  This season marks the third year for the Panthers with Ron Rivera as head coach, and it's the third straight year they've started slow.  They find new and bizarre ways to blow leads late in games, putting themselves in a deep hole by mid-season.  The last couple years, they find some kind of stride fairly late in the season and wind up winning 5 or 6 of their final few games.  If they lose next weekend and start 0-3 - which is a real possibility since they are playing against the desperate Giants - ownership may have to consider making a coaching change at some point this season.

8. I wouldn't be surprised if the Chiefs wound up winning double-digit games at this point.  I know, talk about jumping to potentially irrational conclusions.  But considering the Chiefs have already equaled last season's win total - albeit one of those games was against Jacksonville - they're clearly one of the most improved teams in the NFL right now.  Plus, they have yet to turn the ball over even once.  Don't get me wrong, though; I don't necessarily think they are good enough to win the AFC West yet, but they could very well compete for a Wild Card come December.

9. The Todd Haley Experiment in Pittsburgh is imploding.  I'm not sure if there's any one thing that's caused the Steelers to struggle so much in the first two games of the season.  The offensive line is clearly a weakness, so I can't imagine that the line coach will have a job there much longer.  But when the offense (and the team as a whole) only scores two touchdowns through the first two games of a season, that's about the worst kind of omen.  Even as a Ravens fan, I wouldn't have expected this kind of showing from the Steelers for a prolonged period of time.  The Steelers usually have one down year in every 5-year span or so, but last year's struggles have slopped over into this season, and there's no sign of things changing any time soon.  The Steelers are back at home next week against Chicago, so there's a real chance they could find themselves at 0-3.

Tuesday, September 10, 2013

NFL Week 1 Snap Judgments

This was an idea that I had for last season, but it never got off the ground.  I didn't want to start mid-season in writing my weekly recaps and thoughts, so I figured I'd hold off till now to get it going.  Hopefully I won't run out of steam during the course of the season at all.

It's worth noting that almost all these thoughts are going to be unfair given we're only 1 week into the season, but that's what snap judgments are for.

1. The AFC North looked absolutely awful this weekend aside from A.J. Green.  I'm super grateful that I have A.J. Green on a couple fantasy teams of mine, but wow.  The Ravens fell apart in the second half of their season opener Thursday night in Denver; Cincinnati couldn't hold on to a 21-17 lead in the 4th quarter against Chicago; and Pittsburgh and Cleveland were both so bad on offense they were offensive to offenses around the league.  A.J. Green was the lone bright spot for the entire division this weekend, and he put his team on his shoulders in an effort to win on Sunday.  The rest of the team just couldn't back him up.

2. What did I say about Larry Fitzgerald?  I told you in my season predictions that Larry Fitzgerald will be the Comeback Player of the Year now that he has a quarterback who can actually play the position.  I know, it's only one game, but he looked every bit as awesome Sunday as he did with Kurt Warner. 'Nuff said.

3. Even with replay and the actual officials, we will always have blown calls in games.  I'm talking about the blunder in offsetting penalties in the Green Bay/San Francisco game.  Hey, I would never claim to know the rule book in the NFL, and I don't envy the refs who have to make calls like that on the field at a moment's notice.  But when refs have time to blow a call even after having time to review the play and discuss it before making an official announcement during the game, that's a major black eye.  I don't know what the solution to the problem is, but I'd really hate to see what would happen in a playoff game or the Super Bowl if such a blown call affected the outcome somehow.

4. I might have picked the wrong team to go 0-16.  I said in my predictions that the Raiders have a chance at going 0-16 this year, assuming they don't beat the Jaguars in Week 2.  Ironically, now it looks like it's the Jaguars who look more likely to go 0-16 if they don't win this coming weekend in Oakland.  I'm not sure which position(s) they need to address in order to become a competitive team again, but they somehow managed to look less competitive than the Raiders did.  And that's saying something.

5. The Goat of the Week Award has to go to Lavonte David.  The Bucs were up 17-15 with less than a minute to play in the game when Jets QB Geno Smith scrambled for 10 yards.  He was on his way out of bounds when Lavonte David of the Bucs pushed Smith, even though Smith was already out of bounds.  That kind of play will always get a flag for unnecessary roughness, which tacked on 15 yards on the end of the play, putting the Jets in field goal range.  With 34 seconds left on the clock, the Jets kicked a game-winning field goal, thanks to the dumb penalty on David.  Nice one, Lavonte.  You not only cost your team the game, but I bet a lot of people playing Survivor leagues in fantasy football were eliminated in Week 1 thanks to you (I took the Colts, so I'm safe).

6. The Broncos will be really good again, but I still don't trust their defense.  They will be without Von Miller for another 5 weeks, and I don't know when Champ Bailey is expected to come back from his injury.  Still, they're going to win 11 or 12 games this season.  However, I don't think they're a Super Bowl team because of their defensive issues and Peyton Manning's history of collapsing in the playoffs.  Don't get me wrong, though - Peyton Manning was by far the single best player who took the field in Week 1.

7.  I'm not sure what to make of the Bills/Patriots game.  The Bills have played the Patriots close in a few games over the last couple years, and they've fooled me into thinking they could pull off the upset in the past.  However, I've made no secret over how down I am on the Patriots this year, so the question here is where do the Bills' positives end and the Patriots' negatives begin?  Danny Amendola wasted no time in pulling a groin injury during the game (though he did return after a brief absence), so it's only a question of when he winds up injuring himself to the point of having to miss a couple weeks.  The Patriots still did what they have done countless times in the past, and that's kick a game-winning field goal late in the 4th quarter.

8. The only reason why the Eagles might not win the NFC East is because of their defense.  I'm still sticking to my prediction of the Eagles pulling off the improbable by winning their division this year.  I'm actually more confident of my prediction now than I was prior to this weekend, though it's clear the team's major weakness is its defense.  How else does a team at one point lead a game 33-7, and then wind up with a final score of 33-27?  Despite this glaring weakness though, I am still believing in the team winning the division and making the playoffs.

9. Nearly all these snap judgments will be moot a month from now.  That's the great irony to Week 1.  Football fans and talking heads are all so excited to have the new season start, but after the first weekend, teams are either looking like Super Bowl champions or utter disasters.  Eyes are particularly on the defending champs, and plenty of writers and fans are wondering if they'll even make the playoffs this season.  Reality is always somewhere between extremes, and I think the Ravens will still win the AFC North and make a deep playoff run.  Accuse me of wearing purple-colored glasses all you like, but they won't be as awful as they were in the second half of the game Thursday night.

Monday, September 9, 2013

Recognizing My Greatest Fault

I wrote a while back about my intention to find a therapist after a recent issue that came up with me.  I haven't talked about it since because most of our discussions so far have been too personal for me to want to write about them openly on here.  This week's session, however, really shed some light on a big picture issue that I've been somewhat aware of for a long time, yet chose to ignore.

As far back as I can remember, I've avoided conflict as much as possible.  I've long thought of myself as a very agreeable and easy-going person, one who doesn't let too much get under his skin.  If someone did something to hurt me, I'm more than willing to forgive and forget, provided the person recognizes what he/she had done was wrong and hurt me in the process.  I've never been a person who has either been comfortable with or enjoyed chewing someone else out, even if I'm in the right.  I hated the idea of getting emotionally worked up over something to the point of really getting angry, only to find out my anger wasn't justified in the first place.  I often talked myself out of being angry, thinking I was being mature and level-headed in analyzing the situation in question, and then deciding if it was really worth getting upset over at all.  More often than not, I opted for burying the hatchet and moving on.  Life was too short and precious in my eyes to agonize over someone hurting my feelings.

Trouble is, this line of thinking formed a pattern of passive aggressiveness.  It's clearly been a part of my life since childhood, and it's affected many relationships over the course of my life - dating and otherwise - and even now in the present.  My fear of rocking the boat morphed into fears like making bad decisions, saying something that I would regret later, and an inability to really express my feelings to others.  Having a preoccupation of being a people pleaser at my own sanity's expense was anything but healthy, even though in my mind I was convinced I was taking the high road in avoiding expressing anger.

Up until now, my therapist has allowed me to talk about any subject that I wanted to discuss, but this week's session she took a left turn.  She said now that we've been meeting for several weeks, she's gotten a feel for who I am as a person, how I'm likely to respond in certain situations, and what kinds of comments or recommendations she has for me.  She gave me a homework assignment to do in preparation for our next meeting, and I have to research passive aggressive behavior.

So far, the one piece of information that caught my attention the most was a form of covert abuse.  When the word "abuse" comes to mind, I always picture something of a physical or emotional nature. It's very direct, and easily identifiable.

This kind of abuse is much, much different.  From what I've read, it involves behaviors like forgetfulness, blaming, procrastination, lack of anger, and victimization - all of which I've definitely been guilty of in the past.  While I'm sure that I wasn't fully aware of what I was doing at the time, it doesn't change the fact that what I did was hurtful and selfish.  The crappy part is that most people probably wouldn't get too upset with me if I simply chose to speak my mind and communicate my feelings.

I almost didn't want to write about this because the subject could easily turn into one of two things: a pity party or a cry for attention.  It certainly isn't meant to be either of those; I'm finally being honest with myself, and this blog is probably the most healthy venue to get my thoughts out.  I mentioned this blog to my therapist last week too, and she agreed that it's a good way to get my emotions out when I need to, even if I write a post that I opt not to openly publish (which I have done several times).

I don't expect or want a pat on the back for making this kind of realization.  If anything, I'm hoping that this opens the door for more breakthroughs that are for my benefit, even if the initial reveal isn't something pleasant.  Then again, there's little point in trying to become mentally healthy if I don't confront some unpleasant things about myself at all.

Tuesday, August 27, 2013

Roger Goodell Made His Bed, And Now He May Have to Sleep In It

Many football fans, myself included, love watching a football game being played in winter weather.  There's something fitting about it, considering the sport is played in the fall months into the winter, and by the time December rolls around cold weather starts to affect how games are played in half the cities across the country.  There have even been a few notorious games played in heavy winter weather, most notably the Raiders/Patriots playoff game in January 2002.

The Super Bowl has perennially been played in either domed stadiums or warm weather cities since it's played in early February every year.  The NFL hasn't wanted winter weather to potentially impact the game, and with good reasons.  Snow and ice impact travel and mobility of fans coming to a host city, as well as the actual field conditions for the game itself.  Still, Goodell announced that Super Bowl 48 (I think Roman numerals just look stupid now) would be played in East Rutherford, New Jersey, where the Giants and Jets play their home games.  When he had made the original announcement, he took the obvious risk of inviting Mother Nature to affect the game, but also claimed that fans had been clamoring for this kind of Super Bowl for years.

Despite my love of watching football being played in snow and winter weather, I never liked this idea at all.  Having the rest of the playoffs being played in potentially cold cities like Boston, New York, Philadelphia, Chicago, Baltimore, or Denver is fine.  There isn't much that the NFL could do to avoid weather during January in cities such as those, and the home teams have a bit of an advantage in being used to the weather there.  The home fans are also used to what the weather is like, so they know what they're getting into if their team has to host a playoff game (or more) in January.  They can adequately prepare for cold and/or snow, and take an extra jacket or two if need be.

So what happens if a warm weather team has to play in Super Bowl 48?  Teams in cities like Miami, Tampa, Phoenix, or San Diego aren't used to playing in freezing temperatures, and Northern Jersey is typically below 32 degrees in early February.  Their play in cold weather could be affected negatively, and who would want to watch a sloppy Super Bowl?  I wouldn't like watching players slip and slide in the snow, especially if the players from that team rarely ever see snow in the first place.

Consider the fans in this equation as well.  Fans in those same warm weather cities aren't used to cold or snow either, so they don't know how to prepare properly either.  They sure wouldn't know how to drive in such conditions either, so unless they rely on taxis or other public transportation they would have to walk for the most part.  That would either get very expensive very quickly, or not be much fun at all.

Taking all those factors into account now, think about this latest potential development: The Farmers Almanac made its annual predictions of what winter 2014 will be like, and it ain't pretty.

"Pretty" may not be the right term.  A blanket of snow is actually very beautiful to admire....from the comfort and warmth of one's own house.  I happen to love watching the snow fall while sitting on my couch, sipping hot chocolate and watching a movie.  I don't mind shoveling snow from a driveway or sidewalk.  And who doesn't love a good ol' snowball fight?

The key here is that I'm talking about dealing with snow within the confines of where I live.  If I'm traveling to New York or Northern Jersey because my team is in the Super Bowl, I'd have to drive up there through a potentially awful snowstorm.  Then I'd have to find a place to park it in a hotel.  Then I'd have to walk around the snow when I want to sight see.  Then I'd have to avoid slipping on a patch of ice somewhere on the ground.

And that's before we even get to watching the game.

Oh, and don't forget - I'm used to brutal winter weather.  What if fans from cities like Atlanta or San Francisco come to New York for the Super Bowl?  They have no idea what they're in for.  Their flights could be affected, and by the time the game actually starts on Sunday night (when it's coldest, considering the sun won't even be out!) they may be more excited to go home than watch the game.

Plus, what about the halftime show?  If the snow is falling and it's 20 degrees outside, what will the NFL do with its performance at halftime?  I suppose the concert could be played from an alternate location, but that would only help the fans watching from home.  The fans in the stadium would be screwed.

What if the weather got to be so bad that fans would actually leave the stadium?  I realize that would only happen in the most dire of circumstances, but it's happened to plenty of football games in the past.  The NFL wouldn't like the idea of a half-empty stadium by the 4th quarter.  There's only so much a TV broadcast can cloak by concentrating on the action on the field.

My overall point here is that I think the idea of having the Super Bowl being played in a stadium where winter weather could impact the game is a terrible idea.  I thought it was a bad idea from the moment Goodell had first announced it, and if the Farmers Almanac was correct in its predictions, the worst possible outcome could happen.  Such a situation would make the debacle in Dallas a couple years ago look like a minor hiccup.

I know I sound like a Daniel Downer in talking about this, but I guess in my eyes the Super Bowl was never broken in the first place.  It certainly didn't need "fixing."  I realize this is just an experiment for the league, but it does want its #1 media market to enjoy the exposure of hosting the Super Bowl, especially when much smaller markets like Jacksonville and Detroit have hosted Super Bowls in the past.

I only hope this doesn't mean that Denver will one day host a Super Bowl.  Talk about a recipe for disaster.

Tuesday, August 13, 2013

2013 NFL Season Predictions Sure To Go Wrong

We're getting close to my favorite time of the year, sports-wise.  The pennant chases in baseball are heating up, and football season is upon us.  Once again, for the fourth straight year, here are my 10 predictions for the upcoming NFL season....

1. The Philadelphia Eagles will win the NFC East.  Hear me out on this one.  I know their last two seasons have been dismal, particularly their 2012 season.  Andy Reid is gone, with University of Oregon coach Chip Kelly taking over.  But here's the kicker stat that I keep thinking about: Since 2003, there has been at least one team every season who finished last place in its division to win the division the following year.  That's not a fluky stat, and I think the Eagles stand the best chance at being this year's version of that team.  Plus, every team in the NFC East beats each other up all year long, so 9 wins could be enough to win it and host a playoff game.  The team has enough key pieces in Vick, McCoy, and Jackson on offense to put points on the board, and the defense can still play with the other offenses in the division.

2. The Miami Dolphins will make the playoffs somehow.  I honestly think the Dolphins have a legitimate shot at winning the AFC East, but even if they don't they will snag at least a Wild Card spot.  Ryan Tannehill looks like the real deal, and having Mike Wallace to throw to will give the Dolphins enough offensive boost to win a few key games (even though I think Wallace is overrated as a receiver).  I expect them to give the Patriots the first true competition in the division in years.

3. Tom Brady will throw for his fewest touchdown passes since 2009.  Speaking of the Patriots, I am way down on them this year, for obvious reasons that have affected their offense.  With Wes Welker departed for Denver and Aaron Hernandez facing all kinds of legal trouble, the key receiver is Rob Gronkowski, and there's no telling when he'll be healthy for the season.  Do the likes of Danny Amendola (an injury risk in his own right), Aaron Dobson, Julian Edelman, and/or Michael Jenkins really intimidate defensive backs across the league?  The Patriots will still likely win at least 10 games this season since two of the three other teams in their division are bottomfeeders of the league, but I expect them to struggle by their standards and also rely on their running game more since their receivers are much weaker than they have been in years.

4. The Baltimore Ravens will break the 1984 Chicago Bears' single season team sacks record.  One of the reasons why I've been looking forward to this season is for football talking heads to shut up about the turnover the Ravens had since January.  They kept talking about the Ravens losing the likes of Ray Lewis, Paul Kruger, Dannell Ellerbe, and Ed Reed on their defense, saying those players can't be replaced (Mind you, they also loved to rant over the last few years how Lewis and Reed were also shells of their former selves, which I would say contradicts the previous statement).  So the Ravens chose to revamp their front seven and added Chris Canty, Marcus Spears, Daryl Smith, and Elvis Dumervil, on top of drafting nose tackle Brandon Williams and linebacker Arthur Brown.  Haloti Ngata will now move back to his native position of nose tackle and rotate with Williams, and Terrell Suggs will rush opposing quarterbacks opposite Dumervil on the other side.  The 1984 Bears currently hold the record for most sacks in a single season with 74, and I think the Ravens will break that record with their revamped line this year.

5. The Oakland Raiders have a legitimate shot at going 0-16.  I made a similar prediction back in 2010 about the Browns after looking over their schedule for that season, and I came away with a similar feeling about the Raiders this year.  Their nondivisional opponents include the AFC South and NFC East, which means they'll face teams like the Texans, Colts, Titans, Eagles, Redskins, Giants, and Cowboys, and I wouldn't expect the Raiders to beat any of those teams.  In fact, their game in Week 2 is home against the Jaguars, and if they don't win that game I don't think they have another winnable game on their schedule until Week 14 against the Jets.  Even if they do manage to win a game or two this season, I expect them to wind up with the first overall pick in next year's draft.

6. The Indianapolis Colts will steal the AFC South away from the Houston Texans.  The Texans have been on the cusp the last couple seasons, but they haven't managed to win more than a single game in the playoffs at all.  They were in the driver's seat for the #1 seed in the playoffs with about three weeks to go in the regular season, and then they got sloppy by mid-December.  I think something similar will happen this year, only this time it will cost them the division and a home playoff game in January.  The Colts and Texans face off twice in the second half of the season, including a very important match up in Week 15 in Indianapolis.

7. Matt Ryan will be the league MVP.  I think Matt Ryan is going to have a career year, even after getting his big contract this offseason.  The NFC South is a pretty tough division, and while I don't think the Falcons win 13 games again like they did last year, they'll still come out on top.  I actually thought Ryan was fairly overrated for most of his career to date, but I've come to think of him as a really good quarterback in the league, and he'll get a whole lot more exposure throughout the season.

8. Larry Fitzgerald will be the Comeback Player of the Year.  This prediction sounds a bit weird since players on the comeback usually are recovering from injury, but Fitz hasn't had any significant injuries at any point during his career.  His issue has been a lack of a decent quarterback on his team since Kurt Warner retired a few years ago.  Now that he has (at the very least) a competent quarterback in Carson Palmer, he'll return to the kinds of numbers he was putting up during the hey days of his career, and be worth drafting in fantasy football again.

9. Adrian Peterson will be the first running back in history to rush for 2000 yards in back-to-back seasons.  Until somebody figures out how to stop Adrian Peterson, I see no reason why he'd slow down or step backwards from where he left off at the end of last season.  He's a special kind of running back and offensive threat, and the kind of player that almost any NFL fan would like to see win a championship before the end of his career.

10. The Baltimore Ravens will repeat as Super Bowl champs and defeat the Seattle Seahawks in Super Bowl 48.  I know, I know.  Such a stinking homer pick.  There is a bit of logic to my thinking though, so roll with me for a moment before dismissing my prediction.  I've already talked about how the Patriots are down.  In addition to the Patriots, the Steelers are down as well, the Bengals need Andy Dalton to beat the likes of Tom Brady and/or Peyton Manning, and the Texans need Matt Schaub and Andre Johnson to avoid getting hurt.  That leaves the Broncos in the AFC as the only real rivals to the Ravens, and Ravens have already shown they can beat the Broncos on the road in the playoffs last year.  I don't think the Ravens will steamroll through the regular season (I think they finish with 11 wins), but the team as a whole looks better than last year's Super Bowl champs.

Meanwhile over in the NFC, there are just as many contenders who look weaker than they were last year, namely the Packers and 49ers.  Seattle has Percy Harvin recovering from surgery and will have him back by December to make their playoff push.  I expect them to beat Atlanta in the NFC title game before traveling to New York to face the Ravens.

And there you have it.  If history is any indicator, I probably will only have 3 or 4 of these predictions come true.

Tuesday, July 23, 2013

What Gets My Blood Boiling

I don't get easily offended or even pissed off about anything very often.  I try to take most ideas and comments with an open mind, even if the opinion is different from my own.  This is especially true when debating or discussing something as sensitive as religion; I have many close friends and even some family who have vastly opposing views on religion compared to mine, but we disagree and leave it at that.  I'm hardly a missionary, so getting to a really in-depth conversation over religion would quickly put me in over my head.

With that in mind, I came across this brief story today during my lunch break at work.  Like I said, I try not to get too flustered when I read something about a non-religious person getting into a tizzy over a religious person - Christian or otherwise - making a public display of his or her views.  The last time I can recall ever getting really offended over something anti-Christian was a theater performance I saw in college where a character had intentionally created a performance designed to offend Christians everywhere.

My view on anything in the media designed to be anti-religion or anti-Christian has always been the same: The predominant amount of anti-religion rants have been against Christianity, mainly because it's the "mainstream" religion in this country and around the world.  I can't remember the last time I ever read anything from the likes of American Atheists targeting Muslims or Jews.  Getting back to the aforementioned performance I had seen, I didn't exactly give the character in the play props for being "edgy" for simply mocking Christian theology.

Anyway, the story I came across today was probably the first time I had been so deeply offended and pissed off at an atheist getting riled up about a public display of Christian faith.  I never knew the story of Buzz Aldrin bringing communion with him when he had landed on the moon during the Apollo 11 mission.  When I read that particular side to the moon landing, my first thought was, "Wow, that's pretty awesome."

Then I read about the fit that Madalyn Murray O'Hair threw.

As the link mentioned, the astronauts aboard Apollo 8 had wanted to read a passage from Genesis 8 during their mission into space.  They had wanted to broadcast their reading across the airwaves, but O'Hair threatened to sue the U.S. government if they went ahead with their plans on the grounds that they were government employees on duty, and should not be associated with a religious expression thanks to the separation of church and state.  Because of that headache, NASA didn't allow Aldrin to publicly air his communion on Apollo 11.

O'Hair passed away back in 1996 so it's quite literally a dead issue, but my reaction upon reading this story was, "To hell with you, lady."

Pun intended on that one.

Why do atheists look for excuses to get pissed off about any religious individual making an expression of their faith?  What bothers them so much about our faiths that we have to keep them bottled up at all times?  And why oh why do they have this elitist attitude for feeling "enlightened" that they've "figured out" that there is no God?

Atheists can disagree with me all they like, and I really don't care. What pisses me off is that they're so concerned with people of all religious backgrounds and faiths being open about their faiths, they in fact become the very thing they supposedly are trying to stop: they force feed their own beliefs on others and essentially spread the idea that their civil liberties are more important than those of the people they disagree with. If that's not irony, I don't know what is.

I can at least respect people like Joss Whedon (writer/director of The Avengers and creator of shows like Buffy the Vampire Slayer) because even though he is an atheist, he at least will write characters in his films who have religious beliefs, like Captain America in The Avengers for one.  He doesn't place his own ego or beliefs ahead of other people who may disagree.  I'm okay with that.

There is one great irony that gets a little payback towards any of these angry atheists like Madalyn Murray O'Hair who are still out there today, and that is "In God We Trust" has been the official national motto since 1956, and the phrase appears on all American coins and $20 bills.  Add to that the line "One nation, under God" in the Pledge of Allegiance, and "God Bless America" being sung at baseball games across the country.  Things like that give me a little satisfaction knowing bitter atheists still have to acknowledge the vast majority of Americans and people worldwide believe in a God of some kind.  I'd call that vindication.

Saturday, July 20, 2013

There's Nothing Wrong With Needing a Little Help

Back around the beginning of this year, I started thinking about seeing a therapist.  There were a number of reasons why the idea popped in my head, and I did a little reading on the subject.  I even talked to a couple close friends to get their insight, mostly ones who I knew had already been to a therapist in the past.  They all encouraged me to go ahead with it, considering the benefits they had gotten from therapy.

Then came the procrastinating.  I kept thinking, "Oh, I'll go find one.  Next week."  A week turned into two weeks, then four weeks, and then next thing I knew six months had gone by and I still didn't do anything about it.  Denial had crept its way into my head too, fooling me into thinking maybe I didn't really need one after all.  I told myself I'm fine on plenty of occasions, and that I didn't think I needed a therapist like I had first thought I did.

The past few days taught me otherwise.

I'm not going to go into the deep details because they're too private, but I realized earlier this week that I need to find a therapist.  I don't care if she tells me I'm overreacting in needing to talk to someone; hell, if she does tell me that I'll probably be relieved.  Still, I'm pretty confident that I could use some professional insight instead of just some family members or friends telling me what I want to hear.

Last night I think was the confirmation more than anything else that I need some mental help.  I went to bed after a night out with my friends, and I had a dream about my family.  I've talked on here a few times about how my family has become very disjointed since my parents' divorce, but the effect it's had on me has been greater than I've estimated.  I dreamed that somehow my parents chose to reconcile and got back together, eventually remarrying.  It was one of those dreams that almost felt like reality to me, and when I had woken up I didn't realize at first that it was merely a dream.  When the truth did settle in on me, I felt something like disappointment, though that word is far too soft to describe my reaction.  I regretted that I had woken up, wishing that I could go back to that mental fantasy.

I had already called a local therapist and set up an appointment for Monday evening after work a couple days ago, so this dream wasn't the catalyst for my choice.  It was, however, more evidence to confirm the necessity for working through a lot of emotional baggage that I've been carrying around.  I wouldn't be the least bit surprised if I found out there was plenty more issues that I'm not already aware of that I need to work on as well.  Time will tell just what kinds of issues I have buried deep inside me, and how long it will take for me to work on them.

I haven't yet decided on just what kinds of details I will share on here regarding my sessions.  It'll likely depend on the kinds of things we discuss, and the things I learn about myself.  The good thing is that I've gotten over my initial procrastination and denial, and it "only" took me six months to figure that part out.

I don't know how long the road is ahead of me, but there may be some hope.