Coding Is Solved, Yet the Backlog Remains
A viral post asked why, if coding is solved, we still coordinate work in Linear and Jira. Someone else shut their workspace down entirely. Meanwhile others were spinning up twenty Linear issues per feature and handing them to agents.
What people were saying
The day belonged to a question nobody at Linear asked. @dremnik posted what he called the great paradox of the moment: everyone says coding is solved, and yet we still use Gmail, still use Slack, still coordinate tasks in Linear or Jira. It picked up 1,300+ likes and 300+ replies, which is a lot of engagement for a post whose thesis is that nothing is happening.
Running alongside it, a smaller but sharper version. @euboid said he shut down his Linear workspace after five years, arguing that for small teams the issue tracker was always the middle ground between "urgent enough to hand an agent right now" and "needs real product thinking," and that middle ground has collapsed. His agent workspace is the tracker now: what's running is what's being worked on.
The counterargument arrived hours later and louder. @AlexFinn described a workflow where you let a model interrogate you with a hundred questions, then convert the plan into 20+ Linear issues and say "ok work on the next thing" until the feature exists. He called Linear a second brain. Same technology, opposite conclusion: one person deletes the tracker because agents make it redundant, another keeps it because agents need somewhere to be pointed.
@RHLSTHRM supplied an accidental tiebreaker by listing the software OpenAI still pays for, Linear among it, on the theory that generating code was never the expensive part.
Notable anecdotes
@utekkare mapped out a fully autonomous loop (Cursor writes the tickets, Codex verifies, Devin ships PRs, everyone comments back on the Linear issue) with zero humans in the loop and a $600/month subscription budget. @ToriSeidenstein turned a Product Hunt launch into 49 Linear issues and came in second. @DanKornas open-sourced a local dispatcher that pulls tasks from Linear by default and gives each one its own git worktree and agent pane.
The praise
@_drankou discovered that swapping the GitHub domain in a PR URL drops you straight into the Linear diff viewer, and built a Raycast shortcut around it. Both @karrisaarinen and @artman amplified it, which is the polite way a company says yes, that was on purpose.
On the team side, @emilkowalski shipped a very small fix: toasts no longer cover the Linear Agent chat, and now move when the chat opens. @zenithquinn noted it went from a tweeted suggestion to shipped in under a day. @dizaytsev posted Linear Diffs on a very wide monitor, and @Griveau started a small bit about whether a UI screenshot is an Ableton session or a rendering optimization brag, which @penzington answered with "why not both."
Interest over time
Updated at 9:09pm ET. Posts published later appear on the Posts tab.