Linear is always a lagging indicator<br>remarking

Social media with text files - like twitter but by writing markwhen. Learn more.<br>Login / Sign up HomeSearch

Documentation Login

Rob Kochrob/rob

·8m<br>Linear is always a lagging indicator<br>Not to pick on linear -- any issue tracking tool that is used instead as a visibility tool by higher-ups to get a view into what their organization is doing is also lagging. If engineers used it by themselves for themselves then of course it's useful. We don't want to work on things that are already being worked on or already done.<br>But something something when a measure becomes a target it ceases to be a good measure. Now engineers are thinking about tickets instead of engineering.<br>A fleshed-out linear/jira ticket is essentially done aside from the code writing, review, and deployment. Why? Because these final steps are nearly automated for us these days. But where do you track the work that goes into writing a good ticket (aka prompt)? Is the answer ticket-writing tickets? We have offhand conversations and design reviews and 1:1s and only then, once we have some semblance of how the engineering should be done, do we cut a ticket for implementation. And even then we might not be sure of the size of the work.<br>My pet theory is that at least 50% of the work done at a large organization is internally figuring out what the organization is doing. Want to know what the status of your product development is? Have an LLM look at slack messages and google docs and PRs and review comments over time and synthesize something for you. Seems like a great business idea tbh. Someone release us from the linear expectations so we can use it as an issue tracking tool again.

Cheers

Comments

Drop files here