Thanks again to Cornelius Schramm and Maximilian Gebhard for sharing their experience and feedback on FINN with us. For the full presentation and more details on their takeaway, head over to our community 👇 community.ncscale.com/c/reso… [End of thread]

3️⃣ use naming conventions, standardized logs, and trace ids to monitor and debug your application effectively 4️⃣ build lots of interfaces to avoid people working in the data layer

Their takeaway from their experience: 1️⃣ make your app modular by building a network of processes that trigger each other based on relevant events 2️⃣ automations should behave like small APIs with Payload validation, error handling and http responses to orchestrate your network

But with a fast development came the first issues and the need to: 🐞 keep control over every single bug in the process chain 📋 keep track of changes and implement a proper approval flow 📄 keep track of workflows 🔒 secure the app to its maximum

No-code allowed FINN to develop at a quick pace with efficiency through faster implementation and iteration cycles.

FINN is an online car subscription service Their model is a no-code stack of ▶️ @make_hq ▶️ @airtable ▶️ @retool ▶️ @nocodb with +3k active Make scenarios +30k Make executions/day ~300 no-code suite users creating a 1st class digital customer journey in a rusty industry