Got a case the catalogue doesn’t cover?
Write to me: a real use case often makes a good entry, and I answer gladly.
The entries give you the reasoning and the code. Going from there to something running in your own infrastructure, with your data and your constraints, takes more than that. And sometimes no entry matches what you have in front of you.
Either way, write to me.
What I’m interested in
A use case the catalogue doesn’t cover. You have a model call in production, or you are about to add one, and no entry addresses that need. That is exactly what the catalogue is missing: tell me which one, and it will end up there.
A reasoned disagreement. An entry recommends a level your experience contradicts. Those are the most useful messages, and they end up in the content.
An error. A snippet that no longer runs, a figure that looks wrong, a breaking point that isn’t one. Corrections come before additions.
What I don’t do here
No vendor recommendations, no reselling, and no regulatory compliance work, which is a lawyer’s job.
And no answer written in advance. If your case genuinely needs a general-purpose model, that is what I will tell you.
Writing
Say in a few lines what the task does, what runs today, and what makes you doubt it. That is enough for a first exchange.
Reviewed on