Lying for a living…

When I was interviewing for the Community Manager job with Palm’s Developer Relations, I found myself sitting in a conference room with the person who would ultimately be my boss, and we were talking over various aspects of the job and the usual interview questions and chatter.

And then she got a smile on her face and the question came out of left field: What would you do if I asked you to lie to the developers?

It’s actually an easy answer. I said I’d lie. 

Because I would. And did. Because for all I tried to be the internal advocate for my developers and promote their needs and comments around the company, I was also the representative of the company out into the real world, and my primary role was presenting and protecting the company interests. (any developer I worked with who never realized this at the time, I’m sorry to break it to you now, but really, it shouldn’t be a surprise….)

And then we went into a 45 minute discussion about the implications of lying, and all of the complicated issues surrounding it, such as damage control when we got caught (no IF we got caught. ultimately, you will), and how part of my role was helping advise the company to try to make sure we never got to the point of having to lie (a good idea in theory, but people need to listen to your advice for you to influence decisions). 

And to me, that’s at least the theoretical purpose of the Developer Advocate role, no matter what job description it’s tied to. It’s the person who not only interacts with the developers, but synthesizes down what the developers are saying and spreads that condensed version of the developer into the different part of the organization so that people planning products and making decisions that impact the developer can understand what they’re saying and what they need to be successful. (this, of course, assumes that people within the organization actually want to hear what the developers are saying. To the degree you have people deciding what developers should have, vs figuring out how to give developers what they’re asking for and saying they need, you have a conflict. Which in my experience is handled by finding out about meetings where decisions are made well after they actually happen….)

These are the kinds of questions that ought to be asked when trying to hire this kind of role, or in trying to figure out if you want to be hired. It’s all well and good to get all touchy and feely about taking care of developers and working with them to be successful (and yes, we did all that, too), but where it gets real is when it hits the fan, and then everyone on all sides need to know how people are going to react because that’s the time when you least can afford surprises. 

(the honest fact is, I think my parrot could be a develop advocate for a platform when things are going well. What defines a good one vs. a weak one is how things go down when things aren’t going so well. I just wish my time with webOS had had fewer of those times, and more of the “yeah, this is easy!” times…)

What defines these roles is how the people in them handle crisis and challenge. And the ones that handle crisis well tend to be the ones that know that crisis is inevitable and do as much planning and work ahead of time so that when it hits, there are already options in place to handle whatever comes at them. And hopefully, is watching both the inside and outside of a company closely enough to know the crisis is coming, even if they can’t prevent it…

Posted in Community Management, Social Media

Things You’ll Find Interesting October 2, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Thinking about Blog Content – and asking what you want more (and less) of.

One of the things I’ve been doing the last couple of weeks has been trying to figure out exactly what I want this blog to be about, and what has value in the greater scheme of things.

The thing is, defining “value” for a blog is still a really squishy concept. The easy answer is pageviews, but unless you’re one of those sites that’s designed to maximize them because it drives your advertising revenue, what do pageviews really mean? And buy you? 

Want to goose pageviews? It’s surprisingly easy to write some link bait that gets pointed at by sites that can drive pageviews and give you that nice, ego-satisfying spike on your Google Analytics.

 Google ChromeScreenSnapz001 (look, maw! I went viral!)

Of course, three days later, they’re gone, and they don’t come back. Maybe they even left you a few choice presents in your comments — did you check? 

I’ve come to believe that pageviews is a poor way to judge the value of a blog post, but how I wanted to value them wasn’t really obvious to me.  What is the value of a blog post?

Well, now that I’ve trashed pageviews, I need to talk about them a bit.  Over the last year, readership of this blog has been growing, slowly but consistently — and for that, I say thank you! Pageviews are up about 130% since January, and up a massive 275% compared to this time last year. Visits are up 350%, unique visitors are up over 500% — which implies that pages per visits has dropped, which it has, down from about 1.5 pages to 1.25 pages per visit. 

But overall, the site is now seeing around 10,000-12,000 pageviews a month. A few pages have been blessed by the google beast for a few fun and interesting search phrases, and that’s helped drive consistent traffic for the last six or seven months.

That’s why the Amazon affiliate and Borrowlenses ads showed up about three months ago, because I wanted to experiment to see if the combination of those ads and that traffic might generate a little revenue, and if so, whether it would be worth tossing that page real estate at them for the return. the short answer is yes; with two months of data, the blog is now paying for itself, plus maybe a couple of cups of coffee. The number of complaints I got for adding ads to the site were, well, zero.

So all in all, the experiment is a success. I have zero interest in turning the web site into something that looks like a low-end neon brothel, so don’t expect to see pages festooned with a dozen ads for things like mortgage refinances and weight loss miracles. Not interested in prostituting my content for the sake of a few pennies. I won’t offend your eyeballs like that. 

An interesting shift over the last year is that 70% of my pageviews are now photography related, with an emphasis towards the geekier side of things — tools and workflow. That doesn’t surprise me, and I think that’s an area where I do bring some real value to a conversation, so it’s safe to assume that’ll continue. Having said that, I have no intention of turning this into a photo-only blog. It’s still going to be “stuff I’m interested in”, of which photography’s only one aspect. 

But even that’s not really correct. I’ve been thinking long and hard about not just posting to the blog, but adding value to the universal conversation we have here online. It’s easy to open a vein and type something out and post it, but those kind of articles are quickly forgotten. I’m more interested in posting less frequently, but posting a higher quality and more interesting set of messages. 

How to judge that? I’ve decided on two metrics:

  • Engagement: do people react to the piece? Is it shared? tweeted? Do you leave comments? Do you write blog posts condemning me for it? Do you send me email? All of those are active measures of whether the content matters. So are some less obvious things like how long you spent reading the material and whether that page encouraged you to look at other pages on my site. I’ve decided, for instance, to look more at page views combined with time spent on a page to create a basic value metric: 1,000 pageviews of a page that people spend 3 minutes on is higher engagement value than 10,000 pageviews where people stick for 30 seconds. 
  • Revenue: In some cases, it’s easy to track back an Amazon affiliate order to a specific page or entry point. In other cases, not so — but I have some ideas on how to do some behind the scenes tweaks that will at least let me get this data to the category, if not a specific page. Right now, it’s pretty easy; almost all of the Amazon affiliate purchases have been photography related, so it’s fairly safe to tie it back to the photography writing. About half of the orders I can tie directly to a link on a couple of specific pages, too. 

One of the questions I’ve been asking myself is whether I really want to wade back into the mosh pit of writing about technology stuff, and secondarily, Mama Apple. I find a lot of the writing in this space pretty piss-poor, to be blunt about it, but I also wonder if I really add much to the overall conversation (or even if I want to). In a few specific areas I think I do, but honestly, I struggle to convince myself I really want to, given how many babbling mouths are already fighting to be heard talking about those topics. 

So I conducted a couple of experiments. They got some initial link coverage, and ended up with nice sets of pageviews, but by my metrics they didn’t do well. Engagement was poor — few folks spread the link love around. Few explored my site. Almost none sent feedback of any kind. Nobody clicked an affiliate link and dropped some pennies in the tip jar. And after the peak of the moment, as far as I can tell, none of them subscribed to the site and hung around to see more, because my numbers dropped back to where they were before the spike.

So to me, the value of contributing that kind of content is effectively zero. It helps feed the huge herd of news-omnivores that wander the net in search of something to look at and then move on as if it never existed for the next content to chew on. Other than the herd leaving the occasional turd in the comment section, they don’t return anything useful as an encouragement to grow more stuff for them to feed on.

So I don’t see any reason to keep trying to find reasons to write for that audience right now. Doesn’t mean I won’t occasionally, but it just reinforces my instinct that things are moving in the direction I want it to move. (all those discussions about “slow and steady” as a way to good SEO and search engine placement? It turns out they’re true, and it works, if you keep at it. It took me a couple of years to shift my readership to be photography-centric AND to return to the page view volumes I had when I left Apple. Of course, few folks have the patience to do things the slow and steady way, which is why so many people get taken by the black-hat SEO scammers…)

It’s important to remember that if you want more of some kind of content, or if you have a writer you want to do more of something, you have to actually let them know you want it. Passively sitting back and reading stuff and then moving on — that gives authors no hints on what they ought to be doing more of. I think that’s one reason why so much of what’s published online is so forgettable and interchangeable (that, and there are too many freaking sites all cribbing from each other on the same few and trivial stories trying to pump up pageviews to pay the bills…).

So here’s the call to action: give feedback. I’m not speaking specifically about me, but about writers in general. There’s a reason why I do the Things You’ll Find Interesting blog posts (which are, by the way, the second most popular postings on the site overall after the photo geeking). And why I litter interesting links on Twitter and Google+ (when I have the time; it’s still the site that loses when I get too busy, but hope springs eternal). Links are one way to let someone know you found it interesting; it also helps show Google something was interesting, which helps it get better placement in the great search engine database. And you can do those things without necessarily spending the time it takes to write comments, or drop a buck in a tip jar, or things like that. But those things matter, too, and frankly, a well-thought comment or email means as much as a few dozen links, because of the time I know went into writing it.

If you want better content online, you need to invest a bit of energy — but it’s easy. simple make sure that the people writing the good stuff know about it. It’s as simple as a link on twitter. Or commit to once or twice a month hitting someone’s tip-jar or one of their affiliate links. Amazon affiliate costs you nothing, and Amazon throws a few dollars at someone for you. It may sound trivial, but it’s noticed — and even something simple like having a blog that pays for its hosting costs makes it a lot easier to put time into writing content for the blog. Even if you only throw a half dozen links a week onto twitter or G+ or Facebook, it’ll make a difference in helping encourage better writing on the net. 

Or just sit back and browse on whatever gets tossed at you and do nothing. And you’ll get more of that. To me, that’s like living on fast food. It keeps you fed, but wouldn’t you really like something better to chew on? 

If so, you need to start helping the chefs know what that is. By telling them… 

 

 

Posted in Working on Web Sites

Things You’ll Find Interesting October 1, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

App.net Developer Incentive Program

App.net Developer Incentive Program – Marco.org:

An interesting idea: App.net will be paying “at least $20,000 per month” cumulatively to app developers, divided according to each app’s popularity and user satisfaction ratings. So a reasonably popular app might get a few thousand bucks a month.

It’s a strange move, though. It doesn’t look confident. This reminds me a bit of RIM’s strange $10,000-guarantee-if-you-make-at-least-$1,000 deal. (Apple and Google never needed to pay developers to make apps for iOS or Android.)

You’re trying to solve a chicken and egg problem here. 

Consumers are less likely to buy into a platform if “the apps they want” (see note 1) aren’t available for it. 

Developers are hesitant to commit to developing for a platform where the revenue opportunities aren’t there. 

The challenge is to bridge that gap for developers. You can

  1. ignore it and pray
  2. give them non-financial incentives, such as marketing and promotion, high profile in product launches, and other partnership goodies
  3. pay developers to put apps on your platform (effectively, going to, say, Starbucks and offering to fund the app development for them)
  4. subsidize the app ecosystem to get it off the ground and give developers a revenue stream until it grows enough to be sustainable on its own

For the first two, your platform needs to be pretty persuasive today if you want to go up against IOS and Android and expect developers to just wander in and play in your territory. When we were booting up webOS, it was (relatively) easy to do the “not Apple”, because Android hadn’t yet booted either, and all of the other platforms were missing or tightly managed. Today, booting a platform like webOS would be a lot harder, IMHO. 

So you need to inject money into the app ecosystem to help developers survive as it boots. Typically the worst thing you can do is pay developers to build apps; they’ll take the money, see how little of it they can spend to get an app out the door, and you get a crappy app and they don’t care because they’ve been paid. They invested in shipping the app, not investing in the ecosystem, and in lots of cases, will never care if it sells a copy. 

So it’s all about finding ways to build revenue into the ecosystem in ways that give incentive to both publish apps and to have those apps quality ones and well received by the users. with webOS, we did a series of promotions (please, god, don’t call them contests (see note 2)). With webOS, we tried to structure things to reward success with end users — most downloaded apps, for instance. With the Touchpad, we injected money into the ecosystem by attaching a $50 credit to every TouchPad sold, allowing buyers of the tablet to choose how to spend it. Both of them

FWIW, I’m not sure $20K a month will do a lot to boot the ecosystem. That doesn’t spread very far when you’re talking about trying to help developers pay back development expenses. For webOS, our budgets were more like a million a quarter, just for comparison. 

So both RIM and app.net are on the right track, if these are implemented properly. RIM’s guarantee makes sense because they’re trying to attract the class of developer/company that already has an IOS and an Android app and is saying “what’s in it for me? why should I bother?” — at least now, there’s some financial incentive, where, honestly, marketing/promotion or “hey, we’re not going to suck in year, you want to be part of this!” aren’t going to generate much enthusiasm. You put the $1000 floor on earnings to avoid getting flooded by five thousand tip calculator apps that exist only because people want  a chunk of the money you’re giving away. It saves you from paying out money to the, um, lower-caliber developers that are simply trying to grab your payout and not really trying to build a usable app that’ll help your platform. 

IOS doesn’t have to do this because they are the 800 pound gorilla, and have a zillion units in the hands of consumers looking for apps to buy. Ditto Android. What RIM is trying to do is get into that game again. It’ll be interesting to see whether they succeed. And they can’t do it by making promises or asking people to invest in building apps in hope of future returns. The class of app they need to attract will nod politely and then go plan their IOS next generation app instead. 

App.net is in a different place; I think this is more about encouraging some of the twitter developers to give them a shot, and to create an ecosystem where the developers have a bit of help so that they can give the apps the time for the platform to find a large enough audience. The developers that app.net are likely trying to attract are a lot different than the ones RIM need to grab (app.net is going to be the individual/homebrewer and the tiny shop, RIM needs corporate and mid-sized shops to buy in), but I still wonder if that amount will make a significant difference. We’ll see…

(note 1: “the apps they want” is actually fairly hard to define. There are likely 20-30 apps that are universal to almost everyone, from email and contacts and calendar and maps. There are a larger set of a few hundred that large chunks of potential buyers are going to want SOME of, whether it’s a Starbucks app or Netflix or their bank’s banking app or whatever. And most people have a couple of apps in the “gotta have” pile that are definitely niche apps, but the lack of them can be a killer. In my personal case, those “gotta have” niche apps are my birding and nature guides. A platform I can’t get those on I probably won’t consider, but 95 out of 100 readers of this blog post will shrug and go ‘huh?’? Everyone has those apps — and none of them are common apps in any way, shape or form, which is why you need to try to build a diverse and large app ecosystem. It’s basically the same reason why a steakhouse has a token chicken or fish dish on the menu: to prevent that one “I won’t eat beef” person from keeping the entire dinner party from coming to that restaurant…)

(note 2: the nanosecond someone utters the word ‘contest’ dozens of lawyers warp in through a wormhole and start having hissy fits. it turns out that having a contest is an incredibly complicated and regulated process and involves things like creating ways for people to enter without actually spending money or owning your product and things like that. So you end up sitting down with your lawyers and making damn sure you use language that doesn’t turn it into a contest. Even if it kinda looks and smells and quacks like one.)

Posted in Computers and Technology

Things You’ll Find Interesting September 30, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 29, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

My second blog post on the NHL lockout

Unlike many of you, I’ve been trying to mostly ignore the NHL lockout. As you may remember, way back in August I predicted they wouldn’t settle this before the start of the regular season and suggested it was likely to settle in October and we wouldn’t see hockey until the end of October. Nothing that’s been said or done since then has changed that for me one bit, and in fact, it all lines up with what I expected to happen a lot more than I wish it did. 

So I see no reason to put a lot of time or energy into worrying over the NHL negotiations or the season (or the league, for that matter) until we get a lot closer to them solving this and putting hockey back on the ice and playing some NHL games. Instead, I’ve been watching the SF Giants more, and even a few football games, and, like, having a life. 

I’ve been asked by a few people what fans can do to influence this and help encourage the NHL to settle this dispute. The answer: basically, nothing. Both sides know that when this is solved, the fans will be there, so the fans don’t have much, if any, leverage. Now, if everyone could agree to stop talking about the NHL — don’t blog about it, don’t tweet about it, don’t retweet other tweets, don’t post in hockey forums, don’t read writers talking about the NHL — if fans could generate absolute “we don’t care any more” silence about the league and the lockout, it might get some of the owners nervous and push them. Of course, it’d scare the living crap out of the people paid to write about hockey (or more correctly, paid TO BE READ writing about hockey), and so not only won’t they not go to radio silence on these issues, the silence would likely freak them out and get them even noisier. Not what I’d be looking forward to… But the best thing fans can do is sit back, relax, and let this all work itself out without wasting a lot of time or energy on it. Go enjoy something else until the owners and players work it out. There’s some damn good baseball going on this year, and at least where I live, fall is just swinging into play, and the outside world has been fun and enjoyable. Try it. You might surprise yourself. Life is too short wasting it on this, unless your livelihood depends on writing about it (and/or generating page views over it).

A big reason I saw no purpose in writing about it is because I couldn’t without putting a bunch of work into studying the financial numbers, and to be blunt, I’d rather cut off my hands with a cold chisel and force feed them to iguanas than do the kind of number crunching needed to have a decent financial discussion here on my blog. 

But fortunately (or unfortunately), someone else has done that work for me over at the nhlnumbers.com web site. I can’t decide if I want to thank them or hurt them. I’ll settle for thank. For now. If you look at the numbers they’ve generated, it helps answer some of the questions that are being asked about this lockout, such as “didn’t the owners win the last lockout? and why didn’t it solve all of their problems?” and “The NHL claims to be making lots more money? How can they still need to take it away from the players?”

If you read the three part article, they’ve done a good job of breaking down both costs/expenses and revenues for the league and why we’ve gotten to this point again. For those of you who would rather poke out your eyes than try to deal with the financial details, here’s a very quick summary:

The league is making a LOT more money than it was before the last lockout. It is also spending more money to make that money (which is expected). Most importantly, that new revenue is not evenly distributed: the richest teams have gotten a whole lot richer, the poor teams have struggled to keep up with increased expenses, and the teams in the middle are more or less where they were before — in the middle. 

At the end of part three is an interesting chart where he breaks down revenue (relative size of the dot) and profitability (color of the dot): 

 Google ChromeScreenSnapz001

  • The yellow dots (money makers) are NY Rangers, Toronto, Chicago, Montreal.
  • The green dots (money losers) are Detroit, St. Louis, Carolina, Buffalo, Phoenix, Anaheim, Washington. 

I’m going to right up front flag Detroit as a special cast, because as you can see, their revenue is high, but it’s a team that has been consciously spending at very high levels because it’s been at a peak of a serious winning cycle, and they have an owner that can afford it and is willing to fund losses to keep the team winning. With the retirement of Nick Lidstrom, that cycle is ending, and I wouldn’t be at all surprised if they cut back spending over the next couple of years and perhaps finally go into a rebuilding cycle vs. a reload cycle through free agency. 

In the blue dots, the biggest dots belong to Philadelphia and Boston, which should surprise absolutely nobody. And both of those teams have been spending more heavily recently but not to the degree detroit has. 

This more or less defines the battle lines WITHIN the ownership groups.

There are seven teams with really good revenues that are profitable (or have chosen to spend it now): NY Rangers, Toronto, Chicago, Montreal, Boston, Philadelphia, Detroit.

There are six teams that are losing money and who’s revenue streams make it a challenge for those teams to stop losing: St. Louis, Carolina, Buffalo, Phoenix, Anaheim, Washington. 

If you go back and look at the state of the league prior to the last lockout, it was generally believed that there were 11 or twelve teams that would have qualified for that “green dot” status. So it can be argued that the league really is in a much better shape than it was prior to the last lockout, so the CBA that’s just expired did help the league and a number of teams. It’s just that there are still a number of teams struggling. 

Two big factors in this was the way revenue sharing was structured in the last deal (time limited in many situations, for instance) and that the salary cap floor was tied to the salary cap limit by a pure number and not a percentage. That meant that the floor grew dollar for dollar as revenues grew, even if those revenues didn’t go to the teams at the bottom of the revenue pile. 

So what’s happened since the last CBA is fairly simple: league revenues have gone up a lot. league expenses have also gone up a lot. A number of teams that struggled before the last lockout are now doing okay, but aren’t necessarily thriving, and some teams are simply unable to dig out of the revenue hole and are still struggling.

This is because revenues are not spread evenly among the teams: the richest teams got even more rich, and the poor teams had to fight just to stay competitive. 

A second factor here: as the teams figured out how to — let’s use the word finesse — the new CBA, they were able to issue contracts or find loopholes they could use to their own advantage. The ultra-long contracts with the low cap hit is the poster child of this. 

And so that’s how we got to this point. Basically:

  • The rich teams have no incentive to keep costs down, as long as they can stay under the salary cap (in a legal way if not in reality). 
  • The poor teams are forced to pay market rates for talent, even if they can’t afford it. Those market rates are set by the rich teams.
  • The rich teams don’t care if what they do hurts the poor teams. In fact, if it makes the poor teams uncompetitive, that’s good, because that’s fewer teams fighting for the playoff spots with those rich teams. Of course, that’s not what the rich teams will say in public….

And this is why we never had a chance for the lockout to end before the season started.

Let me explain.

Stop thinking of this as “players vs. league”. It’s not. 

“the league” is 30 owners, each with their own agenda. Broadly speaking, there are three groups:

  • The seven rich teams.
  • The six poor teams (five, actually, since Phoenix is run by the league office itself).
  • The 17 teams “in the middle”, which align to each other, or to either the rich or poorer teams as it benefits them. But since they aren’t really hurting, it tends to be easier to align with the powerful group (the rich teams) than the weaker group. 

The league’s solution to the problem of those six poor teams is to take it out of the player’s share. This serves the purpose of the rich teams because they don’t actually have to give any of their profits up. In fact, they’d make even bigger profits. 

The player’s solution is revenue sharing: having a chunk of the money that currently goes to the richer teams and re-allocate it to help out the poorer teams. 

  • If you think about the NHL as “the league”, then that kind of solution makes sense; after all, it’s based on the NFL model. 
  • If you think about the NHL as “30 franchise owners”, well, if you were the franchise owner of a Subway restaurant in Times Square and making good money, how would you react to being told to give up some of that money to prop up a Subway franchise in Cody Wyoming? 

Exactly. And there’s just as much enthusiasm for that kind of revenue sharing in the offices of the Rangers or Leafs as there would be in the owner’s office of that Times Square Subway. 

So we have impasse. And that impasse won’t break until one side or the other starts hurting enough to make concessions. 

The players have to hold out long enough for the rich owners to say “okay, we’ll throw some money into the pool to end this, but you have to make it worth it with other concessions”. The key here are those “blue dot” teams, and when the lack of gate revenues are going to hurt enough for them to switch from backing the rich teams to joining the poor teams and say “let’s cut a deal” — a simplified way to look at this is that the poor team needs to swing over enough owners to take over the majority position within the ownership group. 

Or the owners hold out until the journeyman players (who have shorter careers with lower-pay contracts) start sweating out losing too much income and align together to force the union to move to get games (and paychecks) flowing again.

This entire lockout is designed to make it hurt enough that players accept the pay cut; in return, the players are trying to make it hurt enough that the different owner fractions realign and force the rich owners to agree to revenue sharing. 

In both cases, there’s zero incentive for anyone to change positions or force a deal until the revenue and paychecks aren’t happening and the lack of money hitting the bank starts to hurt. So there never was any reason to think this would get solved until real games get canceled and real tickets get refunded and real paychecks don’t show up — and then it’s a matter of which side is willing to take the pain longer before deciding to cut a deal.

And so it’s going to take a while. And the fan’s ability to influence any of this is, well, zero

And that’s why I’m going to watch baseball and football and go outside and play until they settle it. And why you should, too. They will, and then we can watch hockey. Until then, our only leverage as fans is to try to pretend we don’t care, and hope that makes them nervous. And the only way to do that is to be quiet. And now, having wasted 2000 words breaking my own recommendation to shut up, I’m going back outside into the fall sun… Join me. 

(my private agenda: this is to me a fairly clear-cut situation where revenue sharing is the “right” answer, as long as player expenses are comparable to other pro sports. And overall, hockey’s are. But I also don’t see that the rich teams will go their easily, or without a “pound of flesh” out of the players. And this is a massive oversimplification of a very complicated situation, where I’m only trying to cover the basic financial issue; the real CBA has dozens of issues, but this is the one that’s driving the lockout, and which has to be solved before there’s a hope of a new agreement. And it won’t be easy, or quick. The only saving grace: both sides are being cordial and professional, and that only helps keep the anger out of the negotiations, which should make the agreement easier — someday.)

 

Posted in Sports - Hockey

Things You’ll Find Interesting September 28, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 27, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 26, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 25, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 24, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 23, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting

Things You’ll Find Interesting September 22, 2012

Here are some items I found today that I thought you’d find interesting.

Posted in Things You'll Find Interesting