the other reason pouring over noval creation with ai is necessary is because then you know deeply how what you are building was created and when the time comes to automate tasks you can define the guidelines clearly in the scope of the rest of your system.
that time has come
this is a nothing ever happens post in hiding and I agree
my codebase needs a scaffolding on/off switch.
these things get pushed around so damn easy, need a mode where there is nothing that pushes then but my words and production code.
This take is really good for when you have one metric that you're optimizing for, or a couple.
Build a knowledge base for this topic. Make this number higher. Build version of this feature.
If you're innovating across the board, this is just not possible. You got to go detail by detail.
there's one thing i do with Hermes, Grok Bot and ChatGPT Dots that makes the experience 100x better...
i teach them frameworks for how to approach problems and build products
for example, i have one bot whose only job is using Compound Engineering skills with Claude Code to come up with plans and code
another one uses Karpathy's LLM Wiki concept to research topics and build a knowledge base
handing them proven concepts and methods is way easier than spending hours describing how they should work
it's the fastest way to get these agents working, and working well
Everyone's trying to sell you on process, process, process when it comes to working with AI, but it's never been more important to focus on what experience you are trying to create.
Can you feel the Interaction you want?
