Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In terms of not working or splitting to multiple jobs. Then that's a performance issue. If you're getting expected work done, it's not a problem... If you aren't, then you're a problem either way. This is not me condoning the practice, only pointing out that it shouldn't be the crux of the problem.

Depending on the job, you won't be on all the time. I have about 2-3 days a week where I'm on and pretty hyper productive and 1-2 where I'm kind of coasting or spending more thinking/learning/reading time.

I do find, I prefer office culture to working remotely... it's much more productive and team cohesion is often much, much better. International work is much harder still to coordinate. Right now I'm working on an East coast team, living in AZ... I'm about to have to start getting up yet another hour earlier next week, and so not a morning person. That said, given the market shifts really remind me of around 2001, and I'm holding on where I am for as long as I can and generally like the people I work with.

Mandatory office presence cuts both ways, you're less likely to gain top talent and even then, you're going to pay above relative market rates for it if you do. I've seen companies try to pay relative to cost of living for developers in different locations, and to me that just doesn't work either. Splitting the difference between top locations and local relative cost of living seems to be the trend, and I'm frankly happy to see it.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: