Arch Forum 2025-09-11¶

Participants: Backend devs, Andy, Kyle, Magnus, and Victor

Agenda¶

Martin gave a demo of how he uses AI (Cursor and Warp).

Discussion followed, with notes below.

AI tool usage is quite varied among backend developers. Tools mentioned:

We want to encourage sharing of rules/instruction files, so that not everyone needs to re-invent their own.

Often every tool has its own conventions, but much of the actual content is universal for all of backend.
As a start, it would be great if we just shared in Slack.
Maybe some general rule file can be generated from be-docs, but summarized (Can AI summarize it?)

While there is no comprehensive AI guideline document, some common sense guidelines are:

Developers are encouraged to use AI to improve efficiency and quality.
Developers are encouraged to experiment with AI tools to learn and explore new ways of working.
AI tools are not different from other tools when it comes to confidentiality.
- You are responsible for what data you share.
- When using tools outside those Majority has a business account with, you need to be extra mindful of their privacy policy.
- Many tools train on data you give them in their free/trial tiers.
- Be especially careful with any extra sensitive data, like secrets or PII data.
The expectations and responsibilities of the developer are not affected by the use of AI:
- The developer is as responsible for code they write and commit manually as for code generated and committed by their AI tools/agents.
- The developer is as responsible for code they review manually as for code reviewed with the assistance of AI tools/agents.
- The standard is as high for AI-generated code/actions as for those done manually.

Now written here: AI Usage

Service team already has an action point to look into generating docs for an area.
Can docs be generated once a week to be kept up to date?
Can docs be generated on demand?