codyde

Hi! Full disclosure - I work for LaunchDarkly. I looked after our Developer Experience team previously and now I look after our Product Incubation function, working on some of our new initiatives, AI being one of them.

We have quite a few developer teams using us for many of these use cases today. Couple of examples are concepts like controlling model functionality via JSON configs, pushing config variables in via string flags, prompt configurations, all that kind of stuff. Beyond that, teams diving into using targeting to add a layer of control over who's receiving those configurations (the beta opt in example comes up a TON).

Gap today is the "help in crafting the prompt" side of things. We're having some really cool conversations around ideas for this internally and how to make that better. Its totally doable today - the UX could just be better.

Another one that you didn't mention that comes up A LOT is measurement of the changes, and how effective they are (this is coming up A LOT with financial institutions). I.e. "If I roll out this new model, is it performing better? Are we getting better results from the new prompts we built?"

Shameless plug - I did a video on this with Amazon for Bedrock, but we did another one using LD for multiple different model providers too. Here's the link - https://www.youtube.com/watch?v=dTyxRnuI3FQ

If you have any questions, feel free to drop me a line. Happy to jump on and show you live a bit of it and answer question. It's such a great time to be building software. Can also DM me on Twitter (X, whatever) @codydearkand

Full disclosure - I work at LaunchDarkly (I look after our DevRel team) - but this is a topic I'm super passionate about also, so though it was worth sharing out. We talk about burnout a lot - but what I really appreciate about posts like this (and the report that it references) is that it gives some tangible examples of where that burnout comes from - and hopefully some paths to mitigating it.

Hope you find the read interesting!

I checked in with product on this! We're planning on supporting the OSS gateway in the future - there are some technical components were working through but its def planned!

Full disclosure - Kong employee here. The Konnect story was a huge part of why I came to Kong, super excited to see this part of it launch. I work primarily on the service mesh side of the house - but happy to help field questions around internally if anyone has any!