Slack Threads Will Not Solve Complex Problems
Complex technical problems often need calls, diagrams, and shared context rather than endless Slack threads or PR comments.
Slack threads will not solve complex problems.
People will.
I have seen the same pattern on too many projects. A complicated issue appears. Someone opens a Slack channel, a private group DM, or a long Jira thread. Suddenly everyone is trying to explain architecture, edge cases, intent, history, and half remembered business rules through walls of text.
That works for about three or four messages.
Then it breaks down.
The hardest thing in software
The hardest thing in software is understanding what someone else is thinking.
The second hardest thing is explaining what you are thinking clearly enough that they understand it the same way.
Text is useful, but it flattens systems. It hides the shape of the problem. People start arguing over sentences when what they actually need is a shared picture.
So the fix is often painfully simple.
Stop typing. Get on a call. Open Miro, FigJam, Excalidraw, or literally anything that lets you draw boxes and lines. Show the system. Show the data flow. Show the edge cases. Get everyone looking at the same picture.
PR reviews have the same problem
The same applies to pull requests.
If a PR is bouncing through multiple rounds of comments and people still misunderstand the intent, do not keep pushing more commits and replying in GitHub like the next paragraph will magically fix it.
Jump on a pairing call.
Open the codebase. Talk through the problem, the intent, the current approach, the edge cases, and whether the solution actually solves the issue.
That thirty minute call can save two days of comment archaeology.
Documentation is not alignment
Documentation is great for history. Text is useful for context. Tickets are useful for tracking.
But alignment often happens in conversation.
And when words are not enough, draw boxes and lines.
This sounds obvious. It still does not happen enough.
As developers, it is easy to hide behind Slack, Jira, GitHub comments, documentation, tickets, and long message threads.
Sometimes the fastest way to solve a complex technical problem is also the simplest.
Speak to another human being.