Not a Hacker or a Hipster – How I Got My First Startup Job
medium.com
medium.com
Maybe if you're a young woman (as the author is) approaching someone at a coffee shop, then sure.
Reverse the genders and watch the interaction take on a dramatically different character.
https://medium.com/life-learning/what-are-people-working-on-...
Anyone who's tried to get petitions can attest that doing this on a street corner is a much different beast, but I think hallway testing (or lead finding, or whatever else) is more viable than most people think.
I'm also reminded of the study about asking people for their seat on a subway - it's almost impossible to ask, but surprisingly easy to succeed.
Now, perhaps it will not work so well for every person. Perhaps in the general case people will instead recoil in horror at being approached nicely for small interesting favours. Perhaps a more universal lesson to take away from this is that success is more likely if you play to your strengths, and push every advantage at your disposal. The author is a Cambridge Law graduate, so one might safely presume reasonably skilled at speaking - I'm not exactly sure how surprised she was that she could engage strangers in professional conversation at a coffee shop - but the experiment is available for others to replicate! I'm not sure what parameters would have to be changed for the interaction to take on a "dramatically different character" though, maybe don't get drunk beforehand.
I dunno, give it a shot. I generally don't have much interest in just randomly starting up conversation, but when I talk to a stranger about something it rarely goes poorly.
you don't know if you don't try.
Never again!!
Hint: startup is more like 7-10y+ unless you're just playing at it, or it fails. If you go into it expecting it to be a year, it probably will be.
The job was technically sales ...
And: Yesterday was my last day there as I’m
now moving on to something new — planning
to develop my currently non-existent
technical skills full time.
So categorizing the author as being new "to the industry" at that point in time (2015/07/30) is nonsensical unless peripheral exposure counts. Not to say this remains the case, mind you, just that the perspective you describe is not applicable to the person the author was at that time.I will add that a person actually in the industry would be wise to "stick around" their first job or two for at least a year. Failing to do so is a red flag for many companies as bouncing around early in the CV is often interpreted as leaving before being fired.
Sorry, I have little idea what your point is.
At the time this blog entry was written, she was working in a sales/marketing capacity and not as a coder (her words, not mine). IMHO, this means she was exposed to tech start-ups. She then goes on to say that she had "non-existent technical skills."My point was that anyone entering into the dev/tech world would be wise to spend a year at their first job in order to:
* Learn about what is involved
* Have time to refine their skills
* Be able to show to other companies that they can survive
Yes, but that was what she was looking for when she said "find one start-up I wanted to devote the next year or so to building" and what I agreed with as "some sort of minimum commitment as an employee"?
My plan wasn't to leave after the year, just to re-evaluate if I was learning what I wanted to be in the role. As it turned out, I did leave as I wanted to develop my technical skills instead of carrying along the VC/Biz-dev career path.
I agree that if you're starting your own thing then 7-10 years is a good minimum time frame.
This sound like very good advice.
Unless we're talking contracts of course, then you'll simply want the best technical candidate because you need someone who can deliver good quality on time.
I've heard countless times from other developers that they would be happy to hire a competent programmer with no familiarity with their stack because it's better than waiting 6 months to find a dev with the preferred experience. I've never seen or heard about this in practice.
I'm not from a God-tier school, but I've been on teams solving non-trivial problems. And I was flown across the country before I had experience like that.
> My job search experience has been that it's pretty much "perfect match or gtfo".
I've seen a lot of that, too. Maybe their own nth degree persnicketiness is why they have problems filling positions and are willing to fly people in from far away. I was once flown halfway across the country by a medium-small webdev company just north of the golden gate bridge.
Chutzpah's critical though- you're usually not going to get what you want if you never ask for it. You can wait a really long time for people to just give you what you want, especially if you never express an interest by asking for it.
It sounds like common sense, but it feels like it took about 20 years too long for that to really sink in with me. I always assumed people understood me a lot more than they actually did.
Over the 200 waking hours, I managed to
hit the standard needed. It felt like
multiple lucky answers and lots of Googling
that got me there, but that’s how learning
works. I learnt enough Javascript to
get accepted onto the course and I spent
another 3 months, with 15 others,
Googling things together and creating
a new app each week.
Now I’m being paid to build early
MVP’s (minimum viable products) for
start-ups. So I can code.
I mean, really? This certainly cannot be modus operandi for start-ups can it? Three months of "Javascript Googling" allows someone to brag about: being paid to build early
MVP’s (minimum viable products) for
start-ups.
And leveraging that incredibly weak argument into a summary of: So I can code.
Wow. If that's all it takes for someone to be hired into a start-up, then the whole "funding is drying up" meme prevalent recently is really making sense.0 - http://www.gadgette.com/2016/02/19/how-i-learnt-to-code-in-a...
Its a sad realization that someone who only started coding 3 months ago is kicking my ass finding jobs at startups meanwhile I am being rejected( when they respond) constantly .
[1] I hate 'culture fit' as a reason to employ someone. Employing people who fit in with the existing culture is a fast track to creating a business completely lacking in diversity.
Then after I left I spent 2 weeks solidly trying to hit the course requirements, then 3 months on the coding course. There was also time before that learning syntax on coding academy in my evenings.
Since finishing the course (in December 2015) I've been freelancing with some mentorship at Founders & Coders. It's only now that I feel I could apply for a role as junior dev. So really it's been 7 months, and a lot of hours, getting to that standard.
Part of the beauty of the current startup landscape is feasibility of throwing a working prototype written by a junior, garbage code and all, into production to see if it gets any traction. It costs little money, offers a chance to hungry juniors to prove themselves and later drives the demand for senior engineers to clean up or rewrite the codebase into something that can scale.
beards and winter hats in summer seem, counter intuitively, to incubate a lot of unique little snowflakes.
"At SXSW, Rei Inamoto, the chief creative officer for AKQA, shared a nugget of wisdom that I’ve observed to be true: “To run an efficient team, you only need three people: a Hipster, a Hacker, and a Hustler.” - http://www.forbes.com/sites/andyellwood/2012/08/22/the-dream...
It was a colloquial way to get across the point that I couldn't code or design at the point I was looking for a role at a start-up.
Meanwhile, I am being humiliated by stupid whiteboard interviews .
I really need to work on my (non existent ) people skills.
I just went through my most humiliating whiteboard interview last week. Never knew how bad it could get until that...
No matter how experienced you are you have to face this everytime you change jobs.