Posted on
in
Software Engineering
• 2019 words
• 10 minute read
Tags:
AI, LLMs
The chat-based workflow encouraged by existing AI harnesses results in a fragmented source of truth for the desired functionality of the software.
To centralise the source of truth, we should use Markdown as Source (MaS). We should adopt a Specify, Generate, Inspect, Loop (SGIL) workflow which puts human-written Markdown files stored in source control front-and-centre.
My Current AI Workflow
I hate my AI workflow. I don’t know how everyone else is using AI, but currently my workflow looks something like:
- Open Claude and type a chat message indicating what I want it to do.
- Look at the code or plans it generates and test the functionality of the code it produced.
- Type a chat message clarifying my ask or correcting the AI’s assumptions. Normally this involves telling it what I dislike about the code it generated.
- Go to 2.





