> What stops any business from over-charging? Competition.
I fully agree.
> It's the same conflict of interest quite literally any business has.
I know that you know what I meant ;)
In the long term it is just as you say - overcharging (eventually corrected by competition forces), but in the short term it can be additional revenue, blamed on a bug, but making some manager look good.
Flip side is customer psychology. Choosing a more expensive tier leaves better emotion.
Also i doubt there was jira ticket with “make llm more verbose”, rather ticket with “bug makes llms too verbose” gets prioritised taking revenue impact into account.
1. I think burden of proof is on the opposite side. (Previous legislations/directives were circumvented without problem)
2.Asking for hard evidence of top spies secretly spying on heads of other states is … (not sure if there is a word for it; some blend between: unrealistic, unreasonable and oxymoron’ish. If they do their job well, you will not find it out, also it might be illegal or punishable to present such evidence)
Good architecture reduces cost, while still achieving business goals.
(E.g. If you have problems hiring for a weird stack, it increases hiring cost; you have problems with dependency zoo maintenance it increases costs; if it took a year to build a framework that could've been a bash script, it increased the cost)
Every other architecture “metric” should be useful/convenient proxy towards reducing overall cost.
If parsing fails - how often can you do anything else than just abort and log/show an error..
Checked exceptions are nice in theory, but it is very context dependent if checked’ness is useful, I would prefer that libraries do not expose them.