3 ms·

In order: - 100% remote only - Flexible schedule (e.g., I can start at at 8am or at 10am. I can go and pick up the kids at 2pm from school. I have a dentist a

by dakiol 4y ago

In order: - 100% remote only - Flexible schedule (e.g., I can start at at 8am or at 10am. I can go and pick up the kids at 2pm from school. I have a dentist appointment tomorrow morning. Etc.) - salary. At least 15% more than what I’m making now - standard health insurance - vacation days. No BS (e.g., unlimited vacation), just plain usual number of vacation days (around 30 where I live) - people. I take a look at LinkedIn and check out the people who work there (experience, past companies, personal websites, Twitter profiles, etc.) - product. Is it actually something I don’t hate? - tech stack. Is it something I actually don’t hate? Would the stack make me more employable in the future? - no on-call. This is getting more difficult to be picky about with all this stupid movement “you build it you run it” - hardware. I hope I can choose the hardware Everything else (conference budgets, learning budgets, etc.) are nice to haves but I couldn’t care less.

crossroadsguy 4y ago
> no on-call. This is getting more difficult to be picky about with all this stupid movement “you build it you run it” A lot many times employees themselves shoot in their foot. They don’t stand their ground and say yes even to nighttime on-call. Are you in a first world country? Wherever you are — isn’t there any legal deterrent against this practice?
- ir123 4y ago
  Who do you expect to do the on-call for the software you write?
  - crossroadsguy 4y ago
    Don’t know, don’t care. That’s the most lame reasoning by the way. Because that means you rm-rf-*ing whatever the code I wrote the moment I walk out of your door, don’t you? So, it’s not my job to figure that out — unless you give me budget to hire. I work only in daytime. Hire someone else to do the nighttime work, or just hire someone else. Or hire a living or otherwise robot who can work round the clock.

by dakiol 4y ago

crossroadsguy 4y ago

> no on-call. This is getting more difficult to be picky about with all this stupid movement “you build it you run it” A lot many times employees themselves shoot in their foot. They don’t stand their ground and say yes even to nighttime on-call. Are you in a first world country? Wherever you are — isn’t there any legal deterrent against this practice?

ir123 4y ago
Who do you expect to do the on-call for the software you write?
- crossroadsguy 4y ago
  Don’t know, don’t care. That’s the most lame reasoning by the way. Because that means you rm-rf-*ing whatever the code I wrote the moment I walk out of your door, don’t you? So, it’s not my job to figure that out — unless you give me budget to hire. I work only in daytime. Hire someone else to do the nighttime work, or just hire someone else. Or hire a living or otherwise robot who can work round the clock.