I think a lot about the low code side and how we can make that work...at the end of the day that looks like a feature/integration into other platforms and that means a lot of matching opinions/interfaces.

I think K8s ecosystem did this well but it required big cross-enterprise working groups that produced things like CSI, SMI, OCI, and before that could happen, there was like 5+ years of storming and forming that had to happen before the dust settled enough for enteprises to step forward and embrace k8s/containers as the new compute paradigm

maybe i'm overthinking things.

onto the coding things -

> clever architecture still tends to beat clever coding

love this

> best code often is the code that’s not written and not maintained

it's too bad not-writing-code isn't as satisfying as deleting code

> it’s developments 5th or 6th version creating major overhauls

yeah the best agent orchestration architecture I'm aware is on interation 4 going on 5. I told him to open source it but he said "its .NET so if I open source it, nobody will care" XD

> There is agentic ai and human in the loop to still figure itself out, as well as how to improve the existing processes. 2025 looks to be interesting.

i'm stoked for it

Maybe piggybacking on existing platforms is a way to go. You already have an API, maybe tying in a few major orchestration platforms like Zapier, n8n, make.com, and maybe even IFTTT, etc in one fell swoop would be a nice start to make it easier to tie in. Since you're into python, something like node-red might not be bad either.

There are lots of other process managers that could fit well with agents as well, python and not that could be reasonable bolt-ons or extensions.

I'd be very happy to check out the best agent orchestration architecture you're referring to, email is in my profile if easier :). 1

In terms of open sourcing, I don't think anyone would have an issue with .NET, I wouldn't. Many businesses have exposure to Microsoft 365 already and using Azure, kind of a massive built in audience.