Instead of asking an AI to directly build something, the more effective approach is to instruct it on *how* to solve the problem: gather references, identify best-in-class libraries, and create a framework before implementation. This means working one level of abstraction higher than the code itself.
Using AI to code doesn't mean sacrificing craftsmanship. It shifts the craftsman's role from writing every line to being a director with a strong vision. The key is measuring the AI's output against that vision and ensuring each piece fits the larger puzzle correctly, not just functionally.
The most significant productivity gains come from applying AI to every stage of development, including research, planning, product marketing, and status updates. Limiting AI to just code generation misses the larger opportunity to automate the entire engineering process.
A powerful workflow is to explicitly instruct your AI to act as a collaborative thinking partner—asking questions and organizing thoughts—while strictly forbidding it from creating final artifacts. This separates the crucial thinking phase from the generative phase, leading to better outcomes.
High productivity isn't about using AI for everything. It's a disciplined workflow: breaking a task into sub-problems, using an LLM for high-leverage parts like scaffolding and tests, and reserving human focus for the core implementation. This avoids the sunk cost of forcing AI on unsuitable tasks.
Vercel designer Pranati Perry advises viewing AI models as interns. This mindset shifts the focus from blindly accepting output to actively guiding the AI and reviewing its work. This collaborative approach helps designers build deeper technical understanding rather than just shipping code they don't comprehend.
The early focus on crafting the perfect prompt is obsolete. Sophisticated AI interaction is now about 'context engineering': architecting the entire environment by providing models with the right tools, data, and retrieval mechanisms to guide their reasoning process effectively.
The most effective way to build a powerful automation prompt is to interview a human expert, document their step-by-step process and decision criteria, and translate that knowledge directly into the AI's instructions. Don't invent; document and translate.
A powerful but unintuitive AI development pattern is to give a model a vague goal and let it attempt a full implementation. This "throwaway" draft, with its mistakes and unexpected choices, provides crucial insights for writing a much more accurate plan for the final version.
Instead of allowing AI to atrophy critical thinking by providing instant answers, leverage its "guided learning" capabilities. These features teach the process of solving a problem rather than just giving the solution, turning AI into a Socratic mentor that can accelerate learning and problem-solving abilities.
For complex, one-time tasks like a code migration, don't just ask AI to write a script. Instead, have it build a disposable tool—a "jig" or "command center”—that visualizes the process and guides you through each step. This provides more control and understanding than a black-box script.