71–80 of 290 posts
I suppose this refers to us (and our Will the real programmers please stand up post). If it doesn't, excuse our self-centeredness and kindly disregard this message. Our salary structure is designed to select for exactly the type of people we want to attract - the kinds of people that will go through walls to bend the world to their will, for some deeply ingrained reason unknown to anyone but them. For people like tha…
Earlier quoted context omitted.
That's silly, physicians, mechanics, lawyers, and many other skilled tradesmen are just like programmers. The problem is that many folks see programmers as somehow different than these folks.
Doctors, dentists, and lawyers have legislated their jobs so that they can maintain monopoly through their guilds and licenses. That's why they can charge such a high rate. If programmers can get non-licensed programmers writing code go to jail, their rate would go up, too.
If you've been around yc for more than a month, you've doubtless seen a number of links to articles on motivation as it pertains to creative activities like software development. The consensus is pretty clear. Incentives hurt productivity in creative activities. This seems to have something to do with the relationship between creative effort and intrinsic vs. extrinsic motivation. The prospect of an incentive seems t…
You have to understand: there's more to hiring programmers than paying lots of money. If that were the case, we wouldn't have had a dot-com bust and software companies would be dominated by MBAs. That's the hard part of hiring programmers. How do you incentivize the good ones to work for you? If you have a solution to that problem, I suspect you'll be a very much in-demand person.
> How do you incentivize the good ones to work for you? If you have a solution to that problem, I suspect you'll be a very much in-demand person. Bonuses, perks, and congrats on jobs well-done. If I spend 40 hours between Dec 31 and Jan 2 writing up a new wireless barcoding system because the powers that be decided at the last minute to begin the new year with a different process for warehousing, I better get a damn…
I think you have it exactly backwards. The best programmers I know seem to be indifferent to cash. They work on the most interesting project they can find that pays them enough to live. Hiring people like that is really tough.
> The best programmers I know seem to be indifferent to cash. No, they do care about cash. How do I know? >They work on the most interesting project they can find that pays them enough to live. There. That's why. If they weren't making enough money to meet their needs, they'd be looking to trade up. Money isn't the only answer. Everyone likes to talk about how money isn't the solution. I'm pretty sure every one is ma…
Earlier quoted context omitted.
I'd imagine the incompetent ones wouldn't bother applying to jobs that are "way out of their league". If you are "sucky" you might still apply for a $60K job, thinking that you might slide through. But you wouldn't bother applying to a $100K job, thinking that there'd be way more competent people applying so it'd be a waste of time
You'd imagine that, but you'd be wrong - there are a great many technical employees who don't realize they are way out of their league and will apply anyway.
I suppose this refers to us (and our Will the real programmers please stand up post). If it doesn't, excuse our self-centeredness and kindly disregard this message. Our salary structure is designed to select for exactly the type of people we want to attract - the kinds of people that will go through walls to bend the world to their will, for some deeply ingrained reason unknown to anyone but them. For people like tha…
Which is exactly what I did. Freelance contract programming pays the bills (and is quite enjoyable) and I'm bootstrapping a startup on the side. It's not so much for the compensation as the challenge of something new and the independence to make my own decisions.
So at least in my case, it's not your fault. You can put the most attractive job offer out there and I won't bite. I'm wondering if there are a lot of programmers like me. That would certainly reduce the supply.
Earlier quoted context omitted.
The only difference is in the protectionism of the other professions. Most of the barriers you mention are imaginary. Programming errors can have far worse consequences than medicine or law. I've never seen a doctor or lawyer make a rocket ship turn into the ground (Arian V) or oil pipelines explode (buggy versions of pipeline software stolen by Russia) or make airplanes refuse to execute commands ( airbus and apache…
The examples you gave are edge cases and exceptions -- relatively very rare situations. Most programming work is hum-drum, with errors being no big deal, and easily and cheaply caught and caught early. I was comparing cases "in the main" between these 3 professions. Also, by pointing out the cases that you did, you actually increased the strength of the point I was making: these 3 professions are very different and o…
And if you fail to meet the high barriers to entry for doctors and lawyers, the likelihood that you'll make disastrous errors is pretty high.
I think you have it exactly backwards. The best programmers I know seem to be indifferent to cash. They work on the most interesting project they can find that pays them enough to live. Hiring people like that is really tough.
I was advising a startup recently about what tech stack to use. Their default notion was PHP-centric. I pointed at the advantages of other languages/stacks. I said that while it's generally true you can get the job done in a variety of languages and tech mixes (anything that's Turing complete, eh?) it's still very important to pick the right mix, because it impacts other things. One of the things I mentioned was that it effects not just the quantity of folks you'll find on the market with that skill set, but also the quality and really the kind of person.
For example, if I had to wade through 100 random resumes from strangers for a dev job I had to hire for, I'd get very different kinds of people if it were for say a PHP stack versus if it were a Java stack or a Lisp stack. Very different folks, on average. To be more explicit, I'm confident there would be way more applicants if it were PHP, but way better applicants, on average, if it were Lisp. (I did not literally recommend they go with Lisp (dev scarcity factor still a bit too strong for my tastes right now, though Clojure may change that), but I will say that it was not PHP.)