4 ms·
I wouldn't say it's an "Anti .NET" bias, as much as it's an "anti too many years in the same exact thing" bias. 1. Choose a different language for your next si
by dkopi 11y ago
I wouldn't say it's an "Anti .NET" bias, as much as it's an "anti too many years in the same exact thing" bias.
1. Choose a different language for your next side project.
2. Step in the door with C#, try to help out on projects or change positions inside the company.
3. Attend hackathons, contribute to opensource projects.
A good programmer can quickly feel comfortable in any programming language. Recruiters feel more comfortable when you can actually show proof of that.
- UK-AL 11y agoChanging stack usually involves a decrease in salary.
- dkopi 11y agoOptimizing for the short term may not give the best results in the long term.
- UK-AL 11y agoI would say most companies pay more for specialists, then someone who knows a little bit about everything. I personally know many languages a little bit, but I find writing my CV to target a specific stack results in a better responsive.
- pingec 11y agoI have side projects in JS and TS (Node.js), Python, C (~500 loc projects). Mostly I care about solving a specific problem. Learning a new stack just so I can put it on my resume would require time I don`t have :(.
- anton_gogolev 11y ago> "anti too many years in the same exact thing" As an opposite to what, exactly? > A good programmer can quickly feel comfortable in any programming language. This is not true. It takes a not-insignificant amount of time to just learn to write idiomatic code, let alone making oneself familiar with all the quirks and idiosyncrasies of libraries and frameworks.
- Jach 11y agoAdditionally if it's your first exposure to a non-Algol language, you're going to have a hard time... you definitely won't feel comfortable quickly. But at least going from, say, Java to Python, you can quickly feel fairly comfortable writing Python code just like you would Java! (Your coworkers who understand "Pythonic" might hate you though.)
- bitwize 11y agoIf you don't have 3-5 years experience in language/framework X, no jobs in language/framework X will be forthcoming. People hire based on what you know, not your ability to learn. A new hire who can "hit the ground running" is an asset; one who can't is a liability.
- chucksmash 11y agoThis varies from place to place. My first company (as a non-programmer) was very much like this. It was very corporate and they weren't willing to take a risk on cross training a hobbyist without the requisite boxes checked on a resume. It was frustrating but I also understand the CYA logic behind it. There's someone willing to take a risk on you somewhere for some amount of money. Having a github with noob code in the language you are trying to get hired for helps. If you are just starting out, being able to show you want it bad enough to learn it off the clock is a strong signal vs "I'll start learning it if you start paying me" (which is...also a signal).
- jghn 11y agoid rather the person who will be overall better once they ramp up instead of worrying about hitting the ground running.
- ljw1001 11y agoI don't mean to be hurtful, but you sound like you've exactly the same biases the original post is about, and you're rationalizing. Seriously, not all good hackers fit any cookie-cutter definition of a hacker.