Thinking out loud: Fairness and Ethics

A close friend of mine sent me this interesting Planet Money article the other day

The Fall And Rise Of U.S. Inequality, In 2 Graphs

I don't see why they needed 2 graphs, because they seemed pretty redundant to me. Either way, here's the graph:

It's a really nice way of showing the income inequality in the US, and how's it's changed over time. The take home point is that the richest 1% have seen a huge increase in their income while the middle class has been more or less stagnant for the last 20-30 years.

We talked about this for awhile, but I kept coming back to a question that I come around to in most discussions:

Is this bad? 

This is so tricky for me to answer. I have the gut reaction that most people probably have, and I say to myself "that's not fair!" But then I ask myself, "So what? Life's not fair."

In my discussion with my friend, I realized that this is a topic in which we have vastly different opinions. His approach to determining whether something is ethical often involves asking how fair it is. The more fair it is, the better. And less fair things are bad things.

I find it better to detach myself from questions of fairness in this instance, since my opinion of fairness comes from an emotional reaction, which is often very irrational.

However, I'm sort of a hypocrite, because I think questions of fairness have a place in many other issues. Here's a few of them where I think fairness is really important:

• The gender pay gap
• Racial profiling by police
• Mass incarceration of minor crimes with mandatory minimum sentences

But can I have it both ways? Can fairness be important some times and not others?

I'm not sure that I have an answer to that question yet.

Florida to North Carolina

So we're settling into our new place in Raleigh, North Carolina. Raleigh is such a nice change from the heat and congestion of Miami.

The move felt like it took forever. We tried to find someone to take over our lease, but in the end we had to pay a penalty to get out of lease in Miami. Then my boss, Brian Mapes, was very generous and let us stay in a little building behind his house in Coral Gables that he referred to as a "mother-in-law cottage". It was a very cozy little spot that were are eternally thankful for, since it made our transition much easier.

On our way to North Carolina, we stopped for a night in South Carolina. Andrea's aunt and uncle from Iowa have a house near Mrytle Beach that another Aunt and cousin just happened to be visiting while we were passing through. It was great to see them and have a nice (and free!) place to stay.

The trip was about 12 hours of driving, which was not bad. The hardest part is that we had to drive separate cars, since we had 2 cars and 2 drivers. We listened to a LOT of podcasts. What did people do before podcasts?!?! Andrea listened to one about beer called Strange Brews, which was pretty interesting. I found that it can get boring though, since it's just a couple guys talking to each other about beer. Apparently there's a few podcasts about beer out there. I would never have guessed!

The most addicting podcast was called "Serial". It's one story, told in a dozen episodes or so. The story was about this guy who got convicted of killing his ex-girlfriend. The problem is that the evidence for convicting him was really spotty. But on the other hand, there's no better explanation for why someone would kill her. I highly recommend this podcast for anyone needing to kill a lot of time.

We made it to Raleigh, safe and sound. We found a nice little apartment and that in a really great location so we can bike almost anywhere that we need to go! Andrea got a job at a local bottle shop. I'm still wrapping up research from my last job, but I'm really enjoying work these days.

That's all the news for now!

New Year's Resolutions: 2015

2014 was a huge year for me personally. Here's the highlights:

• Finished my Ph.D.
• Got my first real science job at the University of Miami
• Got engaged to the love of my life (!)
• Travelled to Germany
• Received the NSF AGS fellowship

Each of those things have left me feeling very lucky. Sometimes I feel bad that it took me longer than most to finish my Ph.D., but that's hardly something to complain about, given that I've found a career that I really enjoy, which something a lot of people don't have.

Last year I made a few goals, one of which I failed to meet. Here's the list from 2014:

• run at least 2x per week on average (success!)
• have 3 publications either published or submitted (fail)

I had 1 paper get published, and I submitted another paper in late December, so that's why I failed on the second goal. This year I'm gonna set the same goal again. If the recently submitted paper gets published, that will count. So I have to submit 2 more papers. This shouldn't be hard since I still have most of my Ph.D. dissertation un-published, and I've got all this new interesting stuff from my postdoc job with Brian Mapes at UM.

The running goal was new for me because it was quantifiable. In the past I had made an effort to do similar things, but I was always too vague about it. Like I would tell myself to "run more", but at the end of the year I never had any idea whether I actually done what I hoped to do. This year I made a serious effort to get better about tracking my running. Part of this was to use an app called Strava, for tracking miles and such. Strava is my favorite running/biking app for a few reasons, one of which is how it keeps stats for you. However, since my goal was to run a certain frequency per week, I need to calculate my own stats.

I decided to use Google drive to make a spreadsheet. The great thing about doing it this way is that I can edit it from anywhere, like my phone or office computer. Here's a snapshot of the data for 2014:

I really like this layout that I settled on. I can add more stats to the right hand side if I need to. This layout is nice and compact, and even is easy to work in leap days! The newest version of Google's spreadsheet program has lots of new and useful functions, which I make heavy use of. a good example is my formula for the "#/week" column:

= iferror(COUNTIF(B2:AF2, ">0")*7/count(B2:AF2))

The "iferror" function is a nice way to not have "ERROR" messages all over the place when you are dividing by a "count", which can often be zero.

Another nice thing about Google spreadsheets is the plotting capabilities. Here's a plot of the "# per week" and "miles per week":

The big dip in the middle is when we were travelling in Germany. in order to pack light I didn't even bring my running shoes, but I did do a ton of walking, so I don't feel bad about it. But because of some large gaps in my running, I barely made my goal at 2.03 runs per week!

So now I need to make some new goals for this year. I'm gonna up my weekly frequency, and also add a goal on getting my pace much faster. To do this I've made a new Google spreadsheet that can average times! it's pretty sweet. While I'm at it, I'm also adding a spreadsheet to track my weight, so this year's end-of-year summary should be pretty interesting.

To wrap up, here's my resolutions for 2015:

• Run 2.5 times per week on average
• Get my average pace down to at least 9:30
• Get my end of year weight down to 165 (which will be harder if I start lifting again)