A bit of a rant. Sorry!
With the probablistic pluggable 'brain' existing in parts of the solution how are you measuring anything is better or worse?
I am at a loss to quantify whether anything is improving or worsening anything. It probably is also because of the various metrics that keeps popping up
* Accuracy
* Cost of running
* Context
* Size
* Time
* Turns
all these vary in a large band even with the same 'brain' on the same 'provider'. It is not so different than a database running strained under load - drawing from a simpler times. But here, which elastiuc band is getting pulled in which direction is worse than playing 3D Tetris.
Then there is the harness side variability of tool choices. Which seems to be the only knob the developer these days seems to have some control over. Other than the deterministic parts of the system.
How are we even going to triage a ticket with so many variabilities. In a runtime. That apparently is still called a software.
Do we just tell the users that you are on your own and whatever you need to solve is between you and your brain of choice?
What are you doing?
Comments URL: [https://news.ycombinator.com/item?id=48696916](https://news.ycombinator.com/item?id=48696916)
Points: 1