Discussion about this post

User's avatar
juluc's avatar

What I find most important is to carefully build rich context at the beginning of a session. I often record myself for 5-10 minutes, transcribe these thought traces, and use them as rich contextual input.

I'm not just transferring the goal "research market X", but making the model aware of its persona, the meta-context (e.g., you are the systems architect and we're building a system that needs this market research to integrate into Part Y), and all the artifacts it will need. I think of these artifacts - repos, documents, research papers - as "packages" that I import, referencing them from the very first audio - Opus is INSANE at connecting the dots here (you know better than I do why probs - would love to hear your best guess.)

I.e., I create a context-rich waterfall where instead of dumping all context at once, I carefully curate it until I reach a state where the model is fully aligned. Then I, if needed for my task, let it generate a sample workflow (usually editing my prompt 3x to sample different approaches and select the best one). After that, I prompt it to execute.

Most of the time I'm just copy-pasting between AI systems, occasionally checking implementations and watching for drift. When context ends, I "export" the current state with nuanced variations:

Export state (general)

Export state focusing on high-level goal and role

Export state focusing on mental model of the task

Then I start a new session, building this cascading context again. Works like magic.

So if future models can handle this calibration themselves (and I just approve) and communicate with other system parts using a systematic approach (honestly, it would probably already work with the right scaffold), then my only role would be to pre-define critical checkpoints and tell the model "notify me when you complete X" or "I need to review output Y." I'd leverage my domain knowledge to identify what needs human validation, then check and steer as needed.

Right now, I'm the glue & bottleneck.

Worth noting: I work as a solo operator, which gives me the flexibility to rapidly iterate on these workflows and experiment with different approaches. This kind of human-in-the-loop orchestration might face different challenges in larger organizational contexts, but the principles should transfer (?)

Expand full comment
2 more comments...

No posts