I’ve been doing this for the past 10 years or so. When I joined my current company a few years ago, it was one of the first things I pushed for. It made cycle times go down drastically and value is being delivered to end users at a much higher rate now.

With enough tests and automation, there is almost no reason not do on the web. On embedded or mobile platforms this might be a bit more difficult, although not entirely impossible.

The use of feature toggles also greatly enhanced our trust in being able to turn a feature off again if it turned out to be faulty somehow. Although we usually opt for patching bugs, it gives the business as a whole more confidence.

We’re using backstage in combination with openapi. The schema is documented in OpenAPI, but how services are connected is done via backstage, which crawls all repositories and puts it together to form nice graphs we can traverse easily

Even after reading both the blog and the website itself I still have no idea what this is supposed to be? Is it a standalone git client that tries to do things differently? Is it a GitHub alternative? I’m super confused

Absolutely this. I didn’t have either of those, but successfully used a Windows virtual machine on my Mac to do it

Controversial opinion maybe, but: pay for your apps/subscriptions. The makers need to feed their families as well. If you don’t want to pay big corporate, or the app doesn’t offer an ad-free alternative, switch to an indie alternative instead. If you can, pay for a lifetime plan.