warwick

If you haven't put the time into creating a reputation (either for yourself or for your product) and getting people excited about your next release, you aren't going to suddenly find yourself able to tap into a nonexistent audience.

What you can do is grow your reputation by creating great products and growing a community of people who are interested. Launch to a hundred people, and don't be disappointed that you're not a hit by next Tuesday. Overnight success stories are rare, and almost always backed by years of hard work. There's no secret website that you have to submit to and people will suddenly start using your product.

You'll gain users over time. At least in my experience, now is the best time for iteration. You've only got a few users, and you can actually interact with them as people, not just statistics.

I was following along with the analogy, but this really bothered me. "If I am fat, then I ate more calories than I burned" isn't vacuously true (because there are people who are fat), it's a tautology.

I don't know anything about nutrition, but seeing an error in the small part of the article I do know something about makes me more skeptical as to it's premise.

EDIT: After a few more minutes thought, I have to mention that since we've all eaten more calories than we've burned (or else we'd be massless), the statement is true for everyone, not just obese people. But that's just me being needlessly pedantic.

[1] http://developer.apple.com/library/ios/#documentation/UserEx...

Of course reports are greatly exaggerated. For something like 'the web is dead', which is essentially punditry, reports will naturally trend towards being premature as the incentives for publishing are biased towards publishing early.

You don't get page views on opinion pieces if they aren't controversial. Things are rarely controversial unless they're exaggerated.

The more interesting question is not if the web browser will eventually diminish in importance, but rather if the web will eventually be eclipsed by custom fat clients.

AppThrob sounds like it'd be better for an app review website. "AppThrob, Apps You Love".

Also, make sure you get a good sleep. There's nothing worse than wanting to be calm on stage while being jumpy from lack of sleep.

Web apps are superior for the reasons you mentioned. As a developer, it's just easier to deploy a web app. That being said, I think you ought to be thinking about the users experience, not the developers.

App store approval processes mean that users have to wait longer for fixes. Using a particular device API means that your app just isn't available to a lot of users.

On the other hand, native apps tend to respond faster, be more in line with the users expectations, and offer the developer a slick way to accept the users money without asking them to put in all their credit card info.

You also have to look at how users expect to install apps. At least on iOS, every web app I've seen has to include install instructions because users don't think about installing them.

I think I can give users a better experience with a native app, and that's what makes the choice for me.

The rule about having to be here for a year before you can even talk about if we're turning into Reddit. It's in the guidelines, but I think it's worth mentioning under "Is HN becoming like Reddit and Digg?".

It's also pretty courteous around here to note any edits you made to your comment with a brief footnote, or by adding the additional content as a footnote itself. The footnote should mention what was edited, not just that the edit occurred. That bit of etiquette might fit under "Someone edited a comment I replied to and now I look like an idiot!"

Some things that I don't see right off, but would love to have:

- Photos of cliff faces, possibly with route overlays.

- GPS integration.

- User submitted photos, reviews, tips.

- User submitted routes.

(Edit: wrote 'auto' instead of 'audio' originally)

To avoid incorrect profile data, it might be implemented so that if a field is never given focus, it would be treated as blank.

I'm suspicious of anyone who claims to be an awesome coder. That's an honour that others bestow on you. Instead, strive to be a better coder than you are now.

In much the same way that starting the day with breakfast gives my days a sense of rhythm, walking once a week gives my weeks a good demarcation.

Since most stacks were interpreted, not compiled, you could just look at the source. HyperTalk is why I learned how to read code. I still remember when I finally realized what HyperCard meant when it said 'too much recursion'. It was like a flashbulb going off in my brain.

The modern equivalent, in terms of 'wow, how do I do that?' is obviously Javascript, but HyperTalk was just easier to read and get started with.

A minor happy note: iOS autocorrects the capitalization in HyperTalk and HyperCard. That just made me very happy.

- Make the list a manageable size. I find more than 30 or so items overwhelming.

- Never let the list run out. I add new items constantly. The last ten or so items all read 'Expand this item: (some high level feature that can be broken down)'

- Mix easy and hard items. Striking an item off the list is satisfying, so make sure that after a particularly hard item, you can breeze through two or three more.

- If you're encountering a lot of hard items, spend some time expanding then into separate line items.

- At the end of the day, don't give into that temptation to polish off the easy item at the top of the list. Otherwise you'll work your way through a couple more easy items and end up having to start the day at a hard one.

- Have a visible backlog of your completed items. It's satisfying when you feel like you aren't making progress.

- Always attack the list in order. If you find yourself needing to move items around to satisfy dependencies, go right ahead, but if you skip and item because you just don't feel like working on it, at the end of the project you'll have a whole list of items you don't feel like working on.