211–220 of 267 posts
Here in Hong Kong, thanks to special offers, 1000 Mbps broadband is only slightly more expensive than 30 Mbps, crazy! I collaborate on a project with a partner in India every day and the experience is quite smooth.
It'd be nice if remote working opportunities didn't come with national borders. The border-less nature of the Internet and knowledge-based work doesn't seem to require geographic location and yet due to complex logistical restrictions most of these job postings are US-only. Kind of a weird place to be. I wonder if there's some kind of hack that could allow small companies and startups to get around the policy issues…
It's not even governmental stuff; one of the sticking points we have is our payroll package, which doesn't support foreign places like "Wyoming", "other countries", and "Indiana." The same issue probably applies to our health insurance plan - it's only useful in the U.S. and would also be expensive to change.
In that scenario I wouldn't care if that was only available to in-country employees, the same way that I wouldn't care about missing out on perks like catered lunches.
Earlier quoted context omitted.
And here's another fine example: You love Macs, open source software and tools, and cringe when you hear the words .NET
They're advertising for a PHP/Ruby dev so making outlandish bullshit requirements like that, along with iMac fawning, is a must. Firms like this that dictate the technology stack you'll be forced to conform to are unemployable to any good developer.
This is a more general comment about job postings in general - Why are salary ranges so seldom listed. If you look at a lot of leading job boards even the company name isn't listed (recruiters). Isn't salary a basic piece of information that every job listing should have?
It's very hard to do for remote jobs. An appropriate salary is relative to the country you live in.
Earlier quoted context omitted.
Good points, but personally, I have never played along with the "We'll pay you just a bit more than what you are making right now". When the question "How much do you make right now?" comes up in an interview, I answer "How much I make right now is irrelevant, here is how much I want if I'll be working for you" (said with more tact, obviously).
As a hirer, I'll always ask what they make now. But I'll also ask are they happy with that salary. There's no point using it as a basis if they are not, but if they are, it's a good starting point.
Interesting that most of the backend jobs look to be for Rails. I wonder if there's a correlation between Ruby/Rails developers and a more liberal policy to remote working...or if it's just because Rails shops are much more likely to flock to a 37signals site.
Earlier quoted context omitted.
And you somehow doubt that to be true, or what is your point?
"better" is always subjective, and it's never even been close to my expectations. I don't think most people who've told me "oh, has gotten a lot better in the last year" even know what the problems are that keep some people away. I think it's largely PR parroting, and a way to seem marginally 'with it' re: linux. "hey yeah, I know ubuntu had some issues in the past, but you should really try it now - it's a lot bette…
Earlier quoted context omitted.
Linux desktop, CentOS, SuSE, Fedora, Ubuntu all have worked fine for me the past 15 years. I have fewer problems than when I have to do something on/with Windows. So either all my machines and all my experiences were really lucky or your post is an elegant troll.
nothing trolling about it. https://bbs.archlinux.org/viewtopic.php?id=120003 2011 people having problems with multiple apps trying to use audio at the same time. This is one of the things that drove me away from desktop linux in 2008. 3 years later it still isn't a solved problem. My gut tells me that in 2013, it's still not a solved problem. I've no doubt that some people get it to work for their use cases OK. But t…
What? Not at all? Not working when you unplug headphones? Not working for Flash?
Google for "osx sound problem" and you'll get plenty hits. What exactly do you think your link from 2011 demonstrates?
Earlier quoted context omitted.
As a hirer, I'll always ask what they make now. But I'll also ask are they happy with that salary. There's no point using it as a basis if they are not, but if they are, it's a good starting point.
During the last decade I changed several jobs. For each next job I managed to get 3-4x of my previous salary. I'm pretty sure it wouldn't happen if I had disclosed my previous salary.
I think you're doing more things right than just not mentioning your previous salary...