I found this to be a difficult read, and quite repetitive in sentence structure. (Ctrl+F says 25 instances of ":" on this page!)

It sounds like the product is intended to help you avoid performance-related regressions, and argues that the risk of performance regressions will increase with AI writing more code. That seems plausible, but it's unclear how or why this product is superior to existing performance testing as part of your CI/CD pipeline.

▲

mstkllah 2 days ago | parent | next [-]

Those 25 instances of ":" are probably caused by author telling their LLM to replace em dash with colon.

	▲	specproc 2 days ago \| parent [-]
		The writing is hideous, I can see that being the case.

▲

tsenart a day ago | parent | prev [-]

Hi. Performance testing in your CI/CD pipeline will catch performance regressions of what your team has covered with benchmarks or load tests. Anything else will fall through the cracks.

Even the most capable performance conscious teams in the world still have limited attention. Perfloop has been contributing significant performance improvements to the open source world too, across repos like ClickHouse, Prometheus, parquet-go, roaring bitmaps and more.

https://github.com/search?q=is%3Apr+is%3Amerged+author%3Aper...