Speaking from experience, if you keep getting advice based on your age and if you keep comparing your work to other people your age, it will be a lot more difficult to get to that next level. Whereas, if you compare your work to just plain good work, you won't be able to say "Well, at least this is much better than most of what people my age are doing," which really means nothing because most people aren't doing shit.
Untitled topic
21–30 of 42 posts
Re: undefined
#22Benefit: A lot of users are (cheaply) drawn to the post. Some snobby coders are going to be upset, but still check out your product so that they can complain about it.
Cost: Some really vindictive coders might go out of their way to slander you? (Man, I really hope not...)
Re: undefined
#23Best case scenario, It just sounds like those mobile email signatures, that excuse themselves for a crappy and short response.
Re: undefined
#24Re: undefined
#25Most of the kids intelligent enough to find this community and build something on their own are probably much more interested in sincere and helpful feedback than upvotes. If anything, upvotes are just a tool for them to get more visibility and therefore a better chance of good feedback. I know that's how I felt when I was their age. I think this community would be a lot better off it we spent our energy giving useful feedback to those who ask us for it instead of bickering over non-issues like this.
Re: undefined
#26People here upvote what they find surprising or interesting (tech or science related stuff). If people find surprising that a kid that is starting high-school has been able to develop an app (and statistically, it's quite surprising), they upvote it.
If a kid thinks that some people might find interesting that he, being as old as he is, has developed an app, he has the right to submit his app to HN.
Generally, I don't know why we shouldn't submit what we think other geeks may find cool.
Re: undefined
#27This post is wrong on so many levels. It basically indicates that the author has zero recollection of being an awkward teenager without self-confidence. As someone who was 15 and making Windows freeware in 1997, let me tell you - it mattered a whole world that people acknowledged that what I was doing was very impressive for a 15 year old. I actively told people that I was the author of X and that I was 15, specifica…
Not only that, I feel like someone starting out stands to be affected a lot more by negative feedback. In this case knowing the experience level gives me a chance to word my advice in such a manner as to help them improve while also encouraging them.
Re: undefined
#28To be fair, my expectations of the work of a female norwegian programmer would be similar to my expectations of an American male programmer of a similar age.
If you have a programmer who is ~14 and they did something, you can assume a few things will be true:
They did it without any significant financial backing.
They did it part time, as they are probably legally required to be following a general education programme full time.
They did it without a formal degree level education. The most advanced math they have probably been exposed to is basic algebra and trig.
They did it with around max 5 years programming experience.
Re: undefined
#29Using your age to promote your project is just another use of competitive advantage on another axis. Marketing is a big part of software, so if people are drawn by an unusual age (playing on the novelty factor), use it.
Also we should be encouraging more young people to enter the industry, not slapping them for being excited about it. No wonder more and more people see software engineers as vindictive jerks. Caramba.
Re: undefined
#30> why mar the pride you should be feeling with manipulation? Because the achievement is greater with context of the creator. It's actually more interesting when a 14 year old creates a mediocre iOS app compared to 24 year old. Similarly it's more interesting when a 6 year old runs a marathon or a 10 year old graduates college (yes, both happened). Honestly it sounds like the writer is bitter for whatever reason. HN h…
Because the writer doesn't understand how important context is to understanding. The yc application isn't up right now, but I remember a question on it along the lines of "why you?" Reality is not a function of the event as event, but of the relationship of that event to past, and future, events.