RUG::B

It’s unthinkable to build a piece of software without using existing libraries and frameworks.

But reusing code written by other people comes with risks. Can you trust the code written by others? Can you trust that the packages weren’t compromised somewhere along the road?

These are important questions, and increasingly important to answer satisfactorily. It’s the reason why supply-chain security is becoming more of a hot topic these days.

But this talk isn’t really about supply-chain security.

Instead, I want to ask the question: Can we create a language that facilitates safe code reuse, across an open-source ecosystem?

It's really easy to create a cool little ruby script that does something - query some API, scrape some website, transform some files, or even find a Bürgeramt appointment.

What is sometimes more tricky is organizing and running these ruby scripts. Even more troublesome is to hook them up the ever-increasing array of other technology that enables new and fancy things.

In order to get AI workflows running which needed some python scripts, but also use my own chatgpt-wrapper in ruby, I started using node-red to organize cool low-code flows that orchestrate everything.

I'd love to show off what I did, and what it can do!

A lot of talk happened recently about RailsConf trying to diversify its keynotes. I would like to give some insight into how talk selection works, how what RailsConf did is long overdue and how we - in all communities - can do better.