Commit 6ba7152b authored by Suri Patel 's avatar Suri Patel 💬

added mek's quote and changed date

parent d137a35f
Pipeline #32702559 passed with stages
in 27 minutes and 39 seconds
......@@ -92,12 +92,14 @@ precedence in some cases and be more important than the gain in speed.” – Ra
At GitLab, we practice [asynchronous communication](/handbook/communication/),
so we “don’t expect an instantaneous response,” allowing us to focus on our
individual workflows. The problem with working asynchronously is that projects
can become delayed when working with team members in almost every time zone and
can become delayed when working with team members in different time zones and
responses don’t trickle in until the following day. Rapid movement might not be
made on projects because of time zone differences. [Mek Stittri](/team/#mekdev),
Engineering Manager of the Quality team, and Rachel acknowledge the difficulties
that can come with asynchronous communication.
>“My team is spread across so many projects and has someone in almost every time
zone, meaning communication can be challenging.” – Mek Stittri
>“This is my first role with an asynchronous method of working. I am finding that
many practices that work in a synchronous team need some adjustment to be useful here.” – Rachel Nienaber
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment