Earlier quoted context omitted.
Given that this is a brand new thing, it sounds a lot like they are failing you massively on this bit of the promise - at the very least, and given you're paying for this, it's not FB and Google that failed to show up - it's Hack Reactor that failed to make them show up: > WE’VE GOT CONNECTIONS > Breaking into the tech industry can be hard on your own. We’ll help you craft a portfolio, guide you through practice inte…
Let's stop the misunderstanding right here. They've done a fantastic job, both in terms of teaching and connections. 100% of the recently graduated first cohort is hired. Their connections have brought top-rate speakers from Heroku, Pinterest, Twitter, TapJoy, Coursera and others and the connections did get more companies in the door than we have graduating students. That list just doesn't include some companies that…
Dear HN "Who's Hiring" responders
201–210 of 212 posts
Re: Dear HN "Who's Hiring" responders
#202Earlier quoted context omitted.
Seriously, try hiring someone, the influx of irrelevant applicants and those who won't take even thirty seconds to read your ad is truly dispiriting. The average time of inspection of a resume is 15 seconds, so it seems it's a two-way street.
The average time of inspection of a resume is 15 seconds, so it seems it's a two-way street. Heh, quite. Although from my experience, receiving a hundred CVs featuring C# application development alone when you've requested PHP will have a significant effect on the average reading time ;)
Re: Dear HN "Who's Hiring" responders
#203Earlier quoted context omitted.
I thought the same until I actually worked with one. This guy can build things in a week that a group of 5 competent programmers will do in a month.
But, as `sybhn said, did that guy call himself a rock star? My manager is very similar--his mind works about twice as fast as mine, and he's very productive. He'd never, ever call himself a "rock star" though.
Re: Dear HN "Who's Hiring" responders
#204Earlier quoted context omitted.
I thought the same until I actually worked with one. This guy can build things in a week that a group of 5 competent programmers will do in a month.
And yet he doesn't get paid proportional to that ratio. He probably makes 20% more.
Re: Dear HN "Who's Hiring" responders
#205Earlier quoted context omitted.
I'm not familiar with that stat but it's perfectly believable. Many people are clearly getting by with a mixture of memorization and trial-and-error rather than understanding. I think of those who understand algorithmic reasoning (i.e. understand loops, assignment, etc.) they also fall into two categories. Those who can understand more abstract programming concepts (indirect referencing, recursion) and those who can'…
Recursion isn't hard, it's just not taught correctly. It's fairly easy to break it down into rules. Because they are shown examples, instead of taught how, people memorize how to do stuff, instead of learning it from principles. Take the classic question, recursively reverse a linked list. You will see a lot of people making false starts, or trying to reverse the list in some way like they would reverse an array, or…
In my mind, a link list is a bunch of nodes with arrows pointing right. To reverse the list, all I need to do is point the arrows to the left.
6(ish) lines of code later, and I've got a recursive reverse method.
Re: Dear HN "Who's Hiring" responders
#206Earlier quoted context omitted.
Essentially every recruiter message that I've received on LinkedIn follows one of two patterns: a) Hello, you do Python, do you want a job? (with no position details, salary, reason to join, etc.) b) a) followed by a clumsy attempt to fish details of my contacts (I don't connect with recruiters). So, er, yeah - "Ha ha, profession!"
I don't doubt the abundance of bad behaviors. I was just doing a literal parse of your logic.
I'm not saying "I have this message from a recruiter, therefore all recruiters are scum." It's a reminder.
Re: Dear HN "Who's Hiring" responders
#207Earlier quoted context omitted.
I had a good laugh at that quote, but now I'm thinking: is it legit to cite one or more persons doing their job poorly to dismiss the entire profession? Do you keep around bad code to remind you why you don't talk to programmers? Examples of quack medicine to remind you why you don't talk to doctors?
Essentially every recruiter message that I've received on LinkedIn follows one of two patterns: a) Hello, you do Python, do you want a job? (with no position details, salary, reason to join, etc.) b) a) followed by a clumsy attempt to fish details of my contacts (I don't connect with recruiters). So, er, yeah - "Ha ha, profession!"
In LinkedIn I've been contacted by recruiters from Amazon, Google, Toshiba and Voyer International and all of them have been quite professional.
Re: Dear HN "Who's Hiring" responders
#208Re: Dear HN "Who's Hiring" responders
#209Earlier quoted context omitted.
...and was amazed how most of them feel comfortable being completely ignorant of new technologies/libraries/frameworks/best practices/whatever. I don't know how to judge that comment. It is true that if you take anyone who is competent and ask them to teach you something that they learned in the last year, they should be able to come up with something. If not, then you've likely got "1 year of experience, 15 times".…
From what you have written I can see you don't suck (I'd need to meet you and see some of your code to actually assess you're good :). You see, you used words like "Bayesian", "Promises". Guys that I was writing about not only don't know what promises are, they don't give a fuck either. A rockstar (in my book, at least) would hear about them and google them as soon as possible. So at the end of the day, it's not real…
I only know "Promises" because I saw that on HN recently. However the concept behind JavaScript promises is one that I've seen before (I first saw it buried in a sideways way inside of http://search.cpan.org/~karasik/IO-Lambda/) and the name "promises" already has a spot reserved in my brain for their use in infinite streams. Therefore if someone mentions JavaScript promises to me again in 6 months I'll draw a blank.
There are some code samples linked in the articles in http://elem.com/~btilly/ab-testing-multiple-looks/index.html if you want to look. I wasn't writing that code for anyone except myself, so it isn't particularly pretty. (It did get the job done though.)
Re: Dear HN "Who's Hiring" responders
#210Earlier quoted context omitted.
It is absolutely a hirers' market if the market is for a low-level coder. Many people, especially coming from an engineering background, have the requisite programming and computer science experience to do what you need. It's a hirees' market at the rockstar level, as always.
Rockstars are a myth. So are low-level engineers who "know what they're doing." Hire smart people who can learn new things instead of resume bullet points and/or mythological creatures.