Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First draft of tool selection chapter #38

Merged
merged 5 commits into from Sep 24, 2020

Conversation

funnelfiasco
Copy link

Here it is for your review

@funnelfiasco funnelfiasco linked an issue Sep 7, 2020 that may be closed by this pull request
@funnelfiasco
Copy link
Author

Also: I intentionally left out anything about etiquette and practice because those are/will be covered in Jimmy's "Communication practices typical of high-performing remote teams" chapter and Joe's chapter (#16).

@semioticrobotic
Copy link
Member

Can't wait to review. Thanks, @funnelfiasco, for your awesome work.

The first draft of the introduction said both that "picking the right tool won't automatically make your distributed work successful" and that "there's no one right tool," so I tried to reconcile these statements into a clearer frame for the piece.
@semioticrobotic
Copy link
Member

Ah! Forgot to leave a comment here. Sorry, @funnelfiasco! I'm finished with the first round of edits and happy to discuss. Thanks for this great chapter.

@semioticrobotic
Copy link
Member

Hey @trncb: Would you mind giving this a second look?

As you can see (above), this is @funnelfiasco's first draft and I've made some edits and suggestions on it, but a more thorough cleanup may be helpful as @funnelfiasco puts his finishing touches in.

@trncb
Copy link
Member

trncb commented Sep 23, 2020

@funnelfiasco great article!

I have made a few more suggestions for consideration.

@semioticrobotic
Copy link
Member

This is great, @trncb. Thanks so much for catching all these mistakes that slipped by us.

The only changes on which I'd push back are those related to the use of em dashes (—). You've proposed changing those to hyphens, which isn't really our style (em dashes without spaces is our style for offsetting clauses for emphasis, and it renders most appropriately in print and typeset).

@funnelfiasco
Copy link
Author

@trncb you capitalized "Internet". I love you already. :-) I'm with @semioticrobotic on the em dashes though—copious em dashery is part of my #Personal #Brand.

@semioticrobotic I read through the chapter as-is and I couldn't tell where my draft ended and your edits begin. I also did add the consideration that I wasn't sure if I had but was definitely going to if I hadn't, so from my perspective this is ready once the em dashes are restored. 😉

@trncb
Copy link
Member

trncb commented Sep 24, 2020

haha, thanks @funnelfiasco.

No problem with regards to the em dash, I'll fix that right up.

@semioticrobotic
Copy link
Member

@semioticrobotic I read through the chapter as-is and I couldn't tell where my draft ended and your edits begin. I also did add the consideration that I wasn't sure if I had but was definitely going to if I hadn't, so from my perspective this is ready once the em dashes are restored.

No greater compliment for an editor. Thanks, @funnelfiasco. Glad it's to your liking. When @trncb makes his final tweaks, we'll get it moving along. Huge thank you for contributing this great resource.

@trncb
Copy link
Member

trncb commented Sep 24, 2020

@funnelfiasco @semioticrobotic em dashes restored.

@semioticrobotic
Copy link
Member

Thanks, all! Let's wrap this one.

@semioticrobotic semioticrobotic merged commit 60ae7be into master Sep 24, 2020
@semioticrobotic semioticrobotic deleted the what_to_select_when_youre_connecting branch September 24, 2020 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a chapter on considerations for selecting communication tools
3 participants