signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Any conversation
"200K lines is not 10 times as much as 20K lines - from the mission perspective it's just irrelevant. And yet it's the easiest thing to measure. And so we look for the keys under the lamp post." ~Kent Beck
www.youtube.com/watch?v=F8fBgDCf2Y4&t=2753s
New in agenttop.dev : panels open in your . ๐คนโโ๏ธ
โข Any panel can now split into its own pane, live, beside the table.
โข Works with all the popular multiplexers: , , ๐ฎ๐ป๐ฑ ๐ธ๐ถ๐๐๐.
โข run a panel on its own: agent-top mcp, agent-top slow, agent-top fails, agent-top advice.
โ The # MCP panel also lists the orphaned MCP processes that outlived their agent and are still eating memory.
Added it as a company on LinkedIn so it must be 'live' now. Cheltenham-od.uk

