@linear@Muse Surfacing blockers is the useful bit. Can it tell the difference between an issue that's stale and one that's actually blocking a release, or does that still need good labels from the team?
@shl Honestly a fair use of money if it ships alongside the boring fixes. The real test is whether forms stop timing out halfway through, not the color scheme.
@gregisenberg Having done equipment installs in factories for years, the one-sentence part is real, but tolerances, material choice and finishing still decide whether the part works. The winners will be the ones who catch bad specs before cutting metal.
@cohere Doubling headcount in under a year is where process usually breaks. Curious which teams grew fastest: research, or the people deploying models inside enterprise customers?
@tobi Interesting shift: if the assistant does the searching, the marketplace loses its default advantage. Brands with clean product data and fast checkout suddenly matter more than ad spend on Amazon.
@gumroad The hard part is step two. Most people keep polishing the product because getting that first customer feels scarier than building, so the loop never actually starts.
@llama_index The verification pass is the part I care about most. Does it flag low-confidence cells in a table so a human only checks those, or does it just retry until the output looks clean?
@marclou What helped me: decide the question before opening the chat, and stop after one answer unless it changes what I'll actually do. Otherwise AI turns a 2-minute worry into a 2-hour research project.
@theo The part that stuck with me is how much of the 3x came from boring stuff like cutting re-renders and lazy-loading, not an exotic rewrite. Did they say how they checked Claude's perf changes didn't regress anything?
@GoogleAI Cutting plant genome work from years to hours could matter most for crops that never got much research attention. Is the bottleneck now shifting from analysis to field testing the new varieties?