| Ahah. Totally missed that, I will admit. I gratefully accept the pun and will be using it even more going forward. If you're willing to chat on the technical details of that notebook, we'd love to. Of course, if you're hoping to build it one day and don't feel comfortable sharing, understand. If yes, it's founders@getpatchwork.io :) We are definitely eyeing up what can be done when you control the log strings and the rest of the payload. And along the lines of what you say, our first step would be to see how much ClickHouse could squeeze that, and then see what other clever compression could be added in advance. Anyone crushing it in the code analysis and refactoring space is a challenger. I think for now our sense is that the full-blown agentic SWE tools have bitten off more than they can chew and aren't viewed as credible just yet. However there are people out there taking a focused, use-case-specific approach (like us) who are building impressive things. komment.ai is one that springs to mind. SonarQube looks interesting - thanks for flagging. In terms of logging stack players, we're hoping some could be friend rather than foe, at least to begin with. We thought ClickHouse might see unstructured logs as an unlock for their customers / GTM motion. However, they have invested a lot in their query-time materialisation tech, which they said their log storage customers love. Expensive, in practice, I suspect. Grafana actually pinged me yesterday. |