21–30 of 231 posts
Earlier quoted context omitted.
You're not competing with your locality but with an entire country, or more. You need to stand out somehow.
How is this any different than a job at Big Tech in SF or NYC?
Earlier quoted context omitted.
I've remote worked for decades, and that isn't my experience. Video/screensharing meetings are far more productive in my experience, but only if everybody is using the tool. Its frustrating to hold an in-person meeting at the office, and try to add remote folks. The local ones shut out the 'voice on the phone' and start drawing on boards and paper and it breaks down. I spent 10 years in a company that had all meeting…
> start drawing on boards and paper Sounds like important brainstorming activities. How do you deal with this when you're remote?
While this is no doubt great I don't really believe a statement "But most importantly, Frein said, it helps InVision build a better product". Under what metric? I don't believe that people who are forced to cooperate with video and screen sharing options can deliver a better product than these, who can walk up to a colleague and ask them in person or use a whiteboard to explain their problem. In the end, remote worke…
I underestimated how high the competition is for remote work. All my attempts failed so far despite having well customized application materials. I didn't submit to hundreds maybe around 20. Most of the time I never even reached a technical test at these companies which I thought would be the hardest part.
I think the way to get a remote job is to start with a non-remote job and slowly convert it to remote. Haven't pulled it off successfully yet but it seems like a much easier path, so long as you're willing to put in the time.
My biggest "issue" with remote working is always when there are differing amounts of remote work within teams.
When you have half the engineers in office, and half remote, the 2 sides end up with communication issues. In-office meetings where a few are remoted in are awful unless the company spends the money on a real remote-conference setup, having co-workers that don't like to pick up the phone and call the remote guy ends up keeping remote workers away from the problems.
I will never work at a remote company that isn't actively working on maintaining a remote workforce. Because even though I absolutely love remote work, it's not easy, even for those that are heavily invested in it.
While this is no doubt great I don't really believe a statement "But most importantly, Frein said, it helps InVision build a better product". Under what metric? I don't believe that people who are forced to cooperate with video and screen sharing options can deliver a better product than these, who can walk up to a colleague and ask them in person or use a whiteboard to explain their problem. In the end, remote worke…
https://blog.aha.io/remote-workers-vs-office-workers/
Notable bits:
> People get more done when they have autonomy
> the office is filled with distractions. This is especially true for those who are in an open-office space, where they are 15 percent less productive, have more trouble concentrating, and are not too pleased with their sound privacy.
> People are often surprised to learn that remote workers are actually more engaged than in-office counterparts. [0]
> Perhaps the greatest benefit of remote work is that it makes the way for sustainable happiness — giving people the chance to pursue their passions both in work and in life
And this is not said in the article, but happy people produce better work.
Also, there are more sources in the blog post.
We've written a lot about it, if you want to read more: https://blog.aha.io/?s=remote
Found it interesting, and likely a very good idea, that they have set ‘office hours’ which are the same for everyone globally. That might be very inconvenient if you’re in a locale where you wind up working nights, but it does give a level of predictability and ensures that everyone is available at a given time.
I suppose if that ever becomes an issue they could settle on two or three time zones to try and accommodate almost everyone. It can be inconvenient but it can also sometimes be efficient for tasks that lend themselves to working in "shifts". Like you develop your software, you send a version for testing, you go home, you return next morning and people on the other side of the globe have had time to test it and give some feedback.
Of course it can also easily lead to a huge waste of time if you're stuck and you need some feedback from people who won't be available until late in the afternoon in your timezone. It definitely requires very good logistics and planning.
While this is no doubt great I don't really believe a statement "But most importantly, Frein said, it helps InVision build a better product". Under what metric? I don't believe that people who are forced to cooperate with video and screen sharing options can deliver a better product than these, who can walk up to a colleague and ask them in person or use a whiteboard to explain their problem. In the end, remote worke…
[meta] Hey, all of HN? I'll risk a bit of karma on this question: Why are any of you downvoting klohto's comment? klohto's requesting specific information and providing one's own impression of (or perhaps anecdotal experience in) a remote environment. I can't think of a single good reason to downvote, and it's really irritating seeing good discourse being suppressed in this manner. [/meta] As for the question about r…
That line couldn't be more wrong based on my own experience. Perhaps the downvote was because it read like an assertion of an obvious fact when it was just a guess?
I moved from the software sales industry to waiting tables in a rural area. I have a 10 minute commute by car or moped, I breathe fresh air, and I make enough money to support myself. My colleagues are my friends and my boss has never once slighted me on anything. There is something to be said about the perks of working remotely, but for once it is nice to work in a supportive, engaging environment that is close to m…