News for hackers. Stuff that matters.
Re:Remote Only by nvarsj on Thursday June 07, 2018 @06:13AM (#17254605)
My somewhat reductive conclusion about remote work is that it boils down to the ability to be an effective writer.

If you're not good at written communication, or you work with people who are not good at it, remote work will be miserable.

People who are not highly fluent in the company's written language or those with some level of dyslexia will struggle. Also some people get frustrated with the more analytic approach required by text, relying instead on spoken rhetoric.

I think even if you're colocated, there are huge benefits to following the remote work practices and improving your written communication. Documenting your work in an issue manager and using chat primarily for communication means no one will miss out, even if someone is sick, a new starter, or on a different team. All these things can make a dev organisation much more effective and break down silos.

Re:Remote Only by linsomniac on Thursday June 07, 2018 @11:24AM (#17256599)
This does ring true. Years ago when I was running a remote-primary shop we hired this one guy that just struggled. I spent the next year trying to get him on track and one of the big issues was his writing was terrible; both internally and with our customers.

Right before we finally gave up, I went back and looked at all his interview communications. As part of the interview we would exchange several e-mails to see how their communication was, because we lived and died by e-mail with clients. All those communications were totally on point.

So I asked him: Why were your e-mails before we hired you so good? "Oh, my wife wrote those for me." So I'm sitting there thinking "We should have hired your wife."

Re:Remote Only by dennisgorelik on Friday June 08, 2018 @12:02PM (#17266744)
Why didn't you hire his wife when you learned that she wrote these emails?
Re:Remote Only by linsomniac on Friday June 08, 2018 @11:19PM (#17271329)
Weeeeell... She didn't apply... :-)
Re:Remote Only by pricees on Thursday June 07, 2018 @09:48AM (#17255696)
This has been my experience, 100%.

All of the jobs I have ever interviewed for casually listed "great oral and written communication" as a skill in the job reqs. I have felt that I had a problem in this area.

I have worked as a remote contractor off and on for most of my life and have never run into an issue.

For the past year and a half I have been on a remote team.

It wasn't until my team lead, who did all of the oral and written communication, left, this past month, that I was placed in the position to pick where he left off.

It became immediately evident how poor my skills are in this area. I know that I am a poor communicator, but I didn't realize just how insufficient I was. Not only grammar and spelling, but conveying complex subject matter in a succinct way for folks lacking detailed domain knowledge. This is a problem!

Regardless, there is hope. How do you get better at writing? Write more. At least that is what I am told. I am now chomping at the bit for long-form writing opportunities to get experiencing it putting thoughts and plans on paper, as well as, using a new SaaS app to commit/tracking writing 5 minutes a day.

Any and all tips are welcome.

Re:Remote Only by specialist on Thursday June 07, 2018 @10:19AM (#17255918)
1) I don't believe you. You're a fine writer.

2) Writers write. So write more. The only actionable advice I ever got.

I used to devour howtos like Bugs In Writing. https://www.goodreads.com/book/show/601222.Bugs_in_Writing

Once I felt confident that I'm saying what I meant to say, I think I stopped. I should probably revisit the classics for a refresher.

3) Simple is harder. Explaining complex stuff is a ninja power. Just keep at it.

4 bonus tip) Proofread, edit stuff you wrote 3, 6, 9 months ago. Consciously note how your writing skill and voice have changed.

Re:Remote Only by dredmorbius on Thursday June 07, 2018 @12:18PM (#17257235)
Write more, but get feedback.

Unselected, ungoverned, training, can simply reinforce bad habits.

Re:Remote Only by wyclif on Thursday June 07, 2018 @10:24PM (#17262073)
If your spelling is poor, make an effort to improve. But don't wait for that to happen. Start composing your email in Google Docs or the word processor of your choice with spellcheck turned on. It is worth the extra step of copy pasting your emails in order to get spelling and grammar right.
Re:Remote Only by dredmorbius on Friday June 08, 2018 @12:24PM (#17266979)
Spelling's one of the least problems with writing.

Structure, meaning, flow, logic, and engaging the reader the most difficult.

Logic and rhetoric over grammar.

Re:Remote Only by ahtu123 on Friday June 08, 2018 @03:11PM (#17268747)
I was never that good at writing but just putting some effort and caring about what you write down makes a huge difference. After you write an email or a document, read through the whole thing and edit. Is it obvious what I want to happen? Do I sound like a dick? The biggest improvement for me was to give more concrete answers. Like when someone asks you for a meeting, don't just say "yeah any time's fine", actually give a few dates and times that work for you. It also cuts down on the annoying back and forth of scheduling via email.
Re:Remote Only by pricees on Thursday June 07, 2018 @10:22AM (#17255961)
This is great. Thank you.
Re:Remote Only by kharak on Thursday June 07, 2018 @09:51AM (#17255719)
I'm mildly confused. Your post here seems fine and quit readable. How do you arrive at the conclusion, that you're lacking in written communication skills?

(sorry for question instead of tips)

Re:Remote Only by scarecrowbob on Thursday June 07, 2018 @10:23AM (#17255968)
In a sense, your confusion here -is- the problem:

"conveying complex subject matter in a succinct way for folks lacking detailed domain knowledge."

FWIW, I didn't have the same confusion about the post, so I don't know how lacking the author is in this specific setting.

But I have had the same general struggle.

I have an MA in English/rhetoric and am a software dev, and even with that nexus of training it has been a lot of work to get better at communicating... the struggle to communicate technical issues to non technical people is a lifelong journey with a complex path. It's just hard.

So here's my tip:

smaller sentences. More paragraphs. Simpler language.

And IME we do best when we develop a continual awareness that although communication is difficult, it is possible.

Re:Remote Only by aeorgnoieang on Thursday June 07, 2018 @01:15PM (#17257913)
> So here's my tip: > > smaller sentences. More paragraphs. Simpler language.

I've also found thinking about sensual clues to be helpful, e.g. what would the user/customer/whatever see (or hear or feel) at this point? What (exact) text would they reasonably anchor on based on everything they might see? I also try to visually distinguish different types of info, e.g. exact text of some kind of UI element, code.

Another really helpful tip is to confirm that the user/customer/whatever sees/hears/feels some (exact) specific thing at a specific { step / point in space-time }. If they don't provide the (near) exact response I expect, I try to notice my confusion and debug right then and there until my confusion is resolved.

Re:Remote Only by scarecrowbob on Thursday June 07, 2018 @02:07PM (#17258497)
This is useful advice.

If you abstract it, the general form is something like "work with concepts that your audience is already familiar with", which is good advice for any communication. And, similarly, be on the look out for any data that says your communication has started to go awry.

Re:Remote Only by Fnoord on Thursday June 07, 2018 @10:39AM (#17256109)
Sample size is one, and they might've discussed this before. Someone with good written communication skills can write effectively, without too much details, quickly on the fly. The same holds true for verbal.

I believe there's two important key points: confidence (but not overconfidence) and empathy/sympathy. Putting yourself in the other person's shoe and figuring what they need to hear ie. not what you want to express. The latter is secondary!

Sure, you can practice it, but only so much. I have autism, and I'm utter shit at this (even in my native language). I've been practicing it pretty much all my life (I remember having issues with it at elementary school). I'm terrible with being to the point and keeping communication short. And if it is short, its usually too rude.

Re:Remote Only by dagurp on Thursday June 07, 2018 @10:10AM (#17255844)
Maybe it took a long time to write that post. That's what I struggle with anyway.
Re:Remote Only by specialist on Thursday June 07, 2018 @10:22AM (#17255949)
"I would have written a shorter letter, but I did not have the time." -- Blaise Pascal

I encourage you to not criticize yourself too harshly.

Re:Remote Only by pricees on Thursday June 07, 2018 @10:20AM (#17255927)
I reread it a few times. I reread it aloud. This is a new discipline.
Re:Remote Only by NoNotTheDuo on Thursday June 07, 2018 @09:54AM (#17255747)
May be evidence that the additional training/work s/he's put in is paying off. I agree that the post does not show a lack of written communication skills.
Re:Remote Only by ed_balls on Thursday June 07, 2018 @10:40AM (#17256123)
Re:Remote Only by pitaj on Friday June 08, 2018 @05:10PM (#17269706)
One good to practice is to think of something that really bothers you: traffic, politics, your in-laws, whatever. Then write a blog post explaining why it makes you angry, and giving ways to fix it.
Re:Remote Only by chrisweekly on Monday June 11, 2018 @10:39PM (#17290296)
Don't just write more! Also read more! :)
Re:Remote Only by AYBABTME on Thursday June 07, 2018 @07:51AM (#17254970)
People say that, yet in my experience it's not actually true. We just need to communicate enough to coordinate. I'm not a great communicator, I don't think most people at my work are great communicators, yet we work just fine as a remote company. I feel people exaggerate this belief.

Regular chatter in public chat channels seems sufficient. What really seems to matter is work ethics.

Re:Remote Only by passiveincomelg on Thursday June 07, 2018 @08:34AM (#17255186)
Maybe the bar is lower than you think. As your comment demonstrates, you are able to form complete sentences that are either correct in terms of spelling and grammar, or so close that I can't tell the difference.

I don't know where exactly the bar is, but a sentence is certainly below it if I can't figure out whether someone told me they did X or they are asking me to do X.

Re:Remote Only by jvannistelrooy on Thursday June 07, 2018 @08:43AM (#17255239)
I think it also makes a difference if you work with people across different timezones or not.

Regular chatter might be good enough to communicate between people in roughly the same timezone. However, If I send an unclear chat (or email) to a colleague who's starting her day when mine has already ended, she can't act on my message and we'll have to waste another day clearing up that miscommunication.

Re:Remote Only by psyc on Thursday June 07, 2018 @11:36AM (#17256749)
I’m on my second remote job, and I find all HN threads on the subject contain this bizarre exaggeration about how different it is, and how you need to be a certain kind of person, and have stellar communication skills. I feel like it’s the same as people warning others off living in Seattle - i.e. gate keeping.

And how are these hypothetical poor communicators performing at non-remote jobs, anyway?

Re:Remote Only by nvarsj on Friday June 08, 2018 @06:42AM (#17264143)
I don't think you have to be an experienced essayist or something. If you can read HN and make comments I think you've probably met the bar. I've worked with people who really struggle to convey or understand technical discussions in text, such that I usually had to talk with them face to face to communicate anything non trivial.
Re:Remote Only by collyw on Thursday June 07, 2018 @09:36AM (#17255613)
I don't work remotely as such, but usually with distributed teams. Personally I find skype chats or similar the best way. Writing emails is quite a long winded way to get to where you want and takes me a while. Chats are more two way so you can judge where the other person is with understanding the problem, and has the benefit of being written down for future reference.
Re:Remote Only by beat on Thursday June 07, 2018 @10:58AM (#17256293)
Yeah, I find Skype or Slack or some other form of IM to be absolutely invaluable in making remote work effective. But it's also semi-synchronous and interruptive, relative to email.
Re:Remote Only by pavel_lishin on Thursday June 07, 2018 @09:50AM (#17255711)
> Regular chatter in public chat channels seems sufficient.

That means your teammates' communication skills are sufficient! Congratulations.

> What really seems to matter is work ethics.

I disagree. Work ethics mean nothing if you don't understand the work that needs to be done, because the problem or the approach is not communicated clearly.

Re:Remote Only by minipci1321 on Thursday June 07, 2018 @06:20AM (#17254628)
> it boils down to the ability to be an effective writer.

effective reader too. One should be able to quickly make sense out of several hunbdreds of email messages, otherwise it will end up in "synchronous mode" -- dozen of messaging windows opened at every moment.

Re:Remote Only by amorphous on Thursday June 07, 2018 @06:42AM (#17254708)
so true.

I have a business partner that I can talk to very effective in person. I had to relocate, and now we have to deal mostly via email. I have been working remotely for ten years now and saw no problem with the change. But it has become disastrous. I figured out that he is just not an "email type". Only picking up the phone works with him, but this does not fit into my workflow. I'm undoing our business partnership currently.

Re:Remote Only by throwawaymath on Thursday June 07, 2018 @07:28AM (#17254869)
Why doesn't picking up a phone fit into your workflow?
Re:Remote Only by jasode on Thursday June 07, 2018 @09:15AM (#17255452)
For many, a ringing phone is much more disruptive than an email notification.

Picking up a phone for voice calls is synchronous.

Responding to an email is asynchronous.

(The asynchronous advantage is probably why SMS texting & WhatsApp/FB messaging has overtaken voice calls.)

I had a friend that didn't use email and always called my phone. Whenever I shut off the ringer, he'd eventually send me an email. But the content of that email was always, "Hey I got no answer on your phone. Give me a call."

Argh!!! Why can't you just put your question directly into the email?!? My behavior of not answering his phone calls failed to "train" him to switch to the email mode of communication. It drove me crazy. I finally realized that some people in this world have brains that work better with voice calls. Unfortunately, that's incompatible with the way I like to work.

Re:Remote Only by mandelbrotwurst on Thursday June 07, 2018 @11:18AM (#17256539)
Phrasing a question in a way that ensure it will be understood by the reader is non-trivial. For tricky problems that might require several steps of back and forth, the ability to ask clarifying questions and access tone of voice that you get on a voice call is valuable.

I'm not saying that this guy was thinking this through that extensively, but IMO there are times when a voice call is more effective.

Did you attempt to explain to him why you didn't answer the phone as opposed to trying to "train" him? i.e. engage in open communication and have a conversation about what works and what doesn't for each of you about various modes of communication.

His request for you to "give him a call" moves thing for you back into the realm of the asynchronous.

I wonder whether maybe you have some other issue with voice calls?

Re:Remote Only by jasode on Thursday June 07, 2018 @11:52AM (#17256954)
>, the ability to ask clarifying questions and access tone of voice that you get on a voice call is valuable. [...], but IMO there are times when a voice call is more effective.

I agree that voice calls can sometimes be more effective. Some types of tech support debugging are much easier with the interaction of live phone calls.

Those weren't the type of calls my friend was making. His calls were banal questions like, "I'm looking at these cameras the Canon 10D and Nikon D70. Which do you think is better?" He could have just typed that question into an email for me to reply whenever it was convenient. Instead, I hold the phone to my ear while I'm googling "Canon 10D vs Nikon D70".

>Did you attempt to explain to him why you didn't answer the phone as opposed to trying to "train" him?

No, I never told him in blunt terms, "don't call me anymore unless it's a complex question that requires the advantages of voice communication." I was hoping that dropping a ton of hints would do it but it didn't work. In any case, I changed my number so it's no longer a problem.

>His request for you to "give him a call" moves thing for you back into the realm of the asynchronous.

Not really because what ends up happening is after I call back, his brain says, "jasode is available now" and he'll call 5 or 15 minutes later with a new question. His threshold for initiating phone calls was very low which put me back in synchronous hell.

>I wonder whether maybe you have some other issue with voice calls?

Well yes, as I mentioned earlier: it's not my preferred form of communication. I do acknowledge and respect the fact that others default to voice but that doesn't change the fact that it's incompatible with how my brain works.

There is clearly a disconnect between people who prefer different modes of communication since the gp poster (throwawaymath) seemed truly confused and therefore asked, "Why doesn't picking up a phone fit into your workflow?"

Re:Remote Only by mandelbrotwurst on Thursday June 07, 2018 @10:39PM (#17262152)
Gotcha. Thanks for breaking that down. It's definitely frustrating when people don't consider the impact/costs of the requests that they are making.
Re:Remote Only by amorphous on Thursday June 07, 2018 @08:59AM (#17255351)
_Always_ picking up the phone doesn't fit into my workflow. Some things are better discussed via email or chat. I think it is very difficult to work remotely if you only have direct verbal communication available.
Re:Remote Only by satsuma on Thursday June 07, 2018 @09:16AM (#17255463)
sort of tangental, but i wonder how a drop in/drop out system like teamspeak/vent/discord/etc. would work in a professional setting. you have direct calls still, but if you just want to be available to coordinate through voice you could. similar to leaving your door open and letting people stop by.
Re:Remote Only by pbhjpbhj on Thursday June 07, 2018 @11:22AM (#17256579)
Keeping an open channel on Teamspeak could be compared to having a person sitting at the next desk.
Re:Remote Only by collyw on Thursday June 07, 2018 @09:32AM (#17255586)
> If you're not good at written communication, or you work with people who are not good at it, remote work will be miserable.

I had a pretty poor team leader a few years ago with a bums in seat type job. He would never write anything down and teh result was quite frustrating. The spec used to change frequenty and he would come and verbally tell me it. then he would change it again, then again. A week or two later when I actually got around to implementing teh said feature I would ask him what he wanted done,

"I thought we talked about that." "Yes we did but you changed your mind 4 times and I can't remember what the conclusion was."

I used to regularly ask him to put things in writing, but he was usually to lazy to deliver on that.

So I don't think these problems are unique to remote teams.

Re:Remote Only by specialist on Thursday June 07, 2018 @10:08AM (#17255834)
One species of gatekeeper (control freak) won't write things down.

Another insists that if it's not documented, it didn't happen.

These challenges have confounded me all my working life.

My few truly positive working experiences happened when there was mutual trust, regard, esteem. First time it happened, I was gobsmacked. I'd read about trust, but had never seen it IRL. It was a never ending warm fuzzy bath of shared awesomeness.

I still have few ideas how to find, nurture, create trust (especially in a chaotic env). But I now know it when I see it. And when I'm not feeling it, I mostly just go thru the 9-5 motions, keeping my expectations and investments lower.

Re:Remote Only by nkjoep on Saturday June 09, 2018 @06:08AM (#17272305)
TBH, I think was somehow your fault. Before writing even a single line of code I make sure that "I" understood what is needed.

Then, if nothing is written down anywhere, I'd just sum up what I am going to implement (email, wiki, internal docs, readme whatever) and send it to anyone involved.

Check mate for for control-freak-undecided-colleagues. :)

Re:Remote Only by newscracker on Thursday June 07, 2018 @08:55AM (#17255332)
I agree that writing well is important, but I would characterize this as beyond writing alone. Assuming that "remote work" isn't confined only to teams in time zones where working hours don't overlap, it's quite easy to start a chat or an audio call/conference. "Talking" directly is more important, and many a times yields quicker results than exchanging long emails or documents, whether it's with text (chat) or voice or even video calls. But it does come at the cost of trying to setup a mutually convenient time and being available (synchronous vs. asynchronous).
Re:Remote Only by pavel_lishin on Thursday June 07, 2018 @09:05AM (#17255380)
> it's quite easy to start a chat or an audio call/conference

"Ok, we're all here. Wait, where's Mike?"

"I think he was making coffee. Let's wait for him."

"Hey, is Zhang saying something?"

"Zhang, say something."

"..."

"I think your microphone is broken."

"Can you disconnect and reconnect?"

"Hey, he's typing something. I... will... reboot. Ok, let's wait for him to reboot."

"Hey, Mike's back. Someone tell him we're waiting on Zhang to reboot."

"I don't think he can hear us."

"Guys, I'm gonna go grab a coffee while Mike and Zhang figure it out."

Re:Remote Only by jon-wood on Thursday June 07, 2018 @09:23AM (#17255511)
If you're working in a largely co-located company, where video conferences are an uncommon occurrence then this probably fits.

In the context of this conversation around remote only companies though, everyone is going to be set up to be able to properly participate in a video call - that means making sure everyone has a decent internet connection, microphone, and camera at home. When people aren't at home tools like Zoom have the ability for them to dial in to conferences on a regular phone which deals with the remaining problems.

Re:Remote Only by drdaeman on Thursday June 07, 2018 @09:33AM (#17255594)
> In the context of this conversation around remote only companies though

I've worked mostly remote for many years and please trust me - it's almost exactly the same, with every weekly meeting starting with "is everyone here", "do you hear me?" etc etc.

This is especially when working from home - typical residential connections are having less nicer SLA and may get flaky from time to time. And someone may leave their phone near mic cable. Or someone's machine may need rebooting. Or conferencing service may be experiencing problems.

Glad if it's not like this for some, but I believe it's not exactly uncommon.

Re:Remote Only by everythingswan on Thursday June 07, 2018 @09:26AM (#17255540)
I worked with a team remotely for 3 years, solely relying on Google Hangouts for video and an occasional Zoom meeting. The video/mic/hardware problems are _incredibly_ rare.

Being late or grabbing coffee instead of starting a meeting are culture problems at a company, not problems with the medium.

Re:Remote Only by pavel_lishin on Thursday June 07, 2018 @09:41AM (#17255649)
> The video/mic/hardware problems are _incredibly_ rare.

You've had better luck than I have. Our New York team is still dealing with the problem of the Boston office being virtually inaudible, while Dublin sounds like they're speaking through a megaphone directly into my ear.

That is, assuming we didn't lose a room, or the Hangouts equipment isn't broken - then Boston uses our manager's laptop, which actually sometimes has better sound quality.

Re:Remote Only by smt88 on Thursday June 07, 2018 @09:26AM (#17255537)
I've worked remotely for 10 years. This happens with new setups, but if you're doing it daily, it stops happening.

I don't do standups anymore, but at my last company, they often took about 5 minutes from dialing to hangup.

Re:Remote Only by newscracker on Thursday June 07, 2018 @09:57PM (#17261963)
I covered part of this under "being available" at the end of my comment. But I completely get what you're driving at. Apart from people's availability, some of the technology is still horrible and quite unreliable (I'm looking at you, Skype for Business). But my main point was that writing emails and documentation cannot be a substitute for instant communication (chat) or voice communication.
Re:Remote Only by eequah9L on Thursday June 07, 2018 @10:34AM (#17256066)
Zhang was on mute. Happens to the best of us.
Re:Remote Only by soneca on Thursday June 07, 2018 @09:09AM (#17255405)
I wholeheartedly agree! I am writing a newsletter to help developers improve their written communication (shameless plug: https://writingfordevelopers.substack.com/)

Do you have an opinion on what aspects of written communication are the most important for remote work?

Just gathering ideas to write about! :)

Re:Remote Only by nvarsj on Friday June 08, 2018 @06:57AM (#17264198)
I think the thing a lot of people struggle with are applying soft skills in their written words. Many devs in my experience come across as very analytical, almost emotionless in their written communication. It's precise, but not great for developing social bonds. It's something I'm very guilty of myself, especially in code reviews. I think we could all benefit by considering the human element in our writing.

It's such a different skill set though compared to in-person communication, where much of this happens non-verbally. I think it's a lot easier for people who grew up with it. I spent a lot of time on MUDs and BBSs when I was younger, where this kind of communication was prevalent.

Re:Remote Only by crunchlibrarian on Thursday June 07, 2018 @12:08PM (#17257119)
I like this idea of a "company's written language", I have known many people who are great communicators who nonetheless didn't write using the correct corporate cultural terms and were viewed as "poor communicators".

Basically this boils down to how strictly you cling to new buzzwords.

Re:Remote Only by markkanof on Thursday June 07, 2018 @03:05PM (#17259089)
I agree completely, and to build on that idea, it is extremely valuable to be able to take an idea from your head and write it down in a way that fully explains the idea, but is as concise as possible. I see this go wrong a lot in Slack. Some people will not take the time to completely form a thought and will instead just type everything that is in there head as quickly as they can. Then others react because they have misunderstood the original point. If you have a few people trying to communicate with this method it quickly becomes chaos. The process of untangling some of those types of conversations can take far longer than the original conversation did.
Re:Remote Only by mcovey on Friday June 08, 2018 @09:52AM (#17265344)
Even though I'm much better at expressing myself with writing than through speaking, I get some anxiety about bothering people or keeping their attention that makes it difficult to "work through" a problem remotely. When I know exactly what I'm doing and just need to communicate it, everything's great. When there's an issue that two or more people need to look at and discuss at the same time, it gets much more difficult. I'd be the perfect remote worker for a company without tight deadlines where there are never any "fires" that need to be put out. But there aren't very many of those.
Re:Remote Only by smpetrey on Thursday June 07, 2018 @12:44PM (#17257573)
100% agree. I think this would even apply to non-remote jobs too.

I used to work remotely as a freelancer and I miss it so much. I now work in-house at an agency and everyone here fails so miserably at writing. Almost all discussion is verbal, nothing is documented and so much double-work happens it's not even funny.

To make matters worse, the agency doesn't use any project management software. So all projects have seemingly imminent deadlines. It's miserable.

If our team was more apt to learn, adapt and document more, we'd probably be a lot happier.

Re:Remote Only by ScarZy on Thursday June 07, 2018 @07:56AM (#17254999)
This is the main reason I want to try and learn Emacs, OrgMode, and Babel. The stuff that Howard Abrahams discusses on the below video is something I think would be highly successful in a remote environment. Documenting your workflow as you go, including commands and output, then emailing it to your team that day or uploading it to a document store/gitbook:

https://www.youtube.com/watch?v=dljNabciEGg

Re:Remote Only by pvaldes on Thursday June 07, 2018 @10:35AM (#17256086)
You can grasp org.mode pretty quickly, is all tab-tab-tab and a lot of asterisks here and there.

Emacs needs more effort but it is an achievable goal. Very customisable so you could even ask somebody to create your own comands and circumnavigate the hairy parts for a lot of time until building enough confidence. Finding a good tutor or having somebody interested in the program in your company would help a lot, obviously.

Re:Remote Only by intrasight on Thursday June 07, 2018 @01:04PM (#17257805)
>If you're not good at written communication, or you work with people who are not good at it, remote work will be miserable.

not just remote - any and all work will be miserable. I work remote and in person with lots of people who will not write things down. When I call them on it, they say "I'm not your secretary" - but they are happy to have everyone be their secretary.

Re:Remote Only by Fire-Dragon-DoL on Friday June 08, 2018 @03:16PM (#17268783)
We had the same problem even in person to be fair: one of the guy didn't speak english properly, we had a lot of troubles understanding him. And he also talked a lot, which made things worse (listen to a lot of things you don't understand). In the end, communication must be great, no matter what.
Re:Remote Only by yosito on Thursday June 07, 2018 @09:26AM (#17255536)
No amount of writing in my life prepared me for the amount of writing I do as a remote developer. I probably write 20+ "pages" a day if you count all of the documentation, emails, chat messages and GitHub discussions I write. Luckily for me, I love writing.
Re:Remote Only by 0xdeadbeefbabe on Thursday June 07, 2018 @11:26AM (#17256622)
Well Linus is a great writer, so I agree with your conclusion.