3 ms·
This is simple. It's Economics 101: Supply and Demand. 1. You work hard to improve yourself and gain more skills that people will want to hire you for. 2. Mor
by cocktailpeanuts 9y ago
This is simple. It's Economics 101: Supply and Demand.
1. You work hard to improve yourself and gain more skills that people will want to hire you for.
2. More people will want to hire you
3. Demand goes up, while supply (yourself) is fixed.
4. Your price goes up.
On the other hand, if you care so much about your "life quality" and put absolutely 0 effort to improve yourself outside of work,
1. You don't have much to show other than what you did at current work
2. You are making yourself completely dependent on the company
3. When the company fires you, you have NOTHING to show to others. It's not like you can show people the code you wrote while you were at the previous company (the company owns the code and you're not supposed to share it outside publicly)
4. Since you have nothing to share, less people will get your value and less people will want to hire you
5. Demand goes down, supply fixed.
6. Your price goes down.
You can keep bitching about how the world is unfair and harsh and write some blog post that sounds almost like a beautiful piece of poetry, but that won't change anything, because that's how the world works.
It's not about companies "exploiting" employees by telling the m to work on something during the weekends. It's actually for yourself. If you don't believe that, that's fine, but you will stay a shitty developer and the law of supply and demand will kick in.
- gfodor 9y agoYep, pretty much this. If the interviewer didn't think a person who had side projects was waiting in line behind you for the next interview slot, they wouldn't have passed. I tend to be skeptical of most forms of software engineering interview tactics, but work samples is not one of them. Strong side projects is a strong indicator of skill. FWIW, for those who do not have projects like the OP, its important IMHO to offer a take-home variety. If you do not have side projects, and are not willing to do a few hours of take home work, then I usually screen you out since there are plenty of other candidates that fit in either bucket and will be easier to make an informed hiring decision about. A strong work sample is an unnecessary but largely sufficient condition for assessing hands-on-keyboard coding skills (a subset of the skills needed to be a good software engineer), so screening out people who don't have them, when there is a glut of supply of skilled labor, as it might be in Austin, is a rational strategy.