And as I write this, my hamstrings are still saying some nasty things to me!
I was hoping to maintain at least a slow jog throughout the race, but that went out the window as soon as I hit the first big hill. The course ended up being more difficult than I expected. (I’ve driven through that area dozens of times. It doesn’t seem too bad in a car! It’s a lot different when you’re on foot!) I tried to jog where I could, but mostly, I walked. I did try at least to maintain a brisk walk, although that didn’t always happen, either. One piece of advice that my CrossFit coach gave me beforehand was, “just keep moving. Don’t stop.”
I did have to stop a couple of times to retie my shoes, but aside from that, I pretty much heeded that advice. I didn’t stop!
One of my favorite moments happened in the middle of the park. A kid had a hand-drawn sign with a Super Mario Mushroom Power-Up and a caption that said “Hit sign to power up!” I don’t know how many people used that to push themselves, but for me, it worked! I touched the sign and broke into a jog — albeit briefly.
A little past the halfway point, one of my friends from the office came up alongside me, and we pretty much did a steady walk together for the remainder of the course, all the way to the finish line.
There were a couple of down moments yesterday. After the race, I parked in a pay lot, didn’t pay, and got towed. (I did manage to get my car back.) Also, they ran out of T-shirts in my size. I was disappointed about not getting a shirt! But nevertheless, it was a good time! It was a beautiful day out — temps were cool and comfortable, and it was sunny. And in addition to my co-workers, I saw several friends at the event. I met my co-workers at a bar after the race (it was while I was here when my car was towed). We ate and drank, and I spoke to a number of people from my office whom I usually don’t talk to!
All in all, it was a good time. I have to admit that I had fun yesterday! Has it changed how I feel about running? Well… not yet. Will I do this event again? Well… more than likely!
During my lunch break, I was perusing the ESPN website and stumbled across this article. It contemplates whether or not a .300 hitter (in baseball, for those of you who are sports-challenged) is meaningful anymore. As a baseball fan, the article caught my attention. I didn’t read through the entire article (it ended up being a much longer read than I expected — too long for me to read while on a lunch break at work), but from what little I did glean from it, a couple of things struck me.
First, they talk about Mickey Mantle‘s batting average and how important hitting .300 was to him. That struck me a little funny, because (as far as I know — as I said, I didn’t get through the entire article) there was no mention of the fact that he actually finished with a batting average under .300. His career batting average was .298.
The second thing that struck me was (Yankees’ first baseman) Luke Voit saying how he felt that “feel like batting average isn’t a thing now.” Indeed, baseball is a much different game than it was, say ten, twenty, or thirty years ago. Analytics are a big part of statistics these days. A lot of stats that are prevalent now — WAR (wins above replacement), exit velocity, OPS (on-base plus slugging), etc. — didn’t even exist when I was a kid growing up, closely following my Yankees. Back when I was eating and sleeping baseball, hitting was about the triple-crown statistics — batting average, home runs, and runs batted in (RBIs). But now, we have “slash lines,” on-base percentage, slugging percentage, and so on. Even as big of a baseball fan as I am, I haven’t a clue about many of these “new age” stats. I still have no idea what WAR represents, I’m not completely sure as to what the numbers in a slash-line are, and I don’t know what constitutes a respectable OPS.
That got me thinking about how statistics have changed over the years, and whether or not that applies to statistics outside of baseball (or sports, for that matter). Maybe people who study data analytics for a living might know this better than I do, but what business statistics have a different meaning now than they did ten, twenty years ago? Are there any numbers from way back when that I should now take with a grain of salt?
I’m sure there are many examples of this outside of sports, but I struggled to come up with any. Off the top of my head, I remember how a company where I once worked made a big deal out of perfect attendance — to the point that they gave out perfect attendance awards at the end of the year. However, that had to contend with situations such as coming to work when you were sick, and so on. Do you really want someone who’s sick coming into work? These days, workplaces do not want sick people in the office, and with the advent of work-at-home provisions, perfect attendance isn’t so meaningful, anymore. (By the way, my understanding is that company no longer recognizes or rewards “perfect” attendance.)
So I suppose the takeaway is, how well do statistics age? Can they be compared with the same statistics now? What needs to be considered when analyzing statistics from years ago? It’s true that numbers often tell a story, but in order to get the full picture, you also need to understand the full context.
I just registered for my very first road race: the 2019 CDPHP Workforce Team Challenge. I have never run any kind of registered road race* before. This will be my first.
(*I have, however, participated in a registered bicycle tour before. But I feel a lot more comfortable about my bike riding than I do my running.)
I will say that running and I have never really gotten along. It is not, I repeat, not one of my favorite physical activities.
I’ve been active in CrossFit since 2015. I’ve made big strides since I started. Although I still have a lot of things that I need to improve, I can do a lot of things now that I couldn’t when I first started.
And as it turns out, one of the things upon which I’ve improved is running. One particular coach tends to push me pretty hard (in a good way). Whenever a 5K run has come up in a CrossFit WOD, I’ve toyed with scaling it down to a shorter distance. It was this particular coach who said to me, “nope, you’re not scaling it. You’re running the full 5K!”
And it’s for that reason why I feel I’m capable of participating in this event.
Granted, I use air-quotes when I say “run.” It’ll probably be more like some jogging, some walking, and some stumbling. (And this event is longer than 5K; it’s actually 3.5 miles.)
If you want to get better, you need to step out of your comfort zone. I’d say that this definitely qualifies.
For reference, my best 5K time is 50:18. We’ll see how this goes. Wish me luck.
“I gotta run a little faster; I gotta reach for the sky; I gotta come a little closer; even if I lose, I gotta try…”
— Kansas, “Inside Of Me”
“Try not. Do. Or do not. There is no try.”
Every Saturday, my CrossFit gym invites friends to join members for workouts (“Bring A Friend Day,” as it’s called). It’s a little bit of a misnomer, as guests don’t necessarily have to be friends — as one coach likes to describe it, “bring your friends, neighbors, coworkers, colleagues, enemies, ‘frenemies,’ whomever.” It doesn’t necessarily have to be by invitation; anyone interested in trying CrossFit can come to these classes — a type of “try before you buy” session, if you will.
I’ve tried to get friends to go to these sessions, with mixed success. Those who do enjoy the sessions, but I have yet to have one friend (other than my wife) try it out and join the gym. (Admittedly, there are fringe benefits for me to get someone to sign up — a month of free membership, for example.)
What’s interesting is those who don’t try it and outright refuse my offer to join me. (As I tell people, joining me in these sessions pretty much guarantees that I will work out on Saturday!) I tried to tell one friend that I thought CrossFit might benefit her. Not only did she outright refuse to take me up on it, I got the impression that she was actually scared to try it. She would not even keep an open mind about it; she just said, “I will NOT do it. Don’t ever ask me about it again.” End of conversation.
My question: why???
I would never twist anyone’s arm into trying it (well, okay, maybe friends with whom I know I can get away with it), but what I don’t completely understand is why people fear it. I get why people won’t do things like go bungee-jumping (disclosure: I am deathly acrophobic), eating exotic foods (I’ll try almost anything, although I draw the line at anything that has more than four legs, shellfish excluded — Andrew Zimmern I’m not!), or do something on a dare. But why are people afraid to try CrossFit?
I think part of it is that it’s human nature to fear what you don’t know. People will see these images of CrossFit (I often post what I do on Facebook) and immediately get the impression that they’re expected to be able to lift large amounts of weights, be pushed to do double-unders, or be able to do pull-ups right off the bat. The fear of “gymtimidation” comes into play. People who fear it are likely afraid of being embarrassed or injured.
First, one of the selling points of CrossFit is that anyone can do it. I’ve seen people as old as eighty (and even more!) in the gym. I once saw a guy who had the use of only one arm in a workout (it was interesting watching him on a rower and an Assault bike). I’ve seen newbies who struggle with weightlifting form. Even I have my own struggles; I can’t (yet) do any moves that involve pulling myself up (pull-ups, muscle-ups, rope climbs, etc.), I have trouble with movements that involve squatting (I was diagnosed with osteoarthritis in my knees), and I’m not exactly the fastest runner (for me, there’s almost no difference between a jog, a sprint, or a fast walk). Heck, even some warmups can sometime leave me out of breath.
However, one of CrossFit’s selling points is that it is scalable. You are never asked to do anything you are not capable of doing. If you have trouble with pull-ups (like I do), you can do barbell pull-ups or ring rows. Unable to do a certain type of weightlifting movement? Don’t worry about the weight; instead, use a lighter weight, an empty bar, or even a PVC pipe, and practice your technique. Whatever movement gives you trouble, there is always a way to scale it that will allow you to perform it to your capabilities.
I’m sure the fear of being injured comes into play. As I just said, you’ll never be pushed to do what you’re not capable of doing. But one of the selling points for me is that CrossFit emphasizes technique. If you are not sure about how to do a movement, coaches will teach you how. If your form has issues, coaches will tweak it so it is better. Technique is key to anything: the better your form, the less chance you’ll be injured.
I also think the intensity is a factor. CrossFit can get very intense. Admittedly, there isn’t a lot that’s enjoyable about working your tail off to the point where you’re gasping for breath and end up lying on the floor. That’s something that can scare people off. However, how hard you work out is up to you. Intensity is what you make of it. But why is it so intense?
I think it’s because the majority of people who take CrossFit seriously want to improve. People push themselves because they want to get better at what they do. Did a deadlift weight of 305 pounds? Next time, I’m going to try 315. Run 5,000 meters in under ten minutes? Next time, shoot for nine. CrossFit is about making yourself better. While you are not asked to do anything you can’t do, you are asked to challenge yourself and push the limits of what you can do. Even my own gym’s motto is “(Be)tter” (as in, “be better”). I wrote before that you have to get uncomfortable in order to improve. Making yourself better involves going out of your comfort zone. How much discomfort — intensity — you decide to put into it is up to you.
Finally, there’s the phenomenon that Planet Fitness refers to as “gymtimidation.” People are embarrassed by their lesser skill level and are often intimidated by performing in front of other people who are in much better shape. This attitude does not exist in CrossFit. Everyone — even the elite athletes — roots for everyone else to succeed. I remember one time watching the CrossFit Games on TV and hearing the commentator say, “CrossFit is probably the only sport in which the person who comes in last gets the loudest cheers.” Even in events where athletes are finished, they will often go back out into the field to cheer on and encourage those who are still working through the event. Here’s a secret: everyone, at some point in their lives, was a beginner at something. Someone once said that one of the worst phrases ever coined was “do it right the first time.” It’s almost never done right the first time. Fear of embarrassment should never be a factor in trying something new.
Although people have their reasons why they don’t want to try CrossFit, fear should not be one of them. CrossFit can be a fun and exciting way to keep fit. Give it a try. Who knows? You might just get hooked — like I did!
And if any of my local friends are interested in hitting a Saturday “Bring A Friend” WOD, hit me up!
I watched this game on a TV at a restaurant where I was having dinner with my wife. I remember watching Brett Gardner getting thrown out as he was caught in a rundown between third and home. I remember thinking, “now the man on third is erased. What were you thinking, Brett?”
As the Times article points out, it ended up being a fateful decision by (Orioles pitcher) Dylan Bundy. Had he thrown the ball to the shortstop instead of his catcher, he potentially could have turned a double play to get his team out of the inning. Instead, the Yankees, with an extra life, rallied in the inning to go up by a score of 5-0 (highlighted by a Tyler Wade grand slam). The Yankees ended up winning, 9-0 (making me, a Yankee fan, happy).
But this article isn’t about the game. It’s about the instant decision. In this case, a quick decision ended up affecting the outcome of a ballgame.
Think about all the times in your life when you’ve had to make an instant decision on your feet. We’ve all had them. How did they turn out? Good? Bad? Did they end up changing the course of your life, or were they just blips on your lifetime radar screen?
I’m sure there’s some kind of psychology as to how your background — upbringing, education, etc. — might play a role regarding the kinds of split-second decisions you make, but this is a subject about which I know nothing. Rather, it got me thinking about the idea that quick decisions can have consequences. In the scheme of things, many of them might not have any effect. But depending on the time, place, and circumstances, such decision-making could have disastrous consequences — or result in the opportunity of a lifetime.
Edit: This is the first of a series of articles (I hope!) in which I’m trying to teach myself about BI. Any articles I write that are related to this, starting with this one, will be preceded with “#BI101” in the title.
As I stated in a previous article, one topic about which I’m interested in learning more is business intelligence (BI). For those of you who are new to BI, it is a broad topic. In a nutshell, it can probably be described as “consuming and interpreting data so it can be used for business decisions and/or applications.”
I’ll admit that I don’t know a lot about BI (at least the fine details, anyway). I did work a previous job where I touched upon it; I was tasked with performing some data analysis, and I was introduced to concepts such as OLAP cubes and pivot tables. I’ve gotten better at creating pivot tables — I’ve done a few of them using MS Excel — but I’ll admit that I’m still not completely comfortable with building cubes. I suppose that’ll come as I delve further into this.
A while back, my friend, Paresh Motiwala, suggested that I submit a presentation for Boston SQL Saturday BI edition. At the time, I said to him, “the only thing I know about BI is how to spell it!” He said to me (something like), “hey, you know how to spell SQL, don’t you?” Looking back at the link, I might have been able to submit (I didn’t realize, at the time, that they were running a professional development track). That said, Paresh did indeed had a point. As I often tell people, I am not necessarily a SQL expert — I know enough SQL to be dangerous — nevertheless, that does not stop me from applying to speak at SQL Saturday. Likewise, as I dive further into this topic, I’m finding that I probably know more about BI than I’ve led myself to believe. Still, there is always room for improvement.
To tackle this endeavor, once again, I decided to jump into this using a subject that I enjoy profusely: baseball. Baseball is my favorite sport, and it is a great source of data for stat-heads, mathematicians, and data geeks. I’ve always been of the opinion that if I’m going to learn something new, I should make it fun!
Besides, the use of statistical analysis in baseball has exploded. Baseball analytics is a big deal, ever since Bill James introduced sabermetrics (there is some debate as to whether James has enhanced or ruined baseball). So what better way to introduce myself to BI concepts?
For starters, I came across some articles (listed below, for my own reference as much as anything else):
Since I’m using baseball to drive this concept, let’s use a baseball example to illustrate this.
Let’s say you’re (NY Yankees manager) Aaron Boone. You’re down by a run with two outs in the bottom of the 9th. You have Brett Gardner on first, Aaron Judge at bat, and you’re facing Craig Kimbrel on the mound.
What do you do? How does BI come into play here?
Let’s talk a little about what BI is. You have all these statistics available — Judge’s batting average, Kimbrel’s earned run average, Gardner’s stolen base percentage, and so on. In years BS — “before sabermetrics” — a manager likely would have “gone with his gut,” decided that Judge is your best bet to hit the game-winning home run, and let him swing away. But is this the best decision to make?
Let’s put this another way. You have a plethora of data available at your fingertips. BI represents the ability to analyze all this data and provide information that allows you to make a good decision.
If Aaron Boone (theoretically) had this data available at his fingertips (to my knowledge, Major League Baseball bans the use of electronic devices in the dugout during games), he could use the data to consider Kimbrel’s pitching tendencies, Judge’s career numbers against Kimbrel, and so on. BI enables Boone to make the best possible decision based upon the information he has at hand.
I do want to make one important distinction. In the above paragraphs, I used the words data and information. These two words are not interchangeable. Data refers to the raw numbers that are generated by the players. Information refers to the interpretation of that data. Therein lies the heart of what BI is — it is the process of generating information based upon data.
What’s there to know about BI?
I’ve already mentioned some buzzwords, including OLAP, cubes, and pivot tables. That’s just scratching the surface. There’s also KPIs, reporting services, decision support systems, data mining, data warehousing, and a number of others that I haven’t thought of at this point (if you have any suggestions, please feel free to add them in the comments section below). Other than including the Wikipedia definition links, I won’t delve too deeply into them now, especially when I’m trying to learn about these myself.
So why bother learning about BI?
I have my reasons for learning more about BI. Among other things…
It is a way to keep myself technically relevant.I’ve written before about how difficult it is to stay up-to-date with technology. (For further reading regarding this, I highly recommend Eugene Meidinger’s article about keeping up with technology; he also has a related SQL Saturday presentation that I also highly recommend.) I feel that BI is a subject I’m able to grasp, learn about, and contribute. By learning about BI, I can continue making myself technically valuable, even as my other technical skills become increasingly obsolete. Speaking of which…
It is a subject that interests me. I’m sure that many of you, as kids, had “imaginary friends.” (I’ll bet some adults have, too — just look at Lieutenant Kije and Captain Tuttle.) When I was a kid, I actually had an imaginary baseball team. I went as far as to create an entire roster full of fictitious ballplayers, even coming up with full batting and pitching statistics for them. My star player was a power-hitting second baseman who had won MVP awards in both the National and American leagues, winning several batting titles (including a Triple Crown) and leading my imaginary team to three World Series championships. I figured, if my interest in statistics went that far back, there must be something behind it. Granted, now that I’ve grown up older, I’m not as passionate about baseball statistics as I was as a kid, but some level of interest still remains, nevertheless.
It is a baseline for learning new things. I’ve seen an increasing number of SQL Saturday presentations related to BI, such as PowerBI, reporting services, and R. I’m recognizing that these potentially have value for my workplace. But before I learn more about them, I also need to understand the fundamental baseline that they support. I feel that I need to learn the “language” of BI before I can learn about the tools that support it.
So, hopefully, this article makes a good introduction (for both you and myself) for talking about BI. I’ll try to write more as I learn new things. We’ll see where this journey goes, and I hope you enjoy coming along for the ride.