4 ms·

It actually does look pretty good, until you realize he doesn't list any real previous job experience anywhere.

pekk 12y ago
Which is the worst, unforgivable sin (even worse than being old). It doesn't matter what you have done, if there is no corporation to witness to your ability and you do not have a fresh face. Hence "entry-level" positions requiring 5 years of experience, and yet you are unemployable forever if you don't have a job within 5 years of graduating. It might as well be law.
- bentcorner 12y ago
  Is having corporate experience really that much better though? I mean, obviously working for someone for several years implies some level of competence, but your work is nearly always locked away and you can't show it off. Ideally you'd want someone who does both; working for someone, which demonstrates the ability to work on a team, while also contributing to open source and making their own content, upon which you can grade their technical skills. As someone who has worked in the corporate world since graduation, I feel I have little to show that is concrete. It's all hearsay. I feel I'd be better off if I spent time developing myself outside of work hours so that I can have something visible to the world to be proud of, but frankly with a family to take care of it's a struggle to get the energy to do that. I'd like to have my cake and eat it too. It's a little depressing to me, honestly, but it is what it is.
  - drivingmenuts 12y ago
    Long-term corporate employment is more valuable if you're seeking corporate employment. Only a few corporations (relatively speaking) place any value on open-source project association.
  - sanxiyn 12y ago
    Practically speaking, yes, having corporate experience is much better. After leaving the school (I didn't graduate), I spent 2 years doing self-directed learning about computing. I have commit access to PyPy and LLVM, am credited in release notes of Mono and IronPython, and hundreds of open source commits to show off. I still had a lot of trouble landing a job. I got lucky in the end, but it was rough. You seem to overestimate how open source contributions are judged in job search. Corporate experience is not hearsay; it is concrete. Open source contributions are not concrete, because most employers do not know how to evaluate them.
    - berdario 12y ago
      I have had mostly the same experience. On the plus side: a lot of companies care about Open Source experience and are able to evaluate it. On the down side: companies who do it are still the minority, and you'll get a lot of competition from similar folks, who'll likely have written even more open source code than you did, and if they have had a real paid-for work experience will probably be preferred
  - base698 12y ago
    > Is having corporate experience really that much better though? Yes, a thousand times yes. At a minimum it gives you insight into some product/set of products that are commercially viable and people use. You get experience with at least one build system, and code architecture someone took to market. It also gives you a paycheck that frees up worries about food and housing. In the least demanding of these jobs you can use the down time to learn other technologies by building a MVP of the current product in another technology or contributing to open source projects your corporate job uses. The insight gained from one "real job" is a million times more helpful than trolling github and trying to figure out what a given project is used for in the real world.
    - leoc 12y ago
      It also gives some assurance that you won't be unmanageable in a working-for-hire context, or a HR problem child in other ways.
- leoc 12y ago
  Apparently one reason that Valve did do well for themselves was that they were something like the first to seek out and hire modders rather than just new grads and gaming-industry made men. Naturally they were looking for the best, most accomplished modders but at the time they had their pick of them.

pekk 12y ago

Which is the worst, unforgivable sin (even worse than being old). It doesn't matter what you have done, if there is no corporation to witness to your ability and you do not have a fresh face. Hence "entry-level" positions requiring 5 years of experience, and yet you are unemployable forever if you don't have a job within 5 years of graduating. It might as well be law.

bentcorner 12y ago
Is having corporate experience really that much better though? I mean, obviously working for someone for several years implies some level of competence, but your work is nearly always locked away and you can't show it off. Ideally you'd want someone who does both; working for someone, which demonstrates the ability to work on a team, while also contributing to open source and making their own content, upon which you can grade their technical skills. As someone who has worked in the corporate world since graduation, I feel I have little to show that is concrete. It's all hearsay. I feel I'd be better off if I spent time developing myself outside of work hours so that I can have something visible to the world to be proud of, but frankly with a family to take care of it's a struggle to get the energy to do that. I'd like to have my cake and eat it too. It's a little depressing to me, honestly, but it is what it is.
- drivingmenuts 12y ago
  Long-term corporate employment is more valuable if you're seeking corporate employment. Only a few corporations (relatively speaking) place any value on open-source project association.
- sanxiyn 12y ago
  Practically speaking, yes, having corporate experience is much better. After leaving the school (I didn't graduate), I spent 2 years doing self-directed learning about computing. I have commit access to PyPy and LLVM, am credited in release notes of Mono and IronPython, and hundreds of open source commits to show off. I still had a lot of trouble landing a job. I got lucky in the end, but it was rough. You seem to overestimate how open source contributions are judged in job search. Corporate experience is not hearsay; it is concrete. Open source contributions are not concrete, because most employers do not know how to evaluate them.
  - berdario 12y ago
    I have had mostly the same experience. On the plus side: a lot of companies care about Open Source experience and are able to evaluate it. On the down side: companies who do it are still the minority, and you'll get a lot of competition from similar folks, who'll likely have written even more open source code than you did, and if they have had a real paid-for work experience will probably be preferred
- base698 12y ago
  > Is having corporate experience really that much better though? Yes, a thousand times yes. At a minimum it gives you insight into some product/set of products that are commercially viable and people use. You get experience with at least one build system, and code architecture someone took to market. It also gives you a paycheck that frees up worries about food and housing. In the least demanding of these jobs you can use the down time to learn other technologies by building a MVP of the current product in another technology or contributing to open source projects your corporate job uses. The insight gained from one "real job" is a million times more helpful than trolling github and trying to figure out what a given project is used for in the real world.
  - leoc 12y ago
    It also gives some assurance that you won't be unmanageable in a working-for-hire context, or a HR problem child in other ways.
leoc 12y ago
Apparently one reason that Valve did do well for themselves was that they were something like the first to seek out and hire modders rather than just new grads and gaming-industry made men. Naturally they were looking for the best, most accomplished modders but at the time they had their pick of them.