I wouldn't wrote as it, sorry, the post was an unintended generated post, wasn't supposed to post for real, until i was going to rewrite it by hand at least.
The meaning for that sentence is that litellm just route requests, it doesn't execute a model.
it's funny I quite like this blog post so I also read the previous post on that blog. And it said:
"It won't replace your staff engineer. It replaces the forty minutes before they open the tab. Your branch rots while someone's in a meeting three timezones away. The bot comments in ~30 seconds. You fix it while the code is still loaded in your head."
And also to think in different directions than you would have gone in isolation. Regardless, this is a great heuristic / rule that I will be sharing and keeping in mind.
Sir, you have a knack for inspiring commentary: the exact opposite of damning with faint praise! Also 0% slop it made me pre-order the book immediately.
I think there is a better way: The colder something is, the less sweet it will taste. if you warm-up ice cream and taste how sickeningly sweet that soup is, you won't be having so much for a while...
Deterrence is exactly what we should be doing. Many responses here were some variation of "he'd never try" or "let him try, we'd win". That's not deterrence - that's ignorance and provocation, respectively.
This is the Claude-ism that I despise the most, when it states something that was never asked because it leaked from the prompt/context. Claude's writing has regressed so much, it's only usable for "raw coding" now.
...and you're right, it's not the idiosyncrasies, it's the fluffy meandering meaningless purposeless vapidity.
reply