chrisheecho

3 ms·

1. 1.▲
   by chrisheecho 1y ago

   Thanks! - I like it too :)
2. 2.▲
   by chrisheecho 1y ago

   This sounds accurate. I see myself as a Pain Manager more than a Product manager. Product just solves the pain that users have ;) Sometimes we get it right the first time we launch it, I think most of the time we get it right over a period
3. 3.▲
   by chrisheecho 1y ago

   You don't have to specify role when you call through Python ( https://cloud.google.com/vertex-ai/generative-ai/docs/start/... ) (which I think is what you are using but maybe i'm wrong). Feel fre
4. 4.▲
   by chrisheecho 1y ago

   Can you tell me the exact instance when this happened please? I will take this feedback back to my colleagues. But in order to change how we behave I need a baseline and data
5. 5.▲
   by chrisheecho 1y ago

   ooh i like!
6. 6.▲
   by chrisheecho 1y ago

   I think you are talking about generativeai vs. vertexai vs. genai sdk. And you are watching us evolve overtime to do better. Couple clarifications 1. Going forward we only recommend using genai SDK 2. Subtle API differences - this is a bit
7. 7.▲
   by chrisheecho 1y ago

   We have Python/Go in GA. Java/JS is in preview (not ready for production) and will be GA soon!
8. 8.▲
   by chrisheecho 1y ago

   one step ahead of you ;)
9. 9.▲
   by chrisheecho 1y ago

   We have moved our quota system to Dynamic Shared Quota ( https://cloud.google.com/vertex-ai/generative-ai/docs/quotas ) for 2.0+ models. There are no quotas in DSQ. If you need a guaranteed throughput there is
10. 10.▲
    by chrisheecho 1y ago

    lemming, this is super helpful, thank you. We provide the genai SDK ( https://github.com/googleapis/python-genai ) to reduce the learning curve in 4 languages (GA: Python, Go Preview: Node.JS, Java). The SDK works for al
11. 11.▲
    by chrisheecho 1y ago

    Ramoz, good to hear that native Structured Outputs are working! But if the docs are 'confusing and partially incomplete,' that’s not a good DevEx. Good docs are non-negotiable. We are in the process of revamping the whole document
12. 12.▲
    by chrisheecho 1y ago

    That’s correct! You can send images through uploading either the Files API from Gemini API or Google Cloud Storage (GCS) bucket reference. What we DON’T have a sample on is sending images through bytes. Here is a screenshot of the code samp
13. 13.▲
    by chrisheecho 1y ago

    simonw, 'Google's service auth SO hard to figure out' – absolutely hear you. We're taking this feedback on auth complexity seriously. We have a new Vertex express mode in Preview ( https://cloud.google.com&#x2F
14. 14.▲
    by chrisheecho 1y ago

    We built the OpenAI Compatible API ( https://cloud.google.com/vertex-ai/generative-ai/docs/multim... ) layer to help customers that are already using OAI library to test out Gemini easily with basic inference b
15. 15.▲
    by chrisheecho 1y ago

    I couldn’t have said it better. My billing friends are working to address some of these concerns along with the Vertex team. We are planning to address this issue. Please stay tuned, we will come back to this thread to announce when we can
16. 16.▲
    by chrisheecho 1y ago

    simonw, good points. The Vertex vs. non-Vertex Gemini API (via AI Studio at aistudio.google.com) could use more clarity. For folks just wanting to get started quickly with Gemini models without the broader platform capabilities of Google Cl
17. 17.▲
    by chrisheecho 1y ago

    Hey there, I’m Chris Cho (x: chrischo_pm, Vertex PM focusing on DevEx) and Ivan Nardini (x: ivnardini, DevRel). We heard you and let us answer your questions directly as possible. First of all, thank you for your sentiment for our latest 2.