Two techniques for staying in flow with AI: version everything you make, and treat context as a collection of artefacts.
TL;DRArtefact Driven Development
Two critical techniques to maximise flow when working with AI:
- Artefact Driven Development
- Context Management
Artefact Driven Development
Decades of nightmares developing software by hand (and not AI) has taught software engineers this incredibly easy but hard lesson: Backup, version, backup, version, backup, version.
Context Management
No one can guarantee a great response from the LLMs. All these people claiming to be prompt kings are just good at English language. And we know your prompts are cool and all, but really context is everything.
Not to mention how these techniques allow you to not be tied to one LLM/AI provider. I can shift from GPT to Claude in seconds because my context and artefacts are all transferrable.
So what are Artefacts, and what is Context?
A ppt is an artefact. The excel from which the numbers are populated on the ppt is an artefact. The logo of your company and your brand content are artefacts. And Context, well it’s nothing but a collection of Artefacts.