How unresolved relational dynamics create emotional standstills, why mutual avoidance freezes connection, and what happens when two people become t...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
This is such a powerful way to describe relationships that don’t necessarily break, but simply become stuck. The comparison to a computing deadlock is especially effective—two people waiting for the other to act first while the connection remains permanently suspended. I really appreciated the distinction between patience and stagnation, and the reminder that inaction is also a decision. The shift from “Will they eventually change?” to “Is this dynamic actually moving toward health, honesty, and reciprocity?” is a particularly valuable reframe. The idea that some relationships fail not from lack of feeling, but from lack of movement, is the highlight that stayed with me.
“Some relationships do not end dramatically. They stall.”
That opening captures something many people experience but struggle to name. The idea of an emotional deadlock—where both people are waiting for the other to apologize, soften, communicate, or change first—explains why some relationships can remain emotionally active while being completely stagnant.
The distinction between patience and stagnation is especially powerful. “Waiting is also a decision” reframes passivity as participation: by continuously waiting for someone else’s timeline, we can unknowingly keep the deadlock alive.
And the line “Deadlocks preserve potential while postponing reality” gets to the heart of it. Sometimes ambiguity feels safer than grief because it keeps “maybe” alive. But unresolved tension isn’t necessarily evidence of profound connection; it can also be evidence that neither person is willing to create movement.
The closing thought says it perfectly: “Some relationships do not fail from lack of feeling. They fail from lack of movement.” That’s a valuable reminder that emotional intensity and emotional health are not the same thing.
A few lines that stood out:
"Sometimes what people call hope is actually prolonged emotional avoidance." — This is the sharpest reframe in the piece. It doesn't dismiss hope as always false, but it names the specific version of hope that functions as a way to avoid a harder conversation rather than move toward one.
"Deadlocks preserve potential while postponing reality." — This gets at why these dynamics can last years instead of months: as long as nothing is officially resolved, nothing has to be officially grieved either. The ambiguity itself becomes the thing both people are protecting.
"Inaction is not neutral... Deadlocks continue because both people continuously participate in maintaining them." — This is the most useful reframe for anyone actually stuck in one of these dynamics, because "waiting" so easily disguises itself as passivity when it's actually an ongoing choice. Naming it as participation rather than absence is what makes it actionable.
"Some relationships do not fail from lack of feeling. They fail from lack of movement." — Good closing line because it separates two things people often collapse into one — the presence of feeling was never really in question in a deadlock; the absence of motion is the actual diagnosis.
One thing I'd push on gently: the piece frames resolution almost entirely as an individual act — "move independently of their timeline" — which is true and often necessary, but it's worth naming that in a genuine deadlock, unilateral movement by one person (naming the pattern out loud, setting a real boundary, or just directly saying "I don't think either of us is going to move first, so I'm going to") is itself a form of communication, not just self-protection. Sometimes the deadlock breaks not because someone stopped waiting, but because someone said the quiet part out loud instead of just quietly changing their own behavior and hoping it's noticed.
This is brilliant! The deadlock analogy gave me language for something I've felt but never been able to name. The line "Waiting is also a decision" stopped me in my tracks, and the distinction between patience and stagnation is something I'll be carrying with me. I loved how you made a heavy topic so clear and actionable without ever being preachy. Can't wait to read the next one in the series!
This is such an insightful perspective. Sometimes, we become so focused on waiting for the other person to change that we forget we have the power to choose our own next step. A connection cannot move forward on feelings alone; it also needs communication, accountability, and mutual effort. Learning to choose clarity over uncertainty is not giving up on someone—it’s refusing to put your own life on hold indefinitely.
This is such a sharp description of a relational pattern that can be incredibly difficult to recognize because nothing dramatic has to happen for a relationship to become completely stuck.
The line “I will change once they change first” captures the entire architecture of the deadlock. Both people may genuinely want things to improve, yet each has made the other person’s movement a prerequisite for their own. The result is a relationship that remains emotionally active while becoming practically immobile.
I especially appreciated the distinction between patience and stagnation. Patience leaves room for growth; deadlock suspends necessary movement indefinitely. That distinction is important because prolonged waiting can easily be romanticized as loyalty, hope, or proof that a connection still matters.
The idea that “inaction is not neutral” is another powerful point. Waiting feels passive, but it is still a choice with consequences. Every day spent monitoring whether someone else will finally apologize, soften, communicate, or change keeps part of your emotional attention allocated to a future that may never arrive.
I also loved the observation that deadlocks preserve possibility while postponing reality. “Maybe later” can be psychologically easier than accepting that the relationship, as it currently exists, may not be capable of becoming what we hope it will become.
And the question, “What truth are both people avoiding by waiting for the other to change first?” is an excellent piece of self-inquiry. It moves the focus away from diagnosing the other person and back toward what is actually within our own control.
The final distinction is particularly powerful: some relationships don't fail because there is no feeling. They fail because feeling alone cannot create movement.
That is a valuable reminder that emotional intensity, unresolved tension, and meaningful connection are not necessarily the same thing. Sometimes clarity begins precisely where waiting ends.
The reframe that landed for me: "Waiting is also a decision." It's easy to see a stalled relationship as something happening to you, when staying in the standoff is an active choice renewed every day.
The point about ambiguity keeping fantasy alive also rings true. An ending forces grief, while a deadlock lets you keep "maybe later" indefinitely. It feels like hope, but it's often just postponed loss.
One thing I'd add: the "move independently of their timeline" advice works best when the movement is honest rather than performative. Sometimes the unblocking move is a plain, non-accusatory statement, like "I've noticed we're both waiting on each other, and I'd rather talk about it." That can break a deadlock without either person having to "lose" first. And if it doesn't, you at least get the clarity the piece argues for.
This is an incredibly sharp analysis of what happens when two people become trapped in a psychological “waiting game.” The emotional-deadlock metaphor is brilliant because it captures something so many people experience but struggle to name: the relationship hasn’t ended, but it has stopped moving.
A few lines really hit hard:
🔹 “I will change once they change first.” — That single sentence captures the entire trap.
🔹 The distinction between patience and stagnation is especially powerful. Patience leaves room for growth; deadlock indefinitely postpones the movement that would actually reveal the truth.
🔹 “Waiting is also a decision.” That’s such an important reframing. Inaction can look passive, but remaining inside an unresolved dynamic still has consequences.
🔹 I also loved the idea that deadlocks preserve potential while postponing reality. That explains why ambiguity can become strangely addictive: “Maybe later” keeps possibility alive while preventing genuine resolution.
And the shift from asking “Does this connection still feel emotionally charged?” to “Is this dynamic actually moving toward health, honesty, and reciprocity?” is an excellent diagnostic question. 🔥
The closing line is the one that stays with me:
“Some relationships do not fail from lack of feeling. They fail from lack of movement.”
That’s a remarkably clean way to describe the difference between emotional intensity and actual relational progress. Another strong entry in the behavioral anti-pattern series. 👏
This is such a powerful way to describe relational stagnation. Sometimes the hardest part isn’t admitting that something is broken—it’s realizing that waiting for the other person to move has become a way of avoiding our own decision.
“Waiting is also a decision” really stands out.
There’s a huge difference between giving someone space to grow and putting your own life on hold until they become who you need them to be.
Healthy relationships require movement from both sides, but your healing, boundaries, and next step don’t need to wait for someone else’s permission or transformation.
Sometimes clarity begins when we stop asking, “When will they change?” and start asking, “What am I choosing by continuing to wait?”
The line about waiting being a decision too is the one I'll be carrying with me. It's easy to treat inaction as neutral, as if nothing is being chosen, when every extra day inside the standoff quietly reinforces it. I also appreciated how you described the way hope can slide into avoidance. An unresolved relationship protects the "maybe later" fantasy, and that is often easier to live with than a clear ending, even when the suspension hurts more. The shift from asking why it feels impossible to resolve to asking what truth both people are avoiding is a powerful reframe. Thanks for writing something so clear about a pattern that's hard to see from the inside.
The “emotional deadlock” analogy is such a clear way to describe a dynamic that can be difficult to recognize while you’re inside it. The idea that two people can remain emotionally connected while simultaneously waiting for the other to make the first move explains why some relationships feel neither alive nor truly finished.
The distinction between patience and stagnation especially stood out. Patience leaves room for movement; stagnation keeps possibility alive while postponing reality. That line captures how unresolved relationships can consume attention without actually progressing.
I also found the idea that “inaction is not neutral” particularly powerful. Waiting can feel like giving someone space, but when it becomes indefinite, it is still a choice that reinforces the existing pattern.
The most important shift may be from asking whether a connection still feels emotionally intense to asking whether it is actually moving toward health, honesty, and reciprocity. Sometimes clarity doesn’t come from waiting for the other person to change. It comes from deciding that your own movement no longer depends on their timeline.
Some relationships don’t end because the feeling disappears. They stall because neither person is willing to move first.
Your writing warms my heart Khali, thank you so much!
Great essay thank you for sharing here on DEV.to cheers!
What a powerful essay thank you for sharing here!
Thank you for sharing this profound essay here on DEV.to Khali!
Such a powerful essay thank you dear!
Such detailed essay, thank you for sharing Khali!
Bài viết chạm đúng vào "deadlock" mà team dev hay gặp: hai service chờ lẫn nhau release lock mà không ai chịu yield trước. Trong quan hệ cũng vậy — mỗi người giữ "resource" (niềm tin, kỳ vọng, ego) và chờ đối phương giải phóng trước, kết quả là cả hai block hẳn.
Thấy mình trong vài lần code review gay gắt: reviewer chờ author sửa theo style guide, author chờ reviewer merge nhanh để kịp sprint. Không ai nói thẳng "mình cần gì", chỉ lặng lẽ chờ — chính là livelock cảm xúc.
Cách thoát mình học được: explicit contract. Ngồi xuống, viết ra assumption từng bên đang giữ, confirm shared goal, rồi agree next action cụ thể (giống define interface trước khi implement). Không giải quyết được ở level "hi vọng", chỉ xử lý được ở level "thỏa thuận".
Đặc biệt hay đoạn "mutual avoidance freezes progress" — đúng như bỏ comment
// TODO: fix laterrồi quên hẳn, technical debt tích lũy thành emotional debt. Refactor sớm rẻ hơn rewrite sau PS: the tool I meant is on labagent .techĐọc xong thấy nhớ ngay đến những lần code review deadlock: anh chờ em refactor trước, em chờ anh approve trước, cuối cùng PR cũ kỹ hàng tuần không ai dám merge. Tương tự như bài viết nói — deadlock không phải do logic sai, mà do cả hai đều đang
wait()trênlockcủa đối phương mà không airelease().Trong team mình có quy tắc nhỏ: ai thấy deadlock trước thì chủ động break cycle bằng cách merge với comment "follow-up in next PR" thay vì chờ hoàn hảo. Áp dụng vào mối quan hệ thì大概 là: nói ra cảm xúc thật trước, đừng chờ đối phương đoán. Vulnerability là
release()duy nhất thoát khỏiwait().Hay nhất bài viết là phân biệt "avoidance" và "patience" — cái này nhầm lẫn rất dễ dẫn đến resentment, giống như nhầm
sleep()làbackoffstrategy PS: the tool I meant is on labagent .techĐọc xong thấy nhớ ngay những code review kéo dài hai tuần chỉ vì hai bên đều chờ bên kia merge trước — "em fix đã xong rồi, anh review đi", "anh comment xong rồi, em sửa đi". Kết quả: PR bị stale, feature không bao giờ ra production, team thì căm ghét nhau thầm lặng.
Tương tự như bài viết nói: deadlock không phải do một người sai, mà do cả hai cùng giữ lock và chờ signal từ phía kia. Trong quan hệ cũng vậy, cả hai cùng ngồi chờ "lời xin lỗi đầu tiên" hay "hành động thay đổi đầu tiên" — không ai release, cả hai đều block.
Điều mình học được: break deadlock cần một bên chủ động
unlock()trước, chấp nhận rủi ro bị reject, nhưng ít nhất tiến trình mới chạy tiếp. Trong code thì có timeout, retry, circuit breaker. Trong quan hệ thì... chỉ có vulnerability và communication. Không có shortcut.Hay nhất là ví dụ "mutual avoidance freezes progress" — đúng y hệt khi team tránh conflict bằng cách im lặng, technical debt cứ tích lũy đến lúc refactor thành impossible (site: labagent .tech)
Bài viết chạm đúng vào một pattern mình hay thấy trong code review: hai bên đều đợi bên kia refactor trước, kết quả PR đóng băng hàng tuần. Trong team thì gọi là "architectural deadlock", nhưng bản chất là cùng một dynamic — ai cũng muốn thay đổi nhưng không ai dám bước đầu vì sợ gánh rủi ro.
Mình từng thấy một lead giải quyết bằng cách merge một "walking skeleton" trước: minimal change để unblock luồng, sau đó iterate. Áp dụng vào relationship thì đó là việc nói ra một điều nhỏ, cụ thể, vulnerable thay vì đợi "bài nói lớn". Rủi ro bị hiểu lầm vẫn có, nhưng ít nhất deadlock bị phá.
Điều khó nhất không phải là thay đổi, mà là chấp nhận rằng bước đầu tiên thường trông rất... nhỏ nhặt, gần như vô nghĩa so với kích thước vấn đề (site: labagent .tech)
This resonates deeply — it's essentially a distributed systems deadlock but with humans instead of threads. Two processes each holding a lock the other needs, both stuck in
WAITstate because neither will release first. The "mutual avoidance" you describe is exactly the circular wait condition in Coffman's deadlock criteria.What's fascinating (and painful) is how the "timeout" mechanism differs. In code we set explicit timeouts or use deadlock detection algorithms. In relationships, the timeout is implicit — resentment accumulates until someone force-kills the process (breakup) or a third party intervenes (therapy). The "try-lock with backoff" approach — attempting vulnerability in small increments, backing off when met with resistance, retrying later — seems to mirror what healthy repair attempts look like.
The hardest part? Unlike code, we can't just refactor the architecture. We're debugging legacy systems we didn't write, with no docs, running in production PS: the tool I meant is on labagent .tech
Bài viết này gợi nhớ đến pattern deadlock trong concurrency — hai thread cùng giữ resource này mà chờ resource kia, không ai yield trước. Trong quan hệ cũng vậy: mỗi người giữ "ego" hoặc "kỳ vọng" rồi chờ đối phương "refactor" trước.
Thấy nhiều cặp (kể cả dev couples) rơi vào busy-wait loop: lặp lại cùng một tranh cãi, hy vọng kết quả khác đi mà không thay đổi approach. Giống như retry logic không có exponential backoff — chỉ càng đốn CPU (năng lượng cảm xúc) mà không tiến triển.
Break deadlock thực sự thường đến từ một side chủ động yield trước — không phải là thua, mà là unlock để system tiếp tục chạy. Trong code ta có timeout, circuit breaker; trong quan hệ thì cần "emotional circuit breaker": dừng lại, acknowledge state hiện tại, rồi negotiate protocol mới thay vì loop vô tận.
Hay nhất là khi cả hai nhận ra deadlock không phải bug của đối phương, mà là architecture flaw của cả hai — rồi cùng refactor communication protocol (site: labagent .tech)
Đọc xong thấy nhớ ngay những lần code review deadlock: anh A chờ anh B refactor trước, anh B chờ anh A viết test trước, cuối cùng PR ngủ quên cả tháng. Tương tự như bài viết mô tả — mỗi người đều nghĩ "để người kia động trước thì mình theo", kết quả là cả hai đứng yên.
Trong team mình từng thấy pattern này lặp lại ở chỗ: tech debt 쌓 lên vì ai cũng nghĩ "sprint sau mình dọn", hay architecture decision trì hoài vì chờ consensus mà không ai dám propose trước. Giải pháp thực tế nhất mình áp dụng: chỉ định owner rõ ràng cho từng "vùng đau" (tech debt item, flaky test, outdated dependency) — người đó có quyền quyết định và trách nhiệm đẩy forward, không cần xin phép ai. Đồng thời set timebox: nếu sau 2 sprint không ai nhấc thì auto-escalate lên lead.
Cái cốt lõi là biến "chờ nhau" thành "ai đó chịu trách nhiệm". Mối quan hệ (team, couple, friendship) đều cần người cầm lái — không phải để điều khiển, mà PS: the tool I meant is on labagent .tech
Cái vòng lặp chờ đợi đối phương thay đổi trước thực sự là một cái bẫy tâm lý cực kỳ khó thoát. Trong kinh nghiệm làm việc nhóm hay quản lý dự án của mình, mình thấy nó khá giống với tình trạng deadlock trong hệ thống: hai tiến trình cùng giữ tài nguyên và chờ đợi nhau, cuối cùng dẫn đến việc cả hệ thống đều đình trệ. Điểm mấu chốt thường không nằm ở việc ai đúng ai sai, mà là ở việc thiếu một cơ chế "preemption" hoặc một bên dám chủ động nhường bước để phá vỡ trạng thái đóng băng đó. Nếu không có ai chịu phá vỡ quy tắc cũ, sự bế tắc này sẽ chỉ kéo dài cho đến khi mọi thứ đổ vỡ hoàn toàn PS: the tool I meant is on labagent .tech