I’m on 12mb/s (which costs a fortune) for two remoties to share.
It’s fast enough to mostly not get in the way too much - you can schedule updates overnight etc. Occasionally bites pretty hard (eg having to fire up a vps and work via SSH to avoid pulling large files down locally). Video calls / screen sharing is limited (quite blurry for the most part).
honestly, as someone who has worked 100% remote for 7 years, I don’t mind slow or latent connections. in fact, I almost rather like them.
maybe it is because I grew up working in a terminal over dial-up with a 2000ms ping, but I don’t at all mind doing so today at 500ms, especially because bandwidth growth has outpaced codebase size growth. git can move diffs around so easily that working on a local copy is possible if terminal workflows aren’t your thing.
as a side benefit, building and testing apps on garbage networks is a fine way to ensure that they behave just fine for all users, not just those on fancy connections.
I have been exclusively working remotely for the past 12 years. I would never work differently in this industry ever again. Happy to answer any questions.
It was a necessity, I was living in a very small town in a very poor country with no IT industry to speak of and no plans to move at that time. Remote work was the only possible option at that point, and it worked well for me. In the meantime, I have moved from there, but remote working stuck with me.
I love this. I am in the lucky position that my company is almost fully remote. (There is a head office but only 2-3 people work from there, and that doesn’t include senior managers.) One disadvantage I can see that isn’t mentioned is that remote employees often have to be contractors / self-employed, which means more accounting overhead for employees than being an employee. Being paid in a currency other than the local one where you live also has problems, for example it makes it harder to get a mortgage here in the UK.
Wow you weren’t kidding, it is. Ironically it’s actually not the entire html body, it’s everything on the page after the main title. Weird.
Looking at the markdown page layout file in the repo, it looks like the committer thinks that you yield a variable, using a hash literal to provide a default. But according to the Middleman docs on front matter variables, you don’t do that, you use the current_page.data object. Amusingly the docs even use current_page.data.title as an example.
Well, not completely different, if remote means anywhere in the world, setting company-wide fixed working hours would be impractical. So the issues aren’t entirely orthogonal.
I’d say it completely depends on the job and the team. I work remotely with people all around north america and europe (mostly), and I appreciate knowing when someone will be online to answer a question or handle a request. I see no reason why a remotee shouldn’t be asked to work 9-5 if it’s needed for communication/productivity/other reasons. That is, to me, a different topic from physical location.
You certainly can have flexible hours without working remotely, but how many office bound staff have accsss to that office outside of say 6am till 8pm?
Love this! One little gripe though:
Gosh, I wish this were true! Significant parts of Massachusetts still don’t have high-speed internet, and I’m sure other states are the same way. https://www.wired.com/2016/04/why-western-mass-doesnt-have-the-internet/
I’m on 12mb/s (which costs a fortune) for two remoties to share.
It’s fast enough to mostly not get in the way too much - you can schedule updates overnight etc. Occasionally bites pretty hard (eg having to fire up a vps and work via SSH to avoid pulling large files down locally). Video calls / screen sharing is limited (quite blurry for the most part).
Sounds painful, but at least your employer seems understanding. Clever work with the vps/ssh btw :)
honestly, as someone who has worked 100% remote for 7 years, I don’t mind slow or latent connections. in fact, I almost rather like them.
maybe it is because I grew up working in a terminal over dial-up with a 2000ms ping, but I don’t at all mind doing so today at 500ms, especially because bandwidth growth has outpaced codebase size growth. git can move diffs around so easily that working on a local copy is possible if terminal workflows aren’t your thing.
as a side benefit, building and testing apps on garbage networks is a fine way to ensure that they behave just fine for all users, not just those on fancy connections.
I have been exclusively working remotely for the past 12 years. I would never work differently in this industry ever again. Happy to answer any questions.
can I ask how you got into remote working?
It was a necessity, I was living in a very small town in a very poor country with no IT industry to speak of and no plans to move at that time. Remote work was the only possible option at that point, and it worked well for me. In the meantime, I have moved from there, but remote working stuck with me.
I love this. I am in the lucky position that my company is almost fully remote. (There is a head office but only 2-3 people work from there, and that doesn’t include senior managers.) One disadvantage I can see that isn’t mentioned is that remote employees often have to be contractors / self-employed, which means more accounting overhead for employees than being an employee. Being paid in a currency other than the local one where you live also has problems, for example it makes it harder to get a mortgage here in the UK.
Is there a reason that the entire body of the site is set as the title? I’ve never seen that before.
Wow you weren’t kidding, it is. Ironically it’s actually not the entire html body, it’s everything on the page after the main title. Weird.
Looking at the markdown page layout file in the repo, it looks like the committer thinks that you
yielda variable, using a hash literal to provide a default. But according to the Middleman docs on front matter variables, you don’t do that, you use thecurrent_page.dataobject. Amusingly the docs even usecurrent_page.data.titleas an example.Edit: I made a merge request.
Working remotely and having flexible working hours seems like two completely different topics to me. I wouldn’t mix them up.
Well, not completely different, if remote means anywhere in the world, setting company-wide fixed working hours would be impractical. So the issues aren’t entirely orthogonal.
I’d say it completely depends on the job and the team. I work remotely with people all around north america and europe (mostly), and I appreciate knowing when someone will be online to answer a question or handle a request. I see no reason why a remotee shouldn’t be asked to work 9-5 if it’s needed for communication/productivity/other reasons. That is, to me, a different topic from physical location.
You certainly can have flexible hours without working remotely, but how many office bound staff have accsss to that office outside of say 6am till 8pm?
That being said, I’m all for it. These are generally good rules to follow even if you aren’t remote.
Yep, that’s exactly how it’s working out in Silicon Valley.