Too many emails, not enough work

All of us get emails daily.
If you are managers, you probably get more than others.
So when is it too much?

I work as a Web team leader and Lately I have felt like I am spending most of my time reading and writing emails than actually working. So, I examined my inbox a bit and discovered I am getting between 150 to 300 emails each day.

Now, say I spend an average of 10 seconds per email (Some might be 5, some might be up to a minute), it will take a full non-stop hour to cover all of them… That’s a lot!

Next, I separated my emails to those where I am in the “to” field and the rest. Unfortunately, that left me with 2/3 of the emails still addressed to me directly 🙁

My conclusion is simple – All of us need to reduce our emails sending!

How can we reduce our outgoing emails\make them more effective?


I can divide the problematic emails to several types:

  • Too many recipients


    Those are the emails that are actually relevant to a small group of people but is sent to a large group from a perspective of “Maybe they will be interested in it too” or “Why shouldn’t I tell everyone about it?”.
    Do the math. a 2 minutes email sent to 30 people is now a 60 minutes email…. it’s that simple.
    So, Think twice before you send an email to a predefined list or before adding more people to your email.


  • Missing context emails


    Some emails require context. Sending a blurry email causes the recipient to spend time searching prior emails on this matter trying to figure out what he needs to answer on or reply back starting a ping pong thread.
    Always specify a short description of the context and need.


  • Long thread looping


    This is actually a private case of the Missing Context emails, but is worth mentioning!
    After a long thread, you’ve decided to loop in someone.
    Do you really expect her to read all the previous emails on the thread, trying to fish out the relevant part and filtering the non relevant one?
    When adding someone to a long threaded email, please summarize the issues and needs in short, don’t make them read all of it.
  • Link to external articles\documents

    You just read some interesting article and you want to share it.

    What did you like about it? what were the main issues? can you summarize it in several points?
    Share the link, but also add a short summary in your own words.
    This will most likely save some time for others + help them decide if they want to spend time reading the actual article or not.


  • Multi-Subject emails

    Most of these emails are “Let’s make sure everyone responses to his part” or emails who got blown up with too many issues and data.
    Such emails lose effectiveness since sometimes it is not clear who needs to answer what and why is the other discussion relevant to me…
    It’s OK to split an email to several emails with specific recipients in such cases. it will probably be more effective!

So, when you send an email, think twice.

  • Do you really need to?
  • Are all recipients relevant?
  • Does it have all needed context?
  • Can it be shorter and more clear?
  • Would a F2F meeting be less wasteful?


Our time is valuable!

A new parent for the second time

4 days ago, my second child was born.

Dror, my first Son, stepped out into the ring, weighing 3.255 KG.

In the first pregnancy period, Every little things was exciting. every check-up, every ultra-sound, etc.

The second time around, let’s face it. you are less excited.

You come to some of the check-ups, you are less attentive to your wife needs, it’s “another pregnancy”…

Well… I thought the birth process itself would also be less exciting, but… when I saw my kid and the tears came out I realized I was wrong.

Yesterday, I’ve put both my kids to sleep. I have to say that passing between the two rooms and realizing I now have two kids was a real empowering feeling.

Well… sleepless nights… here we come… 🙂

Why do today what you can do tomorrow? (Procrastination)

“Never put off until tomorrow what you can do the day after tomorrow.” ― Mark Twain

Procrastination – “…the act of replacing high-priority actions with tasks of lower priority, or doing something from which one derives enjoyment, and thus putting off important tasks to a later time.”

Yep, almost all of us do it from time to time.

It could be that homework assignment you should have started a month ago, the room you haven’t tided up since you moved to your apartment or The workout plan you promised you will start the next week…

Almost all of us have some “high priority” things we know we “have to” but avoid doing it “now” 🙂

We build a to-do list, knowing that some of the items will never get done. they will keep nibbling at our conscience, but we will never find the time to do them.

This of course leads to a feeling of dissatisfaction. “why can’t I get it done?”.

so… why does it happen?

Most of us enjoy setting a list of Goals\Tasks. This gives us a feeling of satisfaction from accomplishments and progress.

But… we have limited resources… time…

So, we end up with a big list which needs priorities. More enjoyable stuff will take less time due to their nature, causing less enjoyable stuff to be postponed. This is the basic human nature.

Cleaning up the list is not a simple task 🙂

Same as in any addiction, the first step is to admit we are procrastinating. It is not a definition of what we are but of what we are doing. it is not a genetic issue but rather a learned behavior, so as any other habit we can learn to avoid it.

My tips would be:

  • Don’t define goals which are not reasonable. You should either give it sufficient time to begin with or admit it cannot be done.


  • When something can be done right now, just do it. It’s amazing how a simple task can grow branches when it gets delayed.


  • Set a dedicated slot in your Weekly\Daily routine for cleaning up your list of tasks. figuring how much time you ACTUALLY have will help you in defining what you really can and can’t do.


  • When something gets delayed for a very long time, it’s probably time to say goodbye, Unless it got new priorities. the fact it was not prioritized till now means it should probably be left alone.


Some interesting reads:


Good and Bad Procrastination

How Seinfeld’s productivity secret fixed my procrastination problem

An Algorithm for Beating Procrastination


Front-End Testing Done Right

I have recently watched a video from a Google conference called “The future of front end testing“, Presented by Greg Dennis & Simon Stewart.

Although this is a video done more than a year ago, I was amazed at how these exact issues are what I face in my day to day tests automation experience.

For those of you who intend to watch the video, the first 28 minutes should suffice. the rest are less relevant.


Prefer Unit Tests and Integration Tests over System Tests


I have previously addressed this issue in the “Why System Tests Can’t Replace Unit Tests” post.

System tests, naturally based on a lot of different components, are a lot more flaky.

They are the least precise tests – when they fail they give you as less info as possible.



Social Challenges VS Technical Challenges


Social Challenges

I am a programmer, why do I need to write tests? I want to write features!

sounds familiar?

I have to admit that prior my work at sears israel, most of the places I worked in lacked this understanding.

developers wrote a set of minimal tests, if any, leaving the testing responsibility solely on the QA team shoulders.

a feature is not done until it is covered by automated tests. why?

let’s say you finished your feature and you manually tested it, deployed it to production and it all works fine. is that it?

what will happen if in another week someone else alters a related code, breaking your feature… how will that be detected?

Is that solely HIS responsibility? what if he had tests in your shared CI system that would indicate that he broke it?

Now think about YOU breaking someone else’s feature. wouldn’t YOU like to know it first?

The other issue is the ability of developer to understand the system structure, function and weak spots better than the QA team. YOU KNOW THE CODE! it’s as simple as that.


Technical Challenges

“I don’t know how to write tests for this”, “writing tests takes too much time”.

We all need  to learn. all the time. that’s how it is.

Most companies have some internal testing frameworks\conventions. If writing a test is hard or requires too much time then you are probably doing something wrong. either because you don’t know how to or the framework is not written correctly.


Flaky Tests


I’ve never seen a system who had non-flaky system tests. we all suffer from that.

An untrusted test Is not a test at all… actually WORSE!

It casts on the entire suite and you’re better of just deleting it!


Correct Test Writing Patterns


Parallel Tests Execution

System tests are slow… as such, we should strive for parallel execution.

in order to be able to do that make sure to:

  • Use a different account\user for each test, a different set of resources…
  • Avoid shared resources or assign a Resource allocator that will lock these resource when needed.

Identify Non-Deterministic States

does your application rely on some configuration or external data and you find yourself altering your tests code from time to time to match these changes?

Add hooks to the application to allow you to address these changes. write to files\db and allow the testing code to access that data.


Wait for The Correct App State

Many tests rely on the fact that a particular state was reached.

a dialog opened\a certain page was reached. etc.

add validations to your code to make sure that the state was reached before continuing to the next steps.

DO NOT USE non conditional sleeps in your code. this introduces either flakiness or long running tests. both are bad!


Page Objects and IDs

There is a reason ids exist in pages. It allows you to identify you are where you think you are. use them!

The Page Objects model allows a separation of control of your app into the actual pages, each responsible for two things:

1) Identifying itself and it’s components (using ids).

2) Exposing the available functionalities.


Not Everything Should be Done Through the UI

E2E tests don’t need to be entirely through the UI.

certain parts of the system can be mocked-up, which is a lot cheaper, AS LONG AS the mocked functionality is tested elsewhere.

I have encountered several occasions of claims against this mocking approach, most of them are based on the notion the System Tests are there to test the System and as such, they should have no mock-ups, ore only for external parts.

If this functionality is tested elsewhere and there is a specific test that tests this functionality, why do I need to test it again and pay the runtime price of this element again?

there is a THIN line between making system tests behave as UI unit tests which should be addressed so use mock-ups wisely.

If needed, address the application DB directly to assert that what you expected really happened.


Tests Should be Able to Run on Different Environments

Other than your local system and you CI system, you might want to execute your tests on other environments (Development\Integration…).

avoid hard-coded environment specific values, like URLs.

Use Guice for different implementations.


Shared Resources and Tests Data

Each test needs data, whether created data or existing one.

your testing framework should support data injection or data retrieval according the test needs.

(of course, don’t forget to cleanup after yourself).



Better testing to all of us 🙂




Not Everything Can Be Automated! Really!

Following my previous post, regarding System Tests misconception, I would like to address another misconception.


Some of you might think it is obvious. Well, good for you!

but… it’s amazing how many people miss this point.

I have been developing and writing automated tests and platforms for the past 5 years.


In the beginning…


When I first started developing automated tests for several companies I was amazed how few companies had actual automated tests.

Most had only manual testers, Some had semi manual tests, where the data creation was automated and the analysis was manual.

Only a few had actual Automated tests and a fewer knew how to actually write and maintain them correctly.

The notion of automated tests, at that time, was not easily grasped. There were claims that it will take a lot of time to build a basic framework for the tests, that the maintenance is too expensive, that it wouldn’t be scalable enough…

It took some time, but now we are at the opposite concept, were a lot of people believe everything can and should be automated.

Of course Automation is great. No argument here.

It allows you to have continuous integration environments, It is not human dependent and it can be very scalable.

Still, it has it’s downfalls.


What Can be Automated?


Technically speaking. all tests that require non graphical interactions (mainly composed of API calls, data analysis, Simple controller testing) and have no actual GUI, can  be automated.

Those are mostly tests which don’t require any human interaction, are straightforward and well defined functional tests.

Their objective is to see everything FUNCTIONS as it should.


So, if it’s technical possible, then they should always be automated?

Here comes the ROI issue into consideration.

Yes, writing an Automated test will sometime require a lot more time than manually testing it.

  • Time needed for developing the technical framework to support the requested functionality.
  • Data bootstrap which is needed for the testing environment.
  • Tests that will require a lot of maintenance or could be unstable in some environments.


So… What can’t be automated (Or rather shouldn’t)? 

There are a few issue in which automation is still lucking the proper solution.

A) Quality:

There are a few solutions out there that suggest they have the ability to estimate the quality of your product.

Up until now, I have yet to encounter an actual framework that gives a proper comprehensive automated solution.

In the past, I have worked quite a lot scheduling schools timetables. you can read more about it in my Jobs Diversity post.

There was a semi automated system that tried to produce a well balanced and fit schedule for all the teachers, but… no matter what, It was always down to some human considerations to wrap it up properly.

You couldn’t give up the human sense when it came to the need to compromise.

Today, I work at Sears Israel, where we are developing a Social e-Commerce and have a great need to examine our recommendations quality.

We do have several ideas regarding how to try and define quality measurement so they can be ran automatically, but still, they are not human-less.

Another example is a Mobile Navigation company I have worked with in the past which had a quality automated system in which they initially took a snapshot of what they considered to be a “Good quality output” and thereon relied on that fact to make sure all future results resemble the initial one. that sounded promising at the time, but…

After a while, the base snapshots where less and less examined, which resulted in bad quality being verified to persist being bad all across the system 🙂


B) Visual Layout and UI:

GUI elements can be tested for functionality. sure.

You have Jemmy for Java Swing applications, Selenium for web automation and more…

BUT, they are all good mostly at testing functionality. You can fetch an element X,Y location with these tools but you will not be able to ensure it appears correctly.

You can semi automate it and take screen capture of the app and later on examine them, but as I said, that’s not a fully automated process.

So.. you still need to “have a look” and see nothing visual was broken.

Remember: a selenium test will pass even if your button is located completely out of place, just as long as it is located and visible.


C) User Experience:

This is maybe the most important of them all.

You covered the functionality, The quality seems good and you even semi automated your screen captures. is that enough to guarantee a quality product?

hmmm…. what about the actual human who is going to use it? is the overall experience of a user on your site good? are the actions self explanatory? are the messages visible enough?

is he overloaded with too much info? and many many more questions can be asked regarding his experience.

Most of these questions cannot be answered in the context of a single feature but rather as a combination of several brought together.


There are a few more issues, but these are the biggest ones in my perspective.

So… don’t give up on your need for manual testing yet. We have still a way to go to get there, if ever…


Why System tests can’t replace Unit tests

Several times I have come across claims of redundant testing.

Most of which claim that a System test can cover all the functionality, so why do we need a unit test?

First of all I would like to emphasize their differences.

Unit tests

Unit tests are basically short and specific.

Checking your helper class returns the right results, test your algorithm on different inputs and checking all edge cases. It is the smallest and basic testable part in an application.

They test that the code actually does what it should… CODE WISE.

Due to their nature, they usually don’t need any third parties or other external dependencies. they are self contained.

System Tests

A complete and integrated testing to make sure all the different parts of the system work together as expected.

These tests are usually more complicated. Many of them will include third parties for their automation, they fall into the “black box testing” criteria and they usually test the functionality of the application as a whole.

Wouldn’t a system test be able to cover any unit test?

Absolutely not!

Think about it.

Even if the same data is created in the beginning of the test and the same assertions are made, how can you be certain who is responsible for the success or failure? there are usually several components, some of which might affect the result.

The test can fail due to several components which will require more investigation, drilling into each components in any case, making sure “this part up until here” works OK and will eventually lead to more wasted time asking yourself “why didn’t I write a unit test for this”.

If the test passed, does it guarantee that everything is OK?

Your first intuition would be YES. but… you’d be wrong 🙂

This only means the SYSTEM is OK at this point. maybe your code has an error which is luckily missed due to another component, ran after your code.

What will happen if that piece of code changes and the actual bugs appear? how much time will you spend tracing down the bug?

Moreover, system tests will usually cover main flows, not edge cases.

We can write system tests for all edge cases.

Yes, you CAN. but how effective will they be? how long will they run?

System tests are almost always slower then unit tests. if not, something is wrong with your unit tests 🙂

Secondly, as explained before, that will most likely violate the “black box testing” methodology since you will have to be aware of the edge cases IN THE CODE.

Another issue is catching bad commits. executing tests before committing will detect your errors.

No problem here, All our programmers execute tests before they commit.

Do they now?

As per my experience, most developers will run the minimal set of tests they can to make sure they did not break anything. They will search for all related unit tests using references to the changed functions or using some simple type searching. most of the time they will not be even aware you have system tests that cover the part they’ve changed.

Still, if we make sure everyone runs ALL the tests and we do not suffer from long execution times, why do we still need unit tests?
that’s simple, because of the “ignored test” syndrome.

never heard of it? c’mmon…

when a test is unstable or fails and you have no time to fix it, you just put it in ignore or ignore it anyway.

but, since this is a system test it checks several components, meaning you didn’t just disable that specific test but all other “disguised” tests for sub-components. had you written unit tests, this test had less effect on the questions: “should we fix it now? is it top priority? is anything else covering this issue?”

To conclude,

System tests and Unit tests each have a specific role. They complement each other.

If you are pressured, System tests will cover basic functionality. but if you have the time, do both, ALWAYS!

For more formal definitions look at:

Unit Tests

System Tests

Unit tests vs System tests

Why wouldn’t it work in Israel

The Good Stuff…

Yes, we Israelis pride ourselves of being warm and helping each others everywhere on the globe.

we are also highly initiative and will always find the best deals there are.

Alas, this is also the reason why some things can never work in our country…

Whose Turn is It?

I just came back from driving more than 2,000 KM around California and Nevada.

I found out there are some rules in the US that are different from what I was used to.

  • Right of way in junctions with no traffic lights – in Israel, when you get to a junction with no traffic lights, the right of way is given to the car arriving from the right side of you. In traffic circles, it’s the car on your left… In the US, if you get to a junction in which everyone has a stop sign, the right of way is given to the first car who arrived at the junction! yep, it sounds weird at first, but it works.
  • Turning right on a red light – unless specified otherwise, when you get to a right turn and the light is red, it functions as a stop sign. meaning, you can make the turn on the red light just as long as you stop at the junction before.
  • Green light for two intersecting lanes – sounds weird but there are junctions in which the left turning lane and the opposing straight lane have green light at the same time. in which case, the left turning lane must wait for the junction to be clear before turning left. this was a near accident experience to me when I first got to LA :).

I did loose a psychic ability though…

in Israel, you have a psychic ability allowing you to control another driver. if you need to change to a left lane in order to pass a car and there is currently another car on the left lane, far behind you, you just need to hit the signal and you can make the other car driver speed up, trying to make its best not to let you pass.

Another weird thing was when I missed the light turning from red to green and I got delayed for 3 seconds, thinking about something else. nobody blew their horn, that was really weird…

Of course, none of these would work in Israel since they require some basic patience.

Apples anyone?

When I was hitch-hiking around in New Zealand, I came across many road-stands with fruits for sale. the stands were packed with all kinds of fruits in different bag sizes and the price was indicated on each bag. there was a metal mail-box style box in which you placed the payment. You just had to pick your bag, place the amount in the box and move on. No, there was nobody watching the place. no camera, no personal, nothing… just your integrity… my first impression was – are they mad? what prevents people from just picking up a bag and moving on?

Several nature reserves and parks along the US have explanatory pamphlets at the entrance, like the amazing Mariposa Grove. the pamphlets can be picked up independently while the sign next to it just indicates that a donation of a quarter or two quarters are requested.

The same thing happened in several gas stations, in which you pumped your own gas, read the amount on the meter and then entered the store to pay the bill…

Your table is ready

In the US, some restaurants have a long waiting list. this forms a big line of people waiting outside the restaurant waiting to be called. but what if you want to go for a short walk in the meantime? get something from your car? there is a chance you will miss your turn…

So, when you register, you’ll get a small table pager transmitter that will indicate that your table is ready.

I would love to see it here, but I am pretty sure some or most of these transmitters will not be returned to the restaurants 🙁

Just buy the cup

Everyone is aware of the fast food refill policy. just buy the cup and feel free to refill. this is of course part of the reason for obesity in the US. (The big cap gets up to 1.2 Litters and more !!!).

Israelis would probably ask – why should I buy several cups for our table, let’s just buy one, it’s a refill… we could all enjoy the cup…

This is just a short list, sadly there are many more examples of this kind…

could this change? could we be more patient and trusting?

I hope so…

Jobs Diversity

Diversity. that’s what it is all about…

Most people I know worked in maybe two, sometimes three different jobs.

In the IT , most of the people started programming in high school, a lot of them even programmed in their military service and continued so till today.

There have been occasions in which I came across people who originated from other expertise fields such as Video photographers,  Renovation contractors and even Electricians.

I started working at the age of 16 or so.

My first actual job was as member of a stage crew, setting up sound and light system for different stages. Small rock concerts, high school graduation events and so on… I did it for around a year and a half or so. I got to see a lot of interesting events and learned a lot of technical stuff regarding sound systems.

After that I went to the army for a couple of years.

Finishing the army I went to a trip abroad for almost a year. During the trip I worked a while in apple and peach picking. It was pretty hard, waking up at 5:30 every morning, starting picking at 6:30-7:00 till 18:00 in the evening. I think the prodigy music I heard while picking was what kept me going 🙂

During my trip hitch-hiking, I came across a 70 year old farmer who told me he held 35 different positions in his lifetime! during a two hours ride he described each and every one of them, roaming between a circus clown and an architect, finally resulting in being a farmer.

I remember thinking to myself: “that sound like a truly fulfilling life”.

After I returned, I started working as a school’s scheduler planner. I did that every summer for 6 years after. I got acquainted with the educational system a bit and felt like I was solving puzzles all the time. It was a very challenging job. I estimate I worked with around 130 different schools in these years and scheduled around 300 schedules.

After that, I worked a bit as a waiter in a small Italian restaurant. Learned a bit about Italian food, wine, and ate a lot of pasta!

Next job was in Sales in a Telemarketing company. I worked about half a year there and got some experience at costumer service and Sales. Eventually, I felt as if I could sell any crap to anyone and that felt wrong, so I moved on…

Next was at a security company. I worked both as a Security officer and as a guard. I mostly worked nights and studied during the day. It was a very stressful period which lasted around a year and a half.

My next job was in a security alarm center, monitoring alarms in shops and houses. I sat in front of two monitors, each displaying between 20-40 lines of alarms from which I had to figure out which one was an actual burglary and which were just bad detectors. Notifying the police on a wrong alarm would have resulted in a fine!

Later on I moved to Beer-Sheva to study computer science. Since I was a film editor (self taught) and a cinema fan, I found a job in the university cinema, screening movies on film. I think one of the most exciting moment I still remember was screening cinema paradiso, a movie about a projectionist…

I worked as a projectionist for two years, a period in which I saw a lot of movies

After that, I started working as a student and later on as a full time job in software engineering and been here ever since.

I think every job I worked on the way taught me something and It helps me get some perspective on my day to day routine. I feel lucky for that

Yep, Diversity is what it is all about…

Sorry, we are only hiring #487

A Pessimistic prophecy by an Optimistic guy 🙂

Back in the old days…

when a boy wanted to find his match, he would go on dates, see if there’s a match and then decide if he wants to move on…

Today, we have all kind of “dating” sites which allows us to filter out people we will meet up with by easily clicking on some filter options:

Is he a smoker? religious? what’s his age range? and so on…

On another issue, many sites today try to personalize your experience. recommend things based on your prior purchases (“People who bought this cat hairbrush also bought the amazing foot massage machine“), post adds based on your searches, etc.

Why are these two things related?  Categorizing people.

Yep, It is a lot easier to categorize people. we all know it. it saves time and effort and a lot of inconveniences.

We do it all the time, whether consciously or not. but why?

There are hundreds of assays written on this matter, for example The psychology of prejudice. And there are even guides on How to categories personalities.

Basically, it comes down to this – It’s easier, a lot easier!

We feel insecure when confronted with someone we don’t know. We don’t understand how he thinks, what he likes, etc. so, we try to categorize him since that will allow us to “know” him much quicker, right?

So, I would meet the love of my life since he passed a filter saying he is “semi-religious, likes long hikes…”, and if a person bought something, we can probably guess what he’ll need next since we are all so predictable and simple to understand. there is probably some good mathematical formula that explains us. and if it is not the case and our engine failed to find a match, this just means we need to adjust the formula.


The way these things are going, we can pretty much assume that, as technology and math advances, each person can comply to a formula and even a number. yes, a number…

For the sake of argument, let’s say we can all be mapped to 1,000 types of personalities. wouldn’t that be simpler? Think about it…

The dating ads\engines will just say “#576 looking for #876 OR #324”.

HR people will not have to go as far as to advertise all job requirements, they’ll just be looking for numbers…

Is it that far fetched? hmm….

Back to Speaking

Starting tomorrow, I am starting to talk again.

For those of you who have not yet done so, I suggest you first read my previous post “Talk, Talk and Talk”.

After two weeks of silence, two weeks of scrabbling on papers and having notepad as my best friend, I would finally be welcomed back to society. back to the “normal” people. those who communicate verbally.

I have to admit, it was a lot harder than I thought it would be. a lot. and it got harder every day.


I can’t pinpoint to a single thing that explains it. it’s, as in many cases, a combination…

I would always walk around with some way of writing. either a pocket notebook or my cell phone. there were occasions in which a simple hand or head signal would suffice but that was very limiting.

I avoided complicated tasks. even ordering food at a coffee shop or a restaurant would end up in me pointing on the menu like my baby daughter, only she could say “this”.

I hardly met up with friends since I felt it would be a bit awkward. When I did meet up with some friends I found out I was wrong. it was VERY awkward and frustrating. I guess it depends on the type of person you are, but the most common frustrating feeling was felt anytime a subject was raised on which I had something to say.

If any of you ever traveled alone somewhere, discovered amazing places or experienced new things and felt the need to share and suddenly realized you have no one to share it with, that’s the feeling. but mostly intellectually. Basic feeling could still be signaled using facial expressions. but thoughts….. nope.

I chatted all the time. Gmail, Skype, Facebook… it’s amazing how many people are available almost all day long on all these platforms. after a while my friends figured, “why should we chat” so we started phone-chatting. they would phone, I would write. this was weird. first of all, every time any of them phoned they’d start be saying: “hello?”, waiting for my answer. 5 seconds after they would go “hmmm… right…”. the chat editor looked funny since it only showed my side of the conversation.

All of you, speakers out there, listen up….

We, the non speakers sometimes need more time to communicate, so patience…

I’ve improved my mime skills a lot and discovered how important it is for the other person to repeat verbally on what he understood. I came across many occasions on which the other sided nodded intensively only to find out later on he did not understand me at all.

On one end, I did enjoy the silence. on the other, it freaked me out sometimes. there’s the notion that you should think twice before saying some things? well… I had the chance to think about it more.

I would suggest to all of you to try it for a day or two. you would come to notice how commonly without thinking you speak and learn to appreciate this ability a bit more.