“Time to 200”? Why not “Zero to 200”? Feels closer to the car simile
That feeling of not being sure if a tool/API/service/SDK/library/hardware is going to work for your purposes and then you get that first example/test/demo running and get your first response...
"Ok, yep, this is good! Now is it gonna let me change this small thing so I can..."
And the positive feedback loop has begun!
It's definitely a metric that impacts developer adoption & is IMO something that needs to be routinely tracked in order to reduce the time taken to get started & catch any unexpected regressions.
* Zero is not a HTTP return code
* You don't want to get all the returen codes up to 200, as you'd get with speed. You want HTTP 200 OK and nothing else.