News for hackers. Stuff that matters.
Re:Cue: The 10 hour scramble to launch two days early by languagehacker on Friday June 22, 2012 @04:19PM (#4148543)
I think that this blog post is hiding the fact that a team of engineers had their evening robbed from them, at no fault of their own, for something that was ultimately kind of trivial. There are numerous reasons why it's a bad idea to make engineers burn the midnight oil to rush the finishing of a product -- the first among them being Hofstader's law. If your team actually needed an additional day of work, and you didn't already have your product in the bag, you had no good reason to be courting the press in the first place. Mistakes happen in the news cycle. This is usually why you do an unadvertised soft launch shortly before a press release's publication date. This was a lack of due diligence, and not on the part of the engineering staff.

I think that there's this misconception in the startup world that the shipping of a stable product and its actual introduction in the market are efforts that are in parallel, in real time. In actuality, it makes a lot more sense to implement a lag of roughly one week between finishing a stable product and putting it out to the public. Many shops refer to this as "staging" or "vetting a release candidate". This doesn't seem like something that the folks at Cue considered before diving head-first into a hurried hackathon.

The last thing a responsible organization should do is punish the people responsible for making a stable and useful product by making them rush the last 10% of their efforts. I don't doubt that this kind of hurried time to market will result in another all-nighter down the road. I'll bet you dollars to doughnuts that after the 20th time hearing "Y Sin Embargo", the team was fatigued, annoyed, and ready to take shortcuts. So there, we have technical debt that could have been avoided if everyone just agreed to stick to their guns with the original release date. But most likely, the best solution would have been a soft launch preceding the any publication by at least a couple of days.

Let's be honest: if the immediate traffic from a little pre-arranged press is what makes or breaks your product, you're doing it wrong. As an engineer, if I see you have to put your entire organization into crisis mode over something like this, then I'm going to start taking recruiter calls more seriously.

Re:Cue: The 10 hour scramble to launch two days early by drusenko on Friday June 22, 2012 @09:47PM (#4149783)
It's negativity through and through here, and it's impossible to get away from it. Consider the following:

- You have a team that has been working incredibly hard pursuing a dream: that they can build a product, from scratch, that is truly useful to millions and millions of people. This is not an EA requiring engineers to pull insane hours -- this is a labor of love and everyone has considerable equity.

- It's a small team and that means each person has a lot of responsibility. Don't like ever having to pull an all-nighter? Never want to work a minute past 5? That's OK, but it means you have no real responsibility, and you will be compensated accordingly. Others choose more responsibility, and they man up when the shit occasionally hits the fan.

- Have you ever coordinated a massive press push with the top print publications? Then you have no business telling them how it should be done. It's extremely difficult, it requires dates locked down months ahead of time, and with that kind of advanced commitment, planning 100% accurately is beyond difficult.

- After this ordeal, the team posts an honest story from the trenches. Go to any successful startup and you will hear many war stories like this. Nothing is ever perfectly planned, unexpected shit happens. It's frankly awesome that they shared it and gave some insight into what goes on behind the scenes that you don't normally hear about.

- What is your reaction? You shit all over them. Tell them that they're horrible people and that they did it all wrong. Exclaim that you could have done it all right and they have no idea what assholes they are.

I have no idea what drives this extreme negativity on HN, but it's gotten completely out of hand.

Re:Cue: The 10 hour scramble to launch two days early by languagehacker on Friday June 22, 2012 @10:15PM (#4149838)
One of the intended uses of this site is to exchange best practices and learn from the mistakes of other startups. I think that this blog post falls in the second category. And I don't think that there's anything wrong with me pointing it out.

I'm glad it worked out for the folks at Cue, but I think they could have avoided a lot of headaches with some better planning. I'm not suggesting some radical technique I just made up; I'm pointing out that there exist practices that would have prevented a needless scramble.

The circumstances of this story should not serve as an example to other startups, but rather a cautionary tale of what can happen to a shop without the proper release cycle and adequate project management in place. My tone may have been a little rough, sure. I probably wouldn't have even commented if the post had addressed what went wrong and what they learned from it.

I guess heroic last-minute efforts amount to a more entertaining story than adequate planning, but I think we can all agree on which method is a more reliable way to run a successful software shop.

Re:Cue: The 10 hour scramble to launch two days early by pg on Friday June 22, 2012 @10:50PM (#4149883)
I have no idea what drives this extreme negativity on HN, but it's gotten completely out of hand.

Occam's razor says it's just the standard symptom of decline-- i.e. the same thing that afflicts Youtube comments, just on a much smaller scale.

Re:Cue: The 10 hour scramble to launch two days early by Dave5314 on Friday June 22, 2012 @11:04PM (#4149902)
Most of the problem seems to stem from a couple of bad apples. I suggest removing them before they spoil the bushel.
Re:Cue: The 10 hour scramble to launch two days early by jaggederest on Friday June 22, 2012 @10:29PM (#4149858)
> It's a small team and that means each person has a lot of responsibility. Don't like ever having to pull an all-nighter? Never want to work a minute past 5? That's OK, but it means you have no real responsibility, and you will be compensated accordingly. Others choose more responsibility, and they man up when the shit occasionally hits the fan.

No, that means you work for mature people who have planning and organizational skills. Having to come in at 3am is not a sign of responsibility, it's a sign of immaturity and failure of management.

Yes, it happens. No, you shouldn't laud it. If they were building bridges, people would be dying - but this isn't bridge building, so it's somehow more okay?

Re:Cue: The 10 hour scramble to launch two days early by drusenko on Friday June 22, 2012 @10:33PM (#4149867)
A startup is not building a bridge. You don't meticulously plan your every move for 3 years before you start.

A startup is jumping off a cliff and figuring out how to build a plane on your way down.

Re:Cue: The 10 hour scramble to launch two days early by georgemcbay on Saturday June 23, 2012 @03:55PM (#4151650)
"A startup is jumping off a cliff and figuring out how to build a plane on your way down."

Suicide, then?

Re:Cue: The 10 hour scramble to launch two days early by gringomorcego on Friday June 22, 2012 @10:34PM (#4149870)
Putting up with that shit is fine when you have founders shares. If you don't, then get ready to clock out and iron the hawaiian shirt. Expecting the engineers to just deal with this is prebuscent.
Re:Cue: The 10 hour scramble to launch two days early by kevinclark on Friday June 22, 2012 @04:36PM (#4148637)
Engineer at Cue here.

This was a team decision. There was no mandate from on high - we're not abused. It was time to ship, so we made it happen.

Re:Cue: The 10 hour scramble to launch two days early by asarazan on Friday June 22, 2012 @04:43PM (#4148689)
What he said.

Furthermore it's worth pointing out when trying to execute a coordinated media push (especially with traditional media), you have no choice but to give a lead time and put an embargo in place. This is standard practice when dealing with publications.

9 times out of 10 it goes off without a hitch. We were the 10%, so to speak.

Re:Cue: The 10 hour scramble to launch two days early by RoboTeddy on Friday June 22, 2012 @04:40PM (#4148664)
The team at Cue is extremely talented and prideful of their product, and such teams are happy to crunch now and then in order to make things happen.
Re:Cue: The 10 hour scramble to launch two days early by moe on Friday June 22, 2012 @07:26PM (#4149424)
How is that an excuse for bad management?
Re:Cue: The 10 hour scramble to launch two days early by Dave5314 on Friday June 22, 2012 @10:07PM (#4149820)
hey moe, let me know when you ship a product rather than spending your entire day trolling on hacker news and tearing down the people who are actually doing something with their lives.

It's not that you criticize or critique other people's work, it's that you're consistently a dick about it.

Nearly all your comments are sarcastic and mean-spirited. IMO you're a liability to the Hacker News community.

One of the great things about hacker news is that we can have an open dialogue with the founders of startups. If you're acting like a jerk, they'll stop being so open.

If people like you keep acting like jerks, you're destroying the spirit of HN and the dialogue this community depends upon.

Re:Cue: The 10 hour scramble to launch two days early by moe on Saturday June 23, 2012 @10:02PM (#4152384)
Hey "Dave5314".

In which thread did I offend you and why can't you just reply there using your real HN-account?

I'm afraid your cry for "open dialogue" doesn't work so well when you plant it in a seemingly random thread using a throw-away account...

Re:Cue: The 10 hour scramble to launch two days early by Dave5314 on Tuesday June 26, 2012 @01:48AM (#4160496)
1.) What makes you think this isn't my "real" HN account? Long time lurker, new commentor. Unlike the founders you tear down, you're not using your real name or any identifiable email address or title/company you work for, "Moe." Afraid to put your name on your hateful remarks? Your account is just as throwaway as mine, you can easily create another vitriolic spewing alias safe from any repercussions. How about this - in the interest of open dialogue. Put your money where your big snarky mouth is. I'll say my real name if you say yours.

2.) Ahhhhh where did you offend me? Here for one.

This isn't random. I think it's mean spirited and insensitive that the Greplin/Cue founders and team members are here. Writing under their own names, their classmate from their YC batch is here writing under their own names and after what seems to be a brutal push with no sleep and lots of stress, all you do is swoop in with "bad management" snark and then swoop out.

Asides from that....

There is this comment:

http://news.ycombinator.com/item?id=4126285

and this one:

http://news.ycombinator.com/item?id=4126422

and this:

http://news.ycombinator.com/item?id=4106497

and this gem:

http://news.ycombinator.com/item?id=4068214

notice a pattern?

your nastiness and at best insensitivity and at worst malicious disregard of others is only matched by your arrogance and superiority.

and of course your oh so witty response to Leo Kim of Foursquare, when he rightly called you out on making tests to make mongo fail .... I reached the same conclusion he did.

Troll.

Let's disregard for a minute, your obvious gaping technical knowledge and your sheer lack of Silicon Valley business acumen. Let's say you managed you convince PG that you aren't a prick and somehow you get into YC. In your weekly meet ups would you ever say any of the above comments to peoples' faces?

HN is suppose to an extension of YC, a place where hackers can come together, take about things of interests, their own projects, start ups, etc. Your entire comment history is subversive to that and completely against the guidelines:

"Be civil. Don't say things you wouldn't say in a face to face conversation.

When disagreeing, please reply to the argument instead of calling names. E.g. "That is an idiotic thing to say; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3." "

Hacker news would be better off without you, you and people like you are bringing a cynical, negative, schadenfreude cloud over what is suppose to a culture centered around idealism, optimism and wanting to change the world- not insulting those that do.

Re:Cue: The 10 hour scramble to launch two days early by moe on Tuesday June 26, 2012 @06:36AM (#4161106)
Lol, I must really have flipped you off.

What makes you think this isn't my "real" HN account?

The fact that it will be abandoned shortly after you realize the feebleness of your little vendetta. Yes, I can predict the future! ;)

would you ever say any of the above comments to peoples' faces?

Yes, actually I do. As you can see I even respond to throw-away accounts, I'm just straight-edge like that.

Other than that I'm sorry to break your heart yet again, but I'll probably continue to stick to the voting system for feedback rather than anonymous rants.

Re:Cue: The 10 hour scramble to launch two days early by gringomorcego on Friday June 22, 2012 @10:30PM (#4149861)
anyone want a dish with ad hominem and a sprinkling of superiority?

You're right, moe probably hasn't shipped anything. I haven't either.

But that doesn't mean that it's okay for you guys to treat engineers like this. Because one of them might just realize how undervalued and mistreated they are, and think about starting their own comapany...

Re:Cue: The 10 hour scramble to launch two days early by Dave5314 on Friday June 22, 2012 @11:01PM (#4149896)
and when they do they'll realize that building a company is fucking tough and sometimes you might have to ask your team to work long hours. None of the Cue engineers that have commented on here have said that they are undervalued or mistreated. It was a team decision - they want impact, they love their product. They wanted to work.

Frankly I'm disappointed that so many folks on hacker news think working long hours on a product is abusive. Newsflash--journalist work long hours to beat deadlines, musicians spend days in the studio recording their music, politicians and their aides spend long hours on the campaign trail, writers write well into the night. If you want to change the world, you going to have to bust your ass doing it.

And p.s. Moe has continually behaved like an ass on this forum, making snide insulting comments to countless people. He's the last person anyone should be white knighting. He's served an entire buffet of "ad hominem" and superiority. It's time he got called out for his dickish ways.

Re:Cue: The 10 hour scramble to launch two days early by gringomorcego on Friday June 22, 2012 @11:13PM (#4149916)
Hey, as long as they have founder shares, im all for whatever your gung-ho routine entails
Re:Cue: The 10 hour scramble to launch two days early by Dave5314 on Friday June 22, 2012 @11:35PM (#4149949)
God forbid people actually work on something because they love it and want impact. In majority of those professions I detailed above, they make much much less than engineers but they still work hard and work long hours. Not everyone is mercenary. Why do you think so many rich people in tech still work? still build? If it's just about shares and profits, then head to finance. though I doubt they'd appreciate the whinging about long hours....
Re:Cue: The 10 hour scramble to launch two days early by MatthewPhillips on Friday June 22, 2012 @04:45PM (#4148707)
> such teams are happy to crunch now and then

No one should ever be happy about working for free. Being a good team player means sometimes doing it anyways, but the situation that caused it should be rectified first.

Re:Cue: The 10 hour scramble to launch two days early by mahyarm on Friday June 22, 2012 @07:09PM (#4149359)
Mistakes happen. What employers should do in this kind of crunch time is offer a long weekend at the end of the crunch period. Most don't.
Re:Cue: The 10 hour scramble to launch two days early by natrius on Friday June 22, 2012 @05:03PM (#4148785)
Unless the employees are being paid hourly, they're not working for free. That's how salaries work.
Re:Cue: The 10 hour scramble to launch two days early by languagehacker on Friday June 22, 2012 @10:18PM (#4149842)
How much is your salary really worth if you're working twice as much as someone making the same amount? What's the value of your free time? How frustrating would that be if you knew it could be avoided?
Re:Cue: The 10 hour scramble to launch two days early by kalleboo on Friday June 22, 2012 @05:52PM (#4149009)
> No one should ever be happy about working for free

Why does "crunching" have to mean working for free? I didn't see anything about that in the article.

Re:Cue: The 10 hour scramble to launch two days early by MatthewPhillips on Friday June 22, 2012 @06:44PM (#4149262)
I associate it with working late, am I wrong in this case?
Re:Cue: The 10 hour scramble to launch two days early by robryan on Friday June 22, 2012 @09:49PM (#4149786)
No reason why it has to be unpaid overtime.
Re:Cue: The 10 hour scramble to launch two days early by spullara on Friday June 22, 2012 @10:11PM (#4149828)
Overtime? What planet are you people from?
Re:Cue: The 10 hour scramble to launch two days early by dllthomas on Friday June 22, 2012 @04:50PM (#4148733)
> No one should ever be happy about working for free.

I don't know if I agree with that statement.

Re:Cue: The 10 hour scramble to launch two days early by MatthewPhillips on Friday June 22, 2012 @04:52PM (#4148745)
Fair enough, in the context of an employer/employee relationship then.
Re:Cue: The 10 hour scramble to launch two days early by dllthomas on Friday June 22, 2012 @04:58PM (#4148763)
Yeah, I think "you should never expect someone to be happy about unpaid work" might be closer.
Re:Cue: The 10 hour scramble to launch two days early by mthreat on Friday June 22, 2012 @05:00PM (#4148774)
Assuming they hold options or shares, it's not likely to be "for free". (edit: I meant to reply to the parent comment)