Hacker News new | past | comments | ask | show | jobs | submit login

Background: I'm friends with the owners of Wildbit, and have watched the journey they took that led to shutting down Newsberry. Several times, over a couple bottles of wine, my husband and I advised them to "just shut it down"! Because my husband & I run a very similar business, and we understand what it's like.

Here's the thing about the comments on this article, here on HN: of the people saying it was a mistake, that the article was misleading, etc, etc: How many of them have a profitable business with a team of any size, and multiple products?

That's the hidden problem with HN: with a few notable exceptions, everybody here is an Monday morning quarterback.

There is NOTHING more draining than to keep a product running "because it's just profitable enough." Or worse, because you feel guilty about shutting it down, because you feel like you're going to let down your customers.

There's nothing more divisive than a redheaded stepchild product.

There's nothing more wasteful than a distraction to you & your team.

Running 2 products is not simply double the work than running 1. Running 3 products is not simply 50% more than running 2.

When one runs a successful business oneself, one knows this implicitly.

But when you haven't, then you are likely to look at this kind of story and go "WTF? They just threw away $75k/year? But they could have spent 1 day a week on fixing it and making it more profitable! They could have hired a part-time designer!"

But this is just a lament wrapped up in logical, impartial language - but still a lament, which is really saying "WTF? I could use $75k/year! How could they possibly throw that away? WASTEFUL. SHAMEFUL."

Which is, really, totally understandable. Until you run a business of this scale, it's hard to imagine how $75k/yr in profit could be a millstone around your neck instead of something to celebrate. However, that does not good business advice make, and one must always consider the source & experience of the person dispensing it.




A lot of good points here.

Perhaps I should grow a thicker skin, but as a father of two redhead children I found the use of the expression "redhead stepchild" offensive. Mostly because I'd hate them to read something like that and think that there is something wrong with them.

I know it's meant to be a funny expression, and it's cool to make fun of redheads and all (isn't it great to find a minority that is ok to publicly ridicule without having to think about issues like racism), but perhaps the joke is getting not funny anymore...

or maybe I need to have a coffee and lighten up?


You need to have a coffee and lighten up. Nobody is making fun of redheads.

1. Lots of people think redheads are sexy.

2. The implication of "redheaded stepchild" is that "it's obviously not your kid" or possibly even a bastard.

3. I'm fat, and a Rails developer, and I don't get my knickers in a twist every time somebody makes the "fat models" metaphor about good MVC design.

No offense, but your sensitivity to your kids' redheadedness is far more likely to make them think it's a bad thing than some random colloquial phrase.


No offense taken. I'm actually not sensitive about their red hair, I love it and the hair of their very sexy redhead mother.

I guess I must have misnderstood the colloquialism as I read it as similar humor to this http://smh.drive.com.au/governments-dont-be-a-dickhead-campa...


http://m.urbandictionary.com/#define?term=red%20headed%20ste...

You are right, the "redheaded" part of the phrase is simply meant to imply the child is obviously not a legitimate child of the parent (who is assumed to be a non-redhead). So I was way off base, my apologies.

That's what you get for posting immediately after learning your flight has been delayed two hours :-(


S'ok.

The point of "redheaded stepchild" is that nobody loves it cuz it's not THEIR baby. Making it the perfect metaphor for this product. :)


That was much more explicitly my lament: Why wouldn't you sell it instead? For example, that's what Brent Simmons did with MarsEdit, and it turned out to be a pretty successful foundation for Red Sweater Software.

But you're right that I don't run a business with >$100k in profits, so I suppose I very well might just not get it.


They addressed that specific question in the essay. Did you miss it, maybe?


"That's the hidden problem with HN: with a few notable exceptions, everybody here is an Monday morning quarterback."

If you're unwilling to receive feedback (be it right or wrong), why write the article in the first place?


First: Who said they are unwilling to receive feedback? Nobody here from Wildbit is going "ohnoes how dare you question us wahhh."

Wildbit already made the decision. It's already happening. They've been working on it for months and months. I don't think they care what random people on the internet have to say, either good or ill.

Why write, then? To draw back the curtain a little on their business, and no doubt also for some exposure. Which has totally worked for them.

I am writing for the benefit of the other people reading, who would only otherwise see the "zomg waste!" responses and not understand where those reactions are coming from… e.g. a place verrry different from the place where the people live who made the decision. Unlike the vast majority of the commenters, my husband and I run a product business very much like Wildbit's, just a little bit younger. And we know them. So I want to challenge more HNers to think beyond the obvious, safe opinion ("they shouldn't have shut it down! money!") and understand what it's really like, what they're missing from their imagined scenario.

And with that said, I'd like to invite you to consider the meaning of "feedback." Is anyone ever excited to get "feedback"? Do people do things, and write, in order to "get feedback"? That is a rather sad, limited view of human endeavor.

HN is a kind of echo chamber, with most people expressing the same (tired, accepted, safe) opinions & receiving plaudits and upvotes in return. That sounds more like the second definition of "feedback" to me -- the return of a fraction of the output signal.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: