Blacksmith (W24) is building a faster cloud for continuous integration (CI), helping developers test…
@ycombinator1.7M followers
39,651 views
24 Comments
Comments from the original post on X (Twitter)

@chrisreedbates
Curious if CI will continue to be a thing going forward?
2 likes

@lokidotdev
"testing is the new bottleneck" is so real. agents write the code in 2 minutes and then everyone waits 20 for CI
2 likes

@bodimog
Very cool.
1 like

@Bijan_Automates
As coding agents spit out more diffs the bottleneck moves to tests Cutting CI from minutes to seconds is the unlock for agent loops Would you pay more for faster green builds than for a smarter model right now
1 like

@jatingargiitk
CI in seconds gives agents a chance to fix a failing change before they build more code on top of it.

@cheneypiano
I'm already seeing this. The code shows up faster than anyone can check it, so testing becomes the real bottleneck.

@sagivo
At what point does CI in seconds stop mattering for me if the agent keeps writing the next change while the last one is still being checked? I want the agent to wait for the result before it builds on top of a failing change.

@chenzhangreal
testing being the new bottleneck tracks, ai spits out code way faster than we can verify it works

@Monetisedev
Reviews and validation are the headline issues now. And as agents move from writing code to executing entire workflows, the next question is whether all that autonomous work is actually worth the cost.

@Mahone_AI
makes sense. agents write the code in 2 minutes and then everyone sits around for 20 waiting on ci

@DavidWever
Shorter test runs make it easier for an agent to work in small steps. When something breaks, there's less new code to untangle.

@cz4000
from Minecraft servers to unicorn, love it!

@nirajkvinit
Code review used to be the bottleneck, then CI (My biggest Infra spend), and soon it'll be the poor human reading the release notes. 😂😂 What do you think breaks next once tests are basically instant?

@davidarngar
Using gaming-grade CPUs for early infrastructure is a clever starting point. It’s a good reminder that infrastructure innovation doesn’t always require purpose-built hardware.

@Studio1HQ
we know a thing or two about helping dev tools find their developers 👀

@edugiansante
we saw this exact pattern at persona haha , the faster code gets written, the more testing becomes the thing people actually complain about at dinners

@iamayushrawat
AI made writing code cheap. Now the real bottleneck is trusting what shipped.

@jeffbruchado
if your suite is mostly single-threaded, a gaming cpu can beat a server with way more cores, because the wait comes down to per-core speed

@gaurav0bhowmick
faster CI helps. the harder problem is tests that actually check behavior, because agents are very good at writing tests that just pass

@aapakari
Were the first 200 customers indie devs or enterprise teams?



