I got excited reading this thinking this can help me with the SDK for a stereodepth camera I'm working with only but read then reading it's for the Next.js stack :sob:
On a separate note I like the retro DOS feel. Will probably look at this again properly when I build out the web side of my RaaS offering.
For the Camera? You don't want to know, it's a PDF that's in Chinese that for a C++ SDK in Linux!
For my future web stack the biggest chunk will probably be Daily https://docs.daily.co/reference/daily-js (by @kwindla) as the backbone of our teleoperation orchestration
Daily would be easy to add. We can technically add C++ library, but we don't have nearly enough linters in our agent even for me to trust it, so that's a task for the future!
I thought adding SDKS is something AI IDE's would be really good at it, but past the install's it usually fumbles to get the middleware/integration layer right so I think this actually makes sense. Only thing will this work for all codebases in the future? For example if I build like a CLI?
Yeah, it should work for clis, even now. For larger codebases we just need to get two things right:
- create good plans with the adequate tradeoffs for the type of service
- make sure to have enough lints and tests to verify the completion end to end, either with browser, or with typechecking or like for c++ - complex static analysis.
This is really interesting. We have a ton of integrations at my company but setting up new ones is largely inaccessible for non-engineers. Would be great if this was a full service biz solution or more self-serve for non technical users. Is this something you’re planning to introduce?
looking at being the middle layer between business integrations of different kinds in the future, starting with SDKs - this is a good idea and certainly the big vision
Yup, that's the plan! We're starting with SDKs to nail code understanding and then we'll add browser tools for traversing web uis as part of integration
We're constantly iterating on setup instructions and our repository analyzer, and during the integration we have a set of linters to prevent the model to generate completely broken code - it checks types, compiler errors for starters.
The scope of the integration is explicitly limited, we make sure that the model doesn't do extra stuff.
I got excited reading this thinking this can help me with the SDK for a stereodepth camera I'm working with only but read then reading it's for the Next.js stack :sob: On a separate note I like the retro DOS feel. Will probably look at this again properly when I build out the web side of my RaaS offering.
It's only Next.js for now, we're expanding the library, what's the SDK you want to use? We can add it for you!
For the Camera? You don't want to know, it's a PDF that's in Chinese that for a C++ SDK in Linux!
For my future web stack the biggest chunk will probably be Daily https://docs.daily.co/reference/daily-js (by @kwindla) as the backbone of our teleoperation orchestration
Daily would be easy to add. We can technically add C++ library, but we don't have nearly enough linters in our agent even for me to trust it, so that's a task for the future!
I thought adding SDKS is something AI IDE's would be really good at it, but past the install's it usually fumbles to get the middleware/integration layer right so I think this actually makes sense. Only thing will this work for all codebases in the future? For example if I build like a CLI?
Yeah, it should work for clis, even now. For larger codebases we just need to get two things right: - create good plans with the adequate tradeoffs for the type of service - make sure to have enough lints and tests to verify the completion end to end, either with browser, or with typechecking or like for c++ - complex static analysis.
Lukas here, would love to answer any questions there :)
[stub]
This is really interesting. We have a ton of integrations at my company but setting up new ones is largely inaccessible for non-engineers. Would be great if this was a full service biz solution or more self-serve for non technical users. Is this something you’re planning to introduce?
looking at being the middle layer between business integrations of different kinds in the future, starting with SDKs - this is a good idea and certainly the big vision
Yup, that's the plan! We're starting with SDKs to nail code understanding and then we'll add browser tools for traversing web uis as part of integration
This is amazing and excited to try this on my personal projects :) thanks for the link!
All of our customers use AI to integrate our SDK anyways so this makes sense
would love to chat, maybe we can add support for your SDK into sourcewizard so your customers can setup directly using that?
How do you know this is not "helpfully" breaking my set up?
We're constantly iterating on setup instructions and our repository analyzer, and during the integration we have a set of linters to prevent the model to generate completely broken code - it checks types, compiler errors for starters. The scope of the integration is explicitly limited, we make sure that the model doesn't do extra stuff.
I refuse to use `npx` on my personal machine. So what now?
What do you prefer? We can use bun and provide a static binary https://bun.com/docs/bundler/executables, would that work for you?
Oh thats useful!! Why is there so little packages? Ill buy 30$/month easily if you can get all packages i use
We're working on adding more packages! Is there anything specific you need? We can add as well
ok that looks very cool. When will you release more providers?
We're working on adding popular libraries, but if you have a specific library, we'll be happy to add it!
pretty cool stuff! will book a demo