✊ Let's make our online communication productive again! Together.
Tags: beginners, productivity, tutorial, dx
Published: 2020-11-15 19:00:12

## Introduction

Hi, DEV people! I'm back with super-awesome news: the Universe has heard my prayers! 🎉 Seriously, I found the coolest idea for all remote people (and not only) around the world.

It's a rather simple but at the same time very deep idea, which many people diligently ignore and don't notice. For a short:

> Don't say just "Hello" in chat, describe your question immediately.

Who're interested in details and reasoning, please follow me in this article.

<a name="toc"></a>
### 📝 Table of contents

- [A few words from the author](#ch-0)
- [The problem of online communication](#ch-1)
- [The "No Hello" manifesto](#ch-2)
- [Let's apply this knowledge](#ch-3)
- [Online communication productive again!](#ch-4)

<a name="ch-0"></a>
## A few words from the author

Initially, I found a website [nohello.com](https://nohello.com), where the idea itself was described in detail. Next, I started looking for more resources describing such areas for productive communication and found the Russian-edition of original website called [neprivet.ru](https://neprivet.ru), where more illustrative examples were given.

It inspired me to improve the idea in a more understandable form for everyone. This is what this article is all about.

> Also, this article deals only with **working correspondence within the company**, that has moved to remote work. When communicating with friends or family, this article isn't to be followed! 😎

[↑ Table of contents](#toc)

<a name="ch-1"></a>
## 🤔 The problem of online communication

How often have you had to wait for a specific question in your work chat room after the phrase "Hello"? I deal with it all the time, because I'm very often the link in the chain of communication in my company.

Usually, it looks like this:

![the hello problem](https://dev-to-uploads.s3.amazonaws.com/i/2chg4px3mg99r1ds6l2y.png)

How productive is such communication? Approximately as productive as reading just the title of an article and waiting for the author to finish the other part.

You (or your colleagues) try to be polite without going into problems, as people do when they meet in person. **But chat is very different!**

People print much slower than they say. Instead of being polite, you make the other person wait until you formulate the question, which leads to a loss of productivity.

Therefore, it's better to do so:

![conversation solution](https://dev-to-uploads.s3.amazonaws.com/i/gwglx0a5zu4zgjlidbe5.png)

In addition, when you ask a question at once, the possibility of **asynchronous interaction** is opened. If the person you're talking to is unavailable and you leave before he or she gets back, he or she **can still answer** the question instead of looking at your "Hello" and thinking about what happened.

Yep, this is the main idea of the "No Hello" manifesto.

[↑ Table of contents](#toc)

<a name="ch-2"></a>
## 📖 The "No Hello" manifesto

1. Send your question in one clear & understandable message.
2. Describe your question in as much detail as possible.
3. If necessary, split your message into semantic paragraphs.

[↑ Table of contents](#toc)

<a name="ch-3"></a>
## ✅ Let's apply this knowledge

Okay. Just rewrite the message from Jane Doe, using our new knowledge:

![manifesto](https://dev-to-uploads.s3.amazonaws.com/i/sz5xqgk4baogvec98rkl.png)

If you read this message from Jane, you will be able to answer faster, because you will immediately begin to think about the question. 

On the other hand, if you get this message in, say, a couple of hours, you will have more input data to answer.

It's great, isn't it? 🥳

[↑ Table of contents](#toc)

<a name="ch-4"></a>
## 👍 Online communication productive again!

Now, if you received a message from a colleague at work that has no semantic value, such as "_Hello. Are you here?_" or "_Hello! There is a question_" or "_Do you have a minute?_"... **Just send a link to this article!**

<a name=""></a>
## P.S.

If you want more articles (like this) on this blog, then post a comment below and subscribe to me. Thanks! 😻

And of course, you can help me make developers' lives even better! Just connect to one of my projects as a contributor. It's easy!

My projects that need your help (and stars) 👇

- 🔥 [gowebly][gowebly_url]: A next-generation CLI tool for easily build amazing web applications with Go on the backend, using htmx & hyperscript and the most popular atomic/utility-first CSS frameworks on the frontend.
- ✨ [create-go-app][cgapp_url]: Create a new production-ready project with Go backend, frontend and deploy automation by running one CLI command.
- 🏃 [yatr][yatr_url]: Yet Another Task Runner allows you to organize and automate your routine operations that you normally do in Makefile (or else) for each project.
- 📚 [gosl][gosl_url]: The Go Snippet Library provides snippets collection for working with routine operations in your Go programs with a super user-friendly API and the most efficient performance.
- 🏄‍♂️ [csv2api][csv2api_url]: The parser reads the CSV file with the raw data, filters the records, identifies fields to be changed, and sends a request to update the data to the specified endpoint of your REST API.
- 🚴 [json2csv][json2csv_url]: The parser can read given folder with JSON files, filtering and qualifying input data with intent & stop words dictionaries and save results to CSV files by given chunk size.

<!-- Footer links -->

[gowebly_url]: https://github.com/gowebly
[cgapp_url]: https://github.com/create-go-app
[yatr_url]: https://github.com/koddr/yatr
[gosl_url]: https://github.com/koddr/gosl
[csv2api_url]: https://github.com/koddr/csv2api
[json2csv_url]: https://github.com/koddr/json2csv