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

The exaggerations in titles are really starting to bother me.

Yes, you started with 300 lines of code... But then you modified it several times for different conferences, and enhanced it a lot when you really become popular. Only after that did you sell it.

The actual number lines actually hovered around that until we sold. It was fork soup because we hardcoded everything for each event (I love git so much for making that so easy). For every event, we always seen it as just one more event for promotion so we didn't want to make everything configurable. Simple and easy to test basically.

Towards the very end we rewrote everything, made it configurable, integrated all past features, and made a UI designer for designing labels (instead of hardcoding the layouts) and then we sold.

Never has the measure of 'lines of code' been less relevant to anything though.

Yup, every fork = +300 LOC! :P

yes. I didn't like measuring it. My partner thought it was significant though.

Sorry, this is very snarky, but seriously (over)paraphrasing:

``We didn't really have anything to sell until "we rewrote everything [and] made it configurable".

Would you say you could have sold without a rewrite? Did you try and sell before that and fail when the buyer started their due diligence?

We could of sold specific versions for different organizers (we did actually give out 2 versions for free to our first event organizers that are hardcoded as a thank you gesture to them and it is still in use). But we wanted something more flexible to sell to the people that contacted us in the past. We spent 2 weeks, cleaned it all up, and got it ready. At the last minute, we started to speak to someone we met at a conference we were at again that wanted to push it. We worked out a deal for his team take it over, maintain, and support it and the rest is history.

Despite the 300LOC stuff, it's still a really inspiring story. You started with a hack, learned a bunch, wrote some code in two weeks, and sold it for, what sounds like, just over the non-trivial threshold. Good job :-)

and evangelized the hell out of it, too, which isn't exactly easy work.

i mean, its still a good story. but the tl;dr title isn't accurate.

Titles aren't meant to be a tl;dr

they aren't always, no, but this one's wording definitely sounds like a summary, and is at least somewhat misleading.


Because HN used to be above that linkbait BS.

The story is interesting and useful and stands up on its own without having to resort to "in only 300 lines!!!".

What HN used to be above is this stupid pedantry. 300 lines of code is a euphemism for a simple system. That's it. Who gives a shit if the actual system was 800 lines, or even several thousand lines?? The system they made was simple.

Notice how it's a self post? It's not some grand ploy to get more pageviews for a blog. What's bullshit is that half of the comments section is being taken up by this contentless debate. That's the actual poison on HN.

original title doesn't show the exclamations, you know: scope and citing :)

Why is it every community ever is awesome until that third person joins? Then suddenly it's all about how things "used to be".

Are linkbait BS titles the cancer that is killing /HN?

When you hear people complain about "<foo> used to be", just mentally replace it with "I think <foo> should be". Whether or not it was true in the past was irrelevant. The main focus should be the statement of how things should be. There's a widespread tendency to romanticize the past, and fighting against it is fighting against human nature.

Granted, HN used to be above romanticizing the past... :-)

No. It's people not being in /new enough and voting up good stories after actually reading them. That way, the "linkbaity" stuff is more likely to get voted up. But this is a problem most vote-based link sites have, alas.

>No. It's people not being in /new enough and voting up good stories after actually reading them.

What's the solution to that, I almost daren't mention it, could it be a dig like toolbar that wraps the story (I'm assuming you mean external articles). Perhaps better would be a personal list (like Reddit) of recently viewed posts.

Alternatively one could have a sort of moderation view for trusted users so that pages like /new would give the story link with a first paragraph and up/flag/down buttons for fast rating. That way standard users time on pages like /new or /noobstories wouldn't need to be spent on spam so much.

Not that spam appears to be a huge problem here but as things grow optimisations become more important IMO.


I would have upvoted it if it wasn't for the hyperbole. It was a good story, with a crappy title. So I didn't upvote.

I get tired of everything ;)

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