6 ms·
One option: Word of your skill travels at approximately the speed of beer. (i.e. Try traditional networking.) You can also have a web presence about the work
by patio11 15y ago
One option: Word of your skill travels at approximately the speed of beer. (i.e. Try traditional networking.)
You can also have a web presence about the work which does not actually include the work. Talk about an interesting sub-problem which is non-proprietary. Talk about architecture choices. Talk about the tech you used and the problems you overcame while using it. Write about how firms in the financial industry are missing opportunities to throw Java at problems and make heaps of money.
- jiggy2011 15y agoI imagine a lot of employers wouldn't really like you discussing stuff you had done for them in any great detail on the public internet, even discussing design / architecture decisions might be controversial (or covered by an NDA). Plus if your employer finds what you wrote you better need a justification for putting it up there that isn't "so I can apply for this job". You don't really want to end up in legal trouble or fired. At this point anyway your "web presence" is pretty much just going to be your resume but put online, I imagine if they explicitly don't want resumes they wouldn't want that either.
- patio11 15y agoThe line I used in my past life as an enterprise Java developer was that Internet participation was a necessary part of my professional development, enhancing my future value to the company without them needing to spend money on expensive training or conferences. Plus it gives me a chance to learn about some of that web stuff that your IT magazine is always talking about, boss. Imagine the TPS reports I could implement with that! (It worked. Japanese megacorps: secret hippies, I tell you.) More broadly: fear, weakness, and lack of creativity in the face of constraint are not career-enhancing attributes. (That's not personal. Many engineers need to hear it, including me, both in the past and occasionally in the present.)
- cube13 15y agoWhy should I have to do that, outside of work, in order to get another job? I'm happy with my current work, and that means that I'm not trying to go out of my way to find additional projects on the side. I have hobbies I'd rather be doing outside of work that don't involve computers. I don't feel that it should be necessary to prove to any potential employer that I'm working outside of work.
- patio11 15y agoIt's not necessary. Exercise isn't necessary, either. It's a good idea for almost everybody, and even if you dislike the activity doing it probably improves outcomes for things you actually do like, but no one will force you to do it.
- jiggy2011 15y agoThe problem is I think that it puts some people at a much bigger advantage over others. A 20something who works at a funky startup and writes for their corporate blog and gets paid to spend 20% of his time contributing to the rails codebase or something. vs somebody older (or maybe not) who works 60+ hours a week in a corporate (possibly non IT) organization which has strict corporate blogging policies (i.e don't blog about work) and has a family to look after. I can see a lot of crap getting thrown up and github and mediocre blog entries written prior to interviews. I think this article sums it up fairly well: http://teddziuba.com/2009/10/i-dont-code-in-my-free-time.html http://teddziuba.com/2009/10/i-dont-code-in-my-free-time.htm...
- cube13 15y agoThat's exactly where I am right now. Like I said, I get enough satisfaction on an intellectual and professional level from my job that I don't feel the need to find side projects. I'll do what it takes to get done with my job, working as many hours as I need to. But I simply don't feel the need to code outside of working hours. On weekends, I'd rather be out fly fishing or playing video games.
- dpritchett 15y agoThis is a sales problem. You can have the best product in the world and you still won't get the customers you want without a solid pitch and some networking. Ted's post about not favoring github et al in applicant screening is one thing, but an aspiring employee who chooses to forego some easy and visible self-promotion has only himself to blame when he doesn't get the same opportunities as someone willing to meet hiring companies at their point of need. To hire someone you have to find them, vet them, and entice them with the right deal. People who make themselves easier to find and to vet are going to get better deals on average.