Reasons to Turn Down That Startup Job
deardesignstudent.com
Reasons to Turn Down That Startup Job
1–10 of 48 posts
Re: Reasons to Turn Down That Startup Job
#2Waiting for the perfect time and feeling not competent enough without a patronage (i.e. points 1-3) are my biggest educational regrets. Sure, in startups there is a bias for being too independent and confident. But virtually all other places (including academia) are not good for skilled minds and independent spirits - they rather expect you to respect hierarchy and status quo.
Surely, not everyone is mature enough to learn by trials and _erorrs_. But by listening to superiors one may never mature.
Re: Reasons to Turn Down That Startup Job
#3This should really be "8 reasons to turn down that startup job as your first job" as most of the bullet points are really only geared towards someone in or leaving college. This should be obvious from the website's name but without context it took me a minute before I realized.
That being said the #7 point of "The world needs fixing, not disrupting" seems to lose sight of what disruption really is and conflates it with simply taking advantage of people.
Disruption fixes things. In fact I think one could easily argue that disruption fixes things far more effectively than anything else. Telling someone to go find "real problems to solve" is simply useless. I don't understand the point of trying to make the "service economy" a place "Where entitled white boys figure out how to replicate their private school dorm experience for life".
Sure there are issues in this area with SOME start-ups but going right into calling it a race issue without providing anything useful just screams useless rant.
Just drop #7, rename to 7 reasons and update the HN title to make it more obvious of the target demographic. Just my thoughts.
Re: Reasons to Turn Down That Startup Job
#4As a developer my experience has been the direct opposite. Getting my first job at a startup was a the best decision for me. I think I have more width (rather than depth) of knowledge because of it, (since I worked in wider verity of roles).
Maybe for a designer this is different. Probably the title should point this out?
Re: Reasons to Turn Down That Startup Job
#5This should really be "8 reasons to turn down that startup job as your first job" as most of the bullet points are really only geared towards someone in or leaving college. This should be obvious from the website's name but without context it took me a minute before I realized. That being said the #7 point of "The world needs fixing, not disrupting" seems to lose sight of what disruption really is and conflates it wi…
I agree with you 100%. You're going along reading a bunch of very reasonable and helpful advice, then BAM, politics, stereotyping, and class warfare! One can observe that most of the "problems" that today's startups are solving are not very interesting or inspiring without resorting to politically charged language and personal attacks (and for the record, I agree that the ideas he lists are silly at best).
Have to give credit, though; he saved it for the end. If that's #1, I don't bother reading the rest and I would guess many others wouldn't either. So that's clever at least.
Re: Reasons to Turn Down That Startup Job
#6More like 8 ways to become another drone.
Re: Reasons to Turn Down That Startup Job
#7This article is aimed at designers, and maybe it makes good points for them.
But for developers beginning their careers at a startup, most of these points just don't apply. I cut my teeth at an early startup, and just for example: people taught me how to be a better developer (#2), I went wider rather than deeper (#3), and I had a great mentor (#4).
Re: Reasons to Turn Down That Startup Job
#8As a developer my experience has been the direct opposite. Getting my first job at a startup was a the best decision for me. I think I have more width (rather than depth) of knowledge because of it, (since I worked in wider verity of roles). Maybe for a designer this is different. Probably the title should point this out?
I'm with you here. After working at a startup for 1.5 years I became a solid full stack developer with the ability to very quickly adapt to the current task.
There's a point about going "wide" instead of "deep" in the article, and I can surely say that working at that startup gave more "wide" than anything else.
And by the way, at the job where I am at the moment, I had to use a severely limited skillset and had to use a couple of same technologies all over the place.
Re: Reasons to Turn Down That Startup Job
#9Also relevant: Fuck You, Pay Me by Mike Monteiro.
Re: Reasons to Turn Down That Startup Job
#10As a developer my experience has been the direct opposite. Getting my first job at a startup was a the best decision for me. I think I have more width (rather than depth) of knowledge because of it, (since I worked in wider verity of roles). Maybe for a designer this is different. Probably the title should point this out?
Many startups see development as the product, and design as the pretty.