That Sinking Feeling

Today’s economic topic will be the Sunk Cost Fallacy. A sunk cost is something you’ve spent money (or other investiture) on and you cannot recover said money (or investiture). The $4.50 you spent on a latte this morning is a sunk cost.  So is the $90 you spent on shoes last month. And, oddly enough, so is the “free” doughnut you ate this morning, because even though it was monetarily free, it wasn’t calorically free – you “paid” in terms of calories for the day and, assuming you weren’t near-bulimic afterwards, you cannot retrieve those calories.  (And even if you did attempt to purge, you are still dealing with a sunk cost).

Generally speaking, it doesn’t make sense to take into account sunk costs when making a decision for future investiture – e.g., whether or not you spent $4.50 on a latte should not impact your decision as to if you will be buying a latte later today. You’ve already spent the money and can’t recoup it, so factoring in the presence it *would have* made in your budget is specious, you need to look at where your budget stands now. But humans don’t tend to work this way due to loss aversion.  They tend to frame an overall project to include what has been spent as well as what will be spent (time, effort, etc.) and look at it on the whole rather than what is left. One of the oddest presentations of this I am most guilty of, as are, I suspect, many of my friends: the Sunk Cost Doughnut.

I seem to be focusing on doughnuts, and this is because I had one today.  I am supposed to be watching my weight (I’m currently watching it nudge up) and today someone (Ms. Krieant, to be exact) brought in Top Pot Doughnuts, which may in fact be my favorites.  I have a workout buddy who insists that you can eat whatever you want as long as you work out enough and he is right, but he is also 25 and has been through OCS and it’s not enough for him to do pull-ups, he has to do them with a 50lb-weight strapped to his stomach. His and my mileages tend to vary.

sprinkles
mmmm doughnuts

At any rate, today I ate one (1) Chocolate with Rainbow Sprinkles doughnut, at a caloric cost of 510 calories. That would be 1/3 of my supposed day’s calories, and so it is really, really hard not to take into account my sunk cost (doughnut/510 calories) and say “well, I’ve screwed up the diet today, so I will just start again tomorrow”. On the whole this is NOT logical because in theory I can pay attention to my caloric budget and be “good” for the remainder of the day, and only come  in a “little” over budget.  If I frame my caloric choices in light of the Sunk Cost Doughnut, though, and eat whatever I want,  I would come in drastically over budget.

A suggested method by economists is to evaluate future costs and avoidable future costs to establish the true prospective cost for the day (E.g., I must have some form of dinner (future cost), it probably shouldn’t include bread or fat (avoidable future cost)).  And so, as I use my “MyFitnessPal” app and truthfully admit to my 510 calorie digression, I sit here re-evaluating my planned caloric expenditures for the day.

They’re serving birthday cake down the hall.

This is Going to Hurt You More than Me

Greetings from the ending of a self-imposed blogging silence: I got the aforementioned email and am happy to state that I will shortly be joining Microsoft.  Sur La Table was very diverting and offered many challenges with respect to data, but it’s hard to pass up an opportunity to work in, and with, big data.

As a result of that interview loop, plus some interviews I did for an open position we have at Sur La Table, I’m here to write something Very Important: Don’t Lie on Your Resume.

Typically when I am called in to conduct a technical interview, I read the candidate’s resume, and then ask the hiring manager how technical they want me to get. If it’s me, and I’m hiring for a developer, I’m going to get very technical, and you’re going to spend 100% of your time with me at the whiteboard. If it’s for someone else, and I’m hiring for say, a PM, or a QC, or technically-minded-but-not-otherwise-a-developer role, I’m still going to test you on skills you state in your resume.

So when you tell me that you have a lot of experience with SQL, or that you’ve been using SQL for five or six years, I’m going to run you through the basics. Either of those statements will tell me that you know the four major joins, you know the simplest way to avoid a Cartesian product, you know how to create data filtration in a join or in a where statement, and you know how to subquery. I’m not even getting to more advanced parts like transactions with rollbacks, while loops, or indexing — the aforementioned list are what I would characterize as basic, everyday SQL use.

Imagine my dismay, then, as an interviewer, when after declaring (either verbally or on your resume) that you are a SQL expert, you can’t name the joins. Or describe them. Or (worse) describe them incorrectly. When you say you know SQL, and then prove that you don’t, it makes me wonder what else is on your resume that you “know”, that is less hard to prove (in the interview) that you don’t. The default assumption, for the protection of the company, is that your entire resume is a raft of lies. It’s the surest way to earn a “no hire”.

It would have been far better to state the truth: someone else wrote SQL scripts for you, told you what they did, and you were adept enough to figure out when there was a disparity in the output. That does not mean you “know” SQL, it means you know how to run a SQL script. This gives the interviewer an honest window and the ability to tailor your time together (remember, they’re getting paid by the company to spend time with you, if it’s productive it is not a waste of money) to figure out your strengths and weaknesses. Having just been hired into a position that works with big data, where I was honest that the largest db I have worked in and with was about 3TB, I can attest that it’s really hard to have to look a hiring manager smack in the eye and say: “I have 90% of what you have asked for but I’m missing that last 10%”. It gives them the opportunity, however, to decide if they’re going to take the chance that you can learn.

If they’ve already learned you’re honest, then that chance-taking looks better in comparison.

I hate waiting.

For reasons that I can’t (and therefore won’t) get in to right now, I’m obsessively waiting on an email. One. Specific. Email.

This sort of obsession is hindered by the very reality that on any given day, I get about 200 work-related emails (if you include the junk mail from vendors who seem to think I’m hiring scads of people or want to outsource scads of work) and probably 50-70 personal emails (not including the invitations to enlarge my manhood or acquire millions from a long-lost eccentric cousin in Nigeria). The fact that this one particular email will come within a 5 to 10 day period, which means it represents 0.04-0.6% of my LEV (Legitimate Email Volume) does not help.

When waiting for that one email, a couple of behavioral shifts occur, including, but not limited to:

  1. Obsessively checking the iPhone to see if it arrived there
  2. Re-checking the desktop browser to see if it arrived there
  3. Keeping a browser tab open to email to see when the tab status changes to indicate a new mail has happened, and when you notice it does your stomach gets all giddy, and then you change tabs to open this one and discover that your Amazon order has shipped, and the giddy excitement crashes away into a wave of “meh”. Inbox(1) does not necessarily equal joy.
  4. Questioning whether or not you really expected the mail to come between 3:20am and 5:20am, which was this morning’s particular brand of insomnia (no, that wasn’t reasonable). Neither was it reasonable to expect it before 8am yesterday, or after 8pm, either.
  5. Trying to convince yourself that when they said 5-10 days they really meant “don’t expect it before 5 days, and from then on expect it within five days of that”, and not believing that *at all*
  6. Repeat steps 1-5.

There are two possible outcomes to this email: one is Tigger-esque mind-blinding joy and excitement. The other is a sense of doubt, self-questioning, and (eventually) redoubled efforts. There does not appear to be a contingency I can plan for beside these two results.

I am on day 2 of 10.

Free Premium

I recently posted about LinkedIn and how I use it; I recently was the recipient of a FREE month’s worth of LinkedIn Job Seeker Premium, and this post is about my experience with that. (NB: I am not paid by, or influenced by, anyone at LinkedIn, save possibly Daniel Tunkelang, who is their Head of Query Understanding and a wicked brilliant person. And no, he didn’t pay me to say that. It’s just that he’s an “influencer” of mine on LinkedIn).

The short of it is my free Premium Membership ends in four days and when it does I will let it end (or more accurately, I will proactively kill it). Much like other “free introductions” the feedback loop is a negative one: the assumption is if you don’t actively end it then it continues on, and bills your card appropriately.  I am letting it end not because I do not feel it is a good program, but because it is not particularly useful for me.

First, the basics: LinkedIn Job Seeker Premium has a check sheet of the advantages of paid membership here. At $25/month (billed annually, so $300/year) it provides you with the ability to see who’s looked at your profile (the regular free membership shows you a subset), you can see full profiles of people up to 3rd degree, you can leverage LinkedIn’s “In Mail” and receive a bump of introductions, and a few assorted other UI niceties (up to 250 results per search, etc.).

whodatFor me the attraction was the ability to see everyone who has looked at my profile, and here’s the rub: it does show you everyone, but only if they want to be seen. For example, if someone has not logged in and/or is surfing anonymously, with Job Seeker Premium you will see an individual, faceless avatar saying “someone” looked at you; you will have no idea who they are. So if 12 total people looked at you and 3 were not logged in and/or were surfing anonymously, you see 9 photos/bios and 3 blank avatars. This is frustrating for someone who wants to inspect the inspectors, but totally understandable from an execution perspective: LI has no idea who you are until you are logged in, so there is no way to let someone else know who you are, either.

Then there’s the fact that I now know that “12” people looked at me, instead of “5”. I also get handy “last 90-day” graphs with informational snippets like “7 viewers had the title of Technology Manager” or “16 viewers work at Microsoft”.  I can also parse out how they found me: search, 2nd or 3rd link, etc.

icon_gold_inbug_74x74As part of Job Seeker Premium you get a little yellow and white icon in your search results (when people search for you, that is) that indicates you’re on Job Seeker. This should be a very large flag to any potential recruiters that you’re open to inquiry, and the inquiries just come flooding in, don’t they?

In my case, not.  I did get one offer of a contract for Salesforce Development (something that is not anywhere on my profile; I have worked with SF developers on getting two Salesforces (Salesforceii?) to talk according to a set of business rules, but haven’t done it myself, thanks) in another state. For someone who has been Manager and above titled, etc. it was an odd request and reaffirms my belief that people don’t actually read.

The other thing that messed with the experience is that I used this opportunity to update my profile and add on consulting work that I have been doing on the side (for about a year) and the recent appointment to a non-profit Board. This generated a bunch of “Congratulate Bobbie on her New Job” notices to those I was linked in to, and when your own best friend emails you to ask about your “new job” it’s time to add a control to the announcement features, methinks.

The rest of the features offered by Job Seeker Premium were unused and I’m not entirely clear how someone looking for a job would actually use them. To wit: as a free member, I can send in-mail to anyone I’m linked to, and can “hack” that by attempting to link to someone I don’t know (e.g., recruiter) and putting my introductory email in that “link to me” email.   If I’m looking to get a job, rather than find someone for a job, I don’t know how useful it is for me to see the full profiles of 3rd-level linked people; I’m more interested in the recruiters seeing me.  I’m not sure how the ability to see up to 250 people per search is useful, unless the proposition is that I will try to boost my 1st-linked numbers while job searching; even then, if you can’t find someone you worked with or know in the first 100 records then you have to question if they’ll even link to you.

Now, counterpoint and contrariwise: if I were not already gainfully employed (“Congratulate Bobbie on her new old job!”) and were actively networking and really trying to get employed, I would probably pay the $300 and then pay another $200 or so for a professional headshot, and possibly another $150 for a resume analyst. I would probably have a resume for every position type I was qualified for and interested in, and would make sure my LinkedIn profile was carefully agnostic (If you are angling for a Dev Manager job you probably don’t want to over-emphasize your writing skills vs. your coding skills).

This assumes that somehow I had the cash for that (remember it’s good to have a cushion for just-in-case) and have not been unemployed for some time.  To that end, if money’s tight, I’d stick with regular LinkedIn at the free level: if someone thinks you’re what they’re looking for, the presence of the little yellow and white “in” icon is not going to further attract, or dissuade, them.

Sporting

NB: I may have previously mentioned that I’m not “into sports”, by which I mean I have not followed football or baseball or basketball teams. It’s only just recently that I’ve figured out when those seasons start and end, and that I have learned the rules of football (thanks to a SuperBowl party and the fact that my region’s team was in the SuperBowl this year. As the kids say, “Go Hawks!”) This post will therefore be unusual that it deals with sports. It will not be unusual in that it deals with gender perception and economics.

This past Wednesday some 700 thousand plus people descended on downtown Seattle to celebrate the Seahawk’s winning of the SuperBowl. Busses were jammed all morning, many folks did not go to work, kids skipped school; this was all for the privilege of standing along 4th Avenue, in the cold, hours on end, for a parade that ironically started late because those in the parade couldn’t get to their starting point because of all the people.

The parade seems to have made many people happy; my Facebook was replete with happy family photos of smiling, green-and-blue-dressed people, plus blurry photos of those in the parade. Everyone seems to have had a good time.

Nestled in that timeline, though, was a comment (actually two, from two different people), that the Seattle Storm (our local female basketball team) won National Championships twice, and no parade was had for them. (It should also be noted that the Seahawks paid for their own parade. )

In reviewing those comments the implication is, I think, that because it was a women’s team that won previously they were not “good enough” (not my words, just what I’m inferring from the context of the statement) because they were female. It doesn’t help that articles like this announced that the last time Seattle had earned a national title was when the Sonics won in 1979 (considerably before the Seattle Storm’s victories of  2004 and 2010 ). Forbes went so far as to acknowledge them and indicate they weren’t “counting” them. And yes, when the Sonics won in 1979 a parade was had.

There are two culprits here: sexism and economics.

Let’s take the simpler one: economics, specifically the concept of Supply And Demand. More specifically, there are demand differences between Women’s Basketball and Men’s Football. (It would have been nicer to have a Men’s Basketball team to weed out the gender variable, or a Women’s Football team, but alas we lost the former and the latter doesn’t really appear to exist except for the Lingere Bowl).

The Seattle Storm plays in Key Arena which holds  slightly over 17,400 seats; they play 34 games per season. 16 of those games are played “home”.  Ticket prices range from $16 to $155 with a mode of $28.  Let’s further say that 20% of anyone at an “Away” game is there for the Storm, and 80% of anyone at a “Home” game is. However, the Storm doesn’t actually sell all of the seats in Key Arena (they block off a portion, and they don’t often sell all the seats that are unblocked). 9,600 seats are actually available to sell and at times The Storm sells about 50% of those. Let’s assume similar seating volumes at away games, and or the purpose of this hack math, let’s say half of the time they’re at half, and the other half of the time they’re sold out, for a blended average of 75% capacity. So a back-of the-envelope dollar value for interest in The Seattle Storm would be about (9600*.75*.8*28*16)+(9600*.75*.2*28*18)= 2580480+725760=$3,306,240. (This obviously doesn’t include sponsorships, swag sales, etc.)

The Seattle Seahawks play in Century Link Field (the Clink) which holds about 68,000 seats and the Seahawks had sold out every one by July. The average ticket price was $220, they had 17 games in their regular season, and had 62,000 season ticket holders. Let’s just stick with the season ticket holders, as that is cash up front. (17*62000*220)=$231,880,000. (This also doesn’t include sponsorships, swag sales, etc.)

In short, there is a purchase-behavior disparity of 7000%.

That disparity is driven by not only volume (the Clink seating is 7x the amount in Key Arena used by The Storm), but also by price (average ticket price for the Seahawks is larger than the HIGHEST ticket price for The Storm).  Even if The Storm were to sell 100% of the available seats in Key Arena, they’d fall very short of economic comparability to the Seahawks in terms of fan fiscal investment.

But this isn’t telling us anything we didn’t already know: the demand for entertainment via male football is much greater than the demand for female basketball. The Sonics left in 2008 and their ticket demand is 44,000 season ticket holders, meaning that even if they sold at the same price as The Storm they would still outsell on overall ticket volumes. And so we can infer that demand for entertainment via male basketball is greater than the demand for female basketball.

And so we segue into sexism: essentially that people are making economic demand decisions based on gender preference in sports.  As a society we tend to like our sports hyper-competitive, confrontational, metricized and self-aggrandizing. Nowhere is this more evident than how we idolize the players, how we purchase team jerseys and say “us” vs “them” when talking about upcoming games. “We won”, “they lost” is how games are summed up; followed by an earnest delve into strategic review of plays, the metrics and statistics behind those plays, and player strength.

These are not things we encourage in our girls. Much has been made of now-pink Legos and Goldie Blox, of Sheryl Sandberg Leaning In and the overall interest in getting More Girls into STEM. We enroll our daughters in soccer just as readily as Girl Scouts, we tell them they can be anything when they grow up. A girl who is hyper-competitive though is deemed less attractive, a girl who is confrontational is deemed a bitch. (Let’s not even touch self-aggrandizing). Women’s basketball is not televised nearly as much, or touted as often, as men’s.

We make these choices, and display our preferences, by our societal expenditure. The Seattle Storm will have a parade when the larger group decides that the athletic achievements of women is as representative and worthy as that of men, and that will have to come from increased ticket sales, which will in turn have to come from increased demand.

Linking In

I am, to no great surprise, a fan of social media. You will find by me near-daily tweets, posts on Facebook, check-ins on Foursquare. Lately, I’ve been playing a lot on LinkedIn, trying certain features, and have been genuinely intrigued by some of the functionality that didn’t strike me (initially) as something I’d find on LinkedIn. To wit: a year ago, when I would wake in the morning and want to read the “news” — and by “news” let’s be honest, I mean “news Bobbie is interested in and therefore skewed toward 2 or 3 specific topics” — I would read my twitter feed (follow reporters AND the companies they work for), then I’d check mobile CNN, After looking at my Facebook feed, (oh, work email too), and maybe Twitter again, I’d check LinkedIn.

(Why all the checking? Not all apps update your alerts to the icon on your mobile phone screen. Sometimes you get the little red bubble of awesomeness, and sometimes you don’t.)

Today, the pattern is more likely Economist.com (mobile), LinkedIn, Twitter, work email, Twitter, and maybe one more round to LinkedIn. Why? Many reasons, mostly dealing with personalized news retrieval and access to information about companies, jobs, etc. that I wouldn’t normally have. But there are many misconceptions about LinkedIn, and that’s what this post attempts to remedy.

Wait, Isn’t LinkedIn for if I’m looking for a job?

Not necessarily. LinkedIn offers a variety of other services that you can use, regardless of your current job circumstance. There’s personalized news feeds, updates on your “linked” connections, and for those of us who are stats-centric, tons of little data updates. I recently tried playing with their business logic: changing my title (and ONLY my title, not dates, company, or description) from “Applications Development Manager” to “Manager, Applications Development” triggered a “congratulate Bobbie on her new job” notice to those I was linked to. Awkward, true, but interesting to note the sensitivity. My personal favorite is Pulse, their personalized news service. You pick themes or people who are interesting to you, and it does the rest. Daily updates of articles, and discussions therein with other people both in and out of your network.

But I’m only linked to people I work or have worked with, right?

No, no, and no. You can link to anybody. You will want to link to people you know, regardless of if you “work” with them. You’re on the PTA? Go find your PTA Board members, link to them. You’re on the board of a NonProfit? Link them. Went to college and remember some pretty cool people? Link, link, link. Met some great people socially? Link. Link to them all. You will get recruiters you’ve never worked with asking to link to you — proceed with caution. Do you do a lot of hiring? Then link to them. Do you want to get poached? OK, link to them. But if you’re an individual contributor who doesn’t want to move, tell them honestly and then link anyway — after all, a friend of yours may want to use a recruiter.

Hey, some of those people don’t work, or are retired, or are in a field I’m totally not in to. Why should I link to them?

You don’t know who THEY know. I’ll take the reverse-route on this and look at it from the “what’s in it for me” aspect; most of this logic works if you think of yourself as a relatively altruistic person. That stay-at-home-mom may know a double dozen people who would love to donate to your charity, or may know someone who works as a recruiter at a company you really want to work for. That artsy friend of yours who does installations at hotels may know someone who manages them, which may fit in with your marketing and sales job. You don’t know what you don’t know — the whole point of LinkedIn is to establish routes of communication. If you’re going to use it as a tool, use it properly.

OK but I should only link to “my level” of people or higher, right? So I’m a Manager, I will only link to Managers and above.

First off, this is just plain douchey, but let’s just assume you didn’t mean it that way and are looking at it pragmatically. You’re wrong, and that’s okay. We’ve all been there.

You will want to link to people, regardless of rank and title. Just like you, people will expand their horizons and grow. Some people grow faster than others, and to quote Sigourney Weaver in “Working Girl”, “Yesterday’s junior prick is tomorrow’s senior partner”. Now, NO, people junior to you (real or imagined, rank or age, etc.) are not pricks. But the tenet is legitimate: you don’t know where their career will lead and if you’re going to pick people based on their success, remember you can’t know it. So link to people you know, and that you respect, and ignore their title (high or low). I know some people who give pause in the other direction — that maybe they “shouldn’t” reach out to that VP or that CEO. Do you know them? Have you been in a meeting with them, talked to them? Do they know you or have they worked with you? Then link to them. They may have something interesting to say, their company may want to work with yours, you may want to solicit a donation, they may want to read your white paper.

No one really fills in all the portions of a profile, right? It’s not just me, right?

Of course not. I don’t have anything published (aside from this blog and another one) and so I haven’t got anything for that section. And so I don’t put anything there. I put in what I’ve got, and “curate” my profile as necessary. Sometimes that curation is to see what happens with the business logic because my business *is* logic, and data, and software, and how that rolls together. So I follow people in that vein and I play with my “persona” on LinkedIn to that end.

They offer a lot of stuff for a fee, is it worth it?

Recently I got an offer to try Job Seeker Premium for free. While I don’t think I’d use it just yet, I do know that free is better than not free, even if only for a month. If I ever do go that route rest assured I’d blog all the details, and with as much anecdotal evidence as I can provide.

But for right now, I’m content to get my news.

Beyoncé and Lean In

I was listening to NPR the other day (this seems to be the thirty/forty-something ubiquitous intro to a story) about Beyoncé’s new album, and how Twitter trended when it dropped, and there as an awful lot about how She Is A Feminist and This Album Is A Tribute To Feminism. Naturally, it being NPR, the second person they interviewed pooh-pooh’d this, pointing out that in her videos apparently Beyoncé is gyrating in such a way that she is gyrating for men, and therefore it isn’t any different than any other oppressed-female gyrations. This is all very normal and to be expected anytime someone declares something “feminist” or “the new feminist”, women will gather on either side and debate earnestly. None of this really irked me until this lady (Tanya Steele, which is a fantastically appropriate name) pointed out that when women were telling her about how they feel Beyoncé’s gyrations/music/etc. made them feel empowered, and/or they felt it was a good example of feministic power, she had to “walk them back” and “explain it to them”.

It took a while for me to sort through why this irritated me. I don’t normally engage in discussions on feminism or women’s issues, it wasn’t part of my educational background and it just really doesn’t come up. I’m more likely to get into an economics debate. (NB: I have not taken a single women’s studies class. I do however own a vagina, and have friends who own vaginas, so I think I’m somewhat qualified to discuss the condition of having a vagina and the thinking that may or may not go along with vagina ownership.)

Merriam-Webster defines Feminism as: “The belief that men and women should have equal opportunities”. (It also defines it as an “organized activity on behalf of women’s rights and interests”).

Beyoncé and Steele

As best as I can tell, Ms. Steele’s contention is that when women view Beyoncé’s new album, and more specifically her videos in which she “gyrates” (I have not seen them nor is it really necessary to do so to illustrate this particular point), as “feminist”, they are incorrect. Her reasoning is Beyoncé is gyrating sexually, as to appeal to and/or entice men, and therefore is acting like someone who has to sublimate their own needs/desires in order to attract someone else, and therefore that isn’t beneficial in any particular way to her gender representation.

This reasoning is highly subjective. First, it assumes a knowledge of what is in Beyoncé’s head as she’s gyrating on the screen. I am willing to wager as she was gyrating, under a myriad of hot lights, multiple takes, makeup touches, reminders on choreography, adjustments to the mic, etc. that what was in her head was,  “I am working, I am working, I am working, I can’t wait for a hot bath and a glass of wine, but I am working.” Beyoncé’s reputation in the industry, even for one who doesn’t follow it altogether much, is one of extreme professionalism and hard work. Her personal wealth is such that she never, ever has to work again, independent of that of her husband. Beyoncé works if she wants to work, she busts her butt because she wants to, and she gyrates because she wants to.  Second, it assumes that Beyoncé’s gyrations were intended for the sole or at least primary benefit of a male and/or lesbian observer (and/or customer. Remember kids, she’s selling a brand.) The assumption is she is gyrating sexually, she is therefore objectifying herself sexually for a sexually interested party. Demographics aren’t readily available for her album but I’d be willing to put the $20 down to say it trends female more than male. And they are not all lesbians. Third, Beyoncé has gone on record, on multiple occasions, for “loving being a woman” and “enjoying her curves” and “dressing sexily”.  It would be a little disingenuous then to expect her to stand in a full-length evening gown when singing songs about seducing her lover.

The fact of the matter is, some women like to exhibit and some do not. Because Ms. Steele does not see value in exhibition she would like others to not see value in it as well. This is human nature, but it is unreasonable to then have to explain to someone why something they like, that you don’t, that doesn’t cause you any personal harm, is “wrong”. If a male person sees Beyoncé gyrating and from that infers all women should gyrate, then it is NOT Beyonce’s gyrations that are to blame. It is his rationale that “female person gyrating on TV = all women gyrate for me” that is wrong. To assume that Beyoncé’s gyrations set feminism back in any way is tantamount to saying that “because a woman dresses XYZ way she is asking for it”. You can’t have it both ways: either the observer is responsible for their own behaviors or they are not.  I prefer to think that men, and women, are rational human beings capable of using their brains and if they are NOT, it is not the fault of society or other folks. Your brain, and your actions, are your own to manage.

Lean In

The larger discussion, though, is how women are perceived in society and, in terms of Lean In, how we perceive ourselves (vs. how we “should” perceive ourselves, as best as I can decipher it).  While the “Beyoncé is/isn’t a Feminist” debate is exciting mostly because it can be and mostly because of the method in which she chose to drop her album, the “Lean In” concept is trickier and, I think, longer lasting. The basic takeaway I had from reading Lean In is that women don’t get opportunities as much as men do because either a. we would if we spoke up but we don’t speak up, or b. we need to speak up more so men get used to it and therefore will “see” us in the roles we want.

Here I think I need to step aside and explain something in my own, personal world that means my subjective take on this is going to be just that — very subjective. I am 5’10” tall. I have never been of slight build. Physically, I do not appear meek or weak or shy. Further, I am the daughter of two strong-minded, outspoken women, and two male engineers. I don’t think I’ve ever had a problem asking for something if I wanted it, and/or providing a rationale on why I should have it. (True story: when I first moved to San Diego 15 years ago, I worked for a company that believed you should get personality tested before you got a position within the company, so everyone knew how to work with you. The sociologist who reviewed my results said that I was a bit like an elephant: when I entered a room everyone would know it, and if my foot fell it would be a resounding stomp, whether or not I intended it to.) A casual reading of my employment reviews would validate this: the best term I think that has ever been applied to my attitude is that I was “highly apolitical”. Time has allowed me to learn how to say “No”, for example, in sixteen different and appropriate ways, but the long and the short of it is if I want something I will ask for it, and if I am told No and I don’t understand why I will press.

Which I guess makes me rather “mannish” in the workforce.

So when Sheryl Sandberg talks about not even thinking about asking for something until it became a really big issue (e.g., preferential parking for expectant mothers) I must confess I don’t understand. When one of the most intelligent, driven women I know in my social circle tells me that until she read this book she would have thought twice, or not at all, pursued a particular project because she wouldn’t have felt comfortable doing so, I am aghast. This book wasn’t particularly instructive to me. It was however, revelatory.

Leaning In Objectively

There is an old joke that PMS is “when women act like men do all the time”. I don’t really think this is accurate and in any event because of better things and better living through chemistry it doesn’t apply to me. However I do think that women can be raised, or conditioned, to not ask for things they want.  It is kind of bittersweet that a Pantene commercial illustrates the deltas in how some women perceive themselves (as well as how they perceive society perceives them, etc.)  It’s entirely possible I am perceived as a bitch, that I’m bossy, or that I’m self-promoting. The question becomes though: what is the end result of my efforts? If I get the promotion, or the project, or the job, or the budget, have I failed still because I ruffled a feather or two? If the tenet is that “men do it all the time” do feathers get equally ruffled? We are told that men “ball-bust” each other and the sting doesn’t last; why must I assume it does if I engage in it as well (abiding thoroughly by the rule that if you dish it, you need to take it).

Bottom line: if I earn what I was after, does it matter if I’m “liked” as much as if I had stayed put? And does it matter, to me, to be liked by someone who would  rather I had stayed put? Like blaming Beyoncé for the perceptions that men may have of other women because of her gyrations, I don’t know that you can blame the woman who gets the project, or the raise, or the bonus, and possibly irks someone, because she asked for and earned it. If there’s anyone who needs to own that, it’s the one who is irked.

In Development

I was at a holiday gathering the other day and during the usual course of “…And what do you do?” I replied that I was a developer. The inference was that I was a Real Estate Developer; I had to explain that I was a Make the Computer Do Useful Things Developer. I was talking to two ladies about my age (Hi, I’m 40), and was surprised at the reply: “Oh, that’s unusual!”

I suppose I should not have been. I know a lot of women in IT, but darned few who do development.  To be clear: most of the women I know in the Information Technology space were at one point developers, or have a passing knowledge of some development language. They merged into Project or Product Management, or Business Analyst roles. These roles require knowing what is possible of code without actually having to write any of it, and so if you get tired of the incessant progress of development technology then that is one way up and out (and it is a way I took, about five years ago).

Careers arc and opportunities knock and itches flare up and I am once again a developer.  And I find myself, when talking to people who don’t work with or know other developers, battling not only the usual misconceptions about development, but the gender-based ones as well.

Development (in IT terms) is the handle one applies to the concept of using a series of commands (code) to tell the box (tower, laptop, server, etc.) what you want it to do; if you want it to take in something or not, if you want it to spit out something or not. In order to create this blog post many people did varying forms of development (from creating the templates that instruct the browser how to make this post look all shiny, to the protocols that tell the server where to put this post, to the widgets on the front end that tell you things like I haven’t posted in a while). If I typed it in MS Word, that required a bunch of other development by a bunch of other people.

Development is not:

  1. Something you can do on five screens drinking 3 bottles of wine to create a “worm” that appears as a graphic on your screen (as in Swordfish), and usually doesn’t involve a developer logging an Easter Egg of themselves in a bad Elvis costume with sound effects (as in Jurassic Park)*. If I drank 3 bottles of wine and was looking at 5 screens they’d probably be the ones you see in a hospital room, and the only graphics I would see appearing would be the “worm” that is my heart rate monitor flat-line.  And while I have myself buried Easter Eggs and commentary in code, it isn’t that elaborate because you don’t typically have time to build elaborate things. You’re busy rewriting all of the stuff you just wrote because someone decided to change the scope of your work.
  2. Anything involving a graphic user interface (GUI). When a developer talks about manipulating objects, they are things that are typed out phrases, they are not boxes that are dragged and dropped. There are some development environments that offer up a GUI in tandem with the “scripting” – that bit about writing out words I was talking about – but they are there to illustrate what you have scripted more often than not, and not there to assist in your scripting.
  3. Finite. Development technology is constantly changing and no one developer knows all of the development methods or languages. That would be like someone knowing all of the spoken languages in the world. Rather, it’s typical you’ll find one developer who “speaks” one development language really well, or maybe a branch of languages (much like you run into a person who can speak Spanish and French and Italian, because they are rooted in the same “base” of Latin, it’s not uncommon to find someone who can code in ASP.Net and VB.Net and C#.Net, because they’re all of the Microsoftian .Net base).  No one hires “a developer”, they hire a .Net Developer or a Java Developer or a Ruby Developer or what have you. Specialization exists because the base is so broad.

Modern cinema has done an injustice to developers in terms of making what we do seem both simple and sexy; the “shiny” environments typified by the interfaces “hackers” use on-screen looks really slick and probably took some real developer hours of time to make look good… with absolutely no real purpose. That said, actual development can be simple (with clear requirements and a decent knowledge of the things you can and can’t do) and can be quite sexy (if you’re sapiosexual). It’s just not well-translated in current media. (To wit: Jeff Goldblum uploaded a Virus to an alien system on a Macbook. He didn’t have to know the alien system’s base language, machinery, indexes, program constraints, functions, etc. And it was on a Mac, in the 90’s, for which development was not one of its strengths).

Most of what development is, is trying to solve a problem (or two), and generating endless logic loops and frustrations along the way. You build a “thing”, you think it works, you go to compile it or make it run, it fails, you go dig through what you wrote, find you’re missing a “;” or a “,” or an “END” or a “GO” or a “}”, re-run, find it fails, and go dig through some more. For every hour you spend writing out what you want it to do, you spend about an hour figuring out why it won’t do it.  This process of “expected failure” is not sexy or shiny or ideal, and that’s why it doesn’t show up on-screen.

These are misconceptions every developer, regardless of gender, has had to deal with at some point. Some deign to explain, some gloss over, some simply ignore; much like I really hope we get a socially-functioning, intelligent person on-screen soon, so do I hope that we get a showcase for the simple elegance of real development.

It would be great, too, if there were more female developers on “display” as well (and not for their bodies, hence the scare quotes).  Think through every movie you’ve ever seen that shows people doing any real development, “hacking” even (a term that is abused beyond recognition); how many were female? Go back to the movie “Hackers”—did Angelina Jolie actually, ever, really type anything? You inferred that she did, but the real development, the real “hacking”, was done by the crew-of-guys. Oh, and that’s right, she was the only girl.  The Matrix? Carrie Ann Moss spent precious little time in front of a computer there. She did look damn good in skin-tight leather.

Fast-forward a decade (or two) and we’re pretty much in the same boat. You see women behind computers on-screen, but they are typing in word processing programs or moving the mouse to click it on the shiny picture of the Murderer/Prospective Boyfriend (or, you know, both). They aren’t buried under a desk trying to trace a network cable or eyeballing multicolored text trying to figure out *WHY* it won’t compile, they’re delivering the shiny printout to the Chief/Doctor/Editor from which Decisions Will Be Made.

We find it surprising in social circles, I suppose, for women to be in development, because we don’t see it exemplified or displayed in any of our mediums.  TV, Movies, even proto-development toys for children often feature eager-looking boys interacting with them, the girls are reserved for the beading kits and temporary tattoo sets (actually, there’s precious little out there for getting your child, regardless of gender, to learn code, but that is changing). We have crime-solving anthropologists, we have NCIS ass-kickers, we have cops and coroners;  maybe it’s time we had a developer.

*Jurassic Park is a good example of both great and poor development display. Right before tripping that “Dennis Nedry Elvis Graphic”, Samuel L. Jackson’s character is eyeballing Nedry’s code. That stuff that looks like sentences that don’t make sense? That’s code. That’s what it looks like, for the most part. Unfortunately, later on when the little girl is hacking the “Unix System” that “she knows”, it’s all graphical. And that’s not accurate.

Temporal Relativity

Otherwise entitled: I Keep Forgetting What Day it Is.

Driving home through unusually light traffic tonight I realized, halfway home, that tomorrow is Thanksgiving.  For someone who works for a retail company centered around food, this is not how it should be. I should have, beating in my heart and tattooed on the inside of my eyeballs, every food-based holiday and a countdown to it. Instead I was one of the many last-minute shoppers at my local grocery store, which amazingly had all of the ingredients to make two pies, homemade cranberry sauce, and a gorgonzola-broccoli recipe I stole from my friend Cynful about five years ago.

My parents have the “Now What Day Is It Again?” syndrome but for drastically different reasons: the parents are retired. “Weekends” have no meaning if you  don’t work during the “week”. My day-of-week forgetfulness comes from “I am going to survive this day” combined with a bit of work each weekend.

My kitchen was demolished on 30 September. The job to remodel it was to be completed 6 November, with a schedule that had a ton of spare space in it. As of today, my fridge is still in my garage, all of my kitchen gear is in boxes, I can’t park in my garage because of said fridge and other kitchen-cabinet boxes, and we are looking at “another week or so” of work. Most people can forgive any amount of stress or craziness at work to go to the solace that is their home, I do not have that solace. I go home to disorder and disruption, which for me is unnerving and quite possibly a form of slow torture. The best way to make a control freak cringe is to take absolutely everything away from their control and tell them there’s no way to get it back.

I will take the frenetic panic of working through the massive consumer glut that is the holiday season, and yes I too have a couple of wish lists out there; I will take the increasing tempo of schoolwork for the boychild, I will take the slow creep of the scale that necessitates increased workouts, I will take the eternal guilt I get at this season for not being able to do more, to provide more, to be more.

It’s just another week until I get my kitchen back.

Cliché

Clichés, as a rule, bother me. This has to do with my innate dislike for anything that must “be accepted”. The absolute BEST way to get me to not read a book, not see a movie, not do something, is to tell me I MUST read XYZ book, I MUST see XYZ movie, I MUST do whatever. It just won’t happen. If I’m in “polite” mode I will dither, if you are family I *may* humor you, but otherwise it’s just not going to happen. This explains why I still haven’t seen the “Breakfast Club”, why it took some serious cajoling to read Lean In (yes, yes, blog post coming about it eventually), and why, at 40, I don’t know if I own a hairdryer because I simply refuse to use one.

Clichés are the verbal “you must”. It suggests that there is something out there you must do, or must allow, because it just *is*. The absolute worst one, in my opinion, is “Everything Happens For A Reason”.

Please. Just… don’t.

Things happen because they happen. There is little reason in someone going in to a school and shooting children, there is little reason in the antics of Congress (these days), there is little reason in Wall Street (as evidenced by a DOW nearing 16k whilst we have the hurdles we have. There need not be, and frequently there is not, a reason.

Saying “Everything happens for a reason” is a way of accepting a lack of control; it means “I can’t see a good reason for this to happen in a logical world so I will abuse this platitude and hope this changes the subject and/or gets the person who is trembling with doubt, pain, or hurt to stop it long enough for me to be comfortable”. Looking for “reason” where no good one is, is insanity. Or optimism.

I’m more of a fan of “It is what it is.” “Que sera, sera”, however sung by Doris Day, is accurate. Things happen: this much is true. Entropy increases. Time marches. But the notion that there is some underlying reason causing a typhoon to kill off five thousand people, or a tsunami and earthquake to hit the site of a nuclear reactor, is asinine.

OK: Point and counterpoint. Correlation and causality. That is to say, YES, ultimately there is a cause to every effect.  A ginormous typhoon hit the Philippines because global warming has warmed the atmosphere and waterways in that area to a devastating effect and the bomb that would go off there went off with a bigger bang; people tend to build nuclear reactors near waterways in order to easily flood the site to cool it down. But when people say “Things happen for a reason” they do NOT mean, “things happen because a series of events led to them”, they mean, “there is some good reason for this to have happened” and “good reason” usually infers somehow, somewhere, there is benefit.

You will notice that very rarely does anyone say “Things happen for a reason” where something happens that is obviously beneficial. “Things happen for a reason” is not applied to the lottery win, or the quick reflexes that get you OUT of a car accident, or the “A” you got on your Chemistry final. No, then you take the credit: you studied, you had quick reflexes, YOU picked the lucky number. So if it’s good, you controlled it with your abilities and your skills; if it’s bad there must be some better reason for you to have fallen on misfortune.

I have been in plenty of good circumstance that was of my own doing, and nearly as much malfeasance that was as well. I do not attribute this to “fortune”, I attribute this to the way things are. It is what it is.

But it may not have happened for a “reason”.