What's the main difference between treating AI as a tool versus a teammate?

When you treat AI as a tool, you accept whatever output it gives you and move on. But when you treat it as a teammate, you provide feedback, ask follow-up questions, and iterate together to improve the results. This collaborative approach leads to much better outcomes.

How can I get AI to ask me questions instead of just answering mine?

Simply prompt the AI to gather more context about your goals by saying something like 'Before you answer, ask me questions to better understand what I'm trying to achieve.' This flips the dynamic and helps the AI provide more tailored, useful recommendations.

Do I need to be technical to use AI effectively in my workflow?

Not at all! Jeremy's example of a National Park Service ranger who saved thousands of hours by automating paperwork shows that creativity and willingness to experiment matter more than technical expertise. The key is being open to trying new approaches.

Why shouldn't I accept the first answer AI gives me?

As Jeremy says, 'Creativity is doing more than the first thing you think of.' The first AI response is often generic. True value comes from pushing past that initial result—exploring alternatives, iterating, and asking better questions to get exceptional outputs.

How can developers specifically apply these AI collaboration principles?

Developers can treat AI like a code review partner—give it feedback on its suggestions, ask it to explain its reasoning, and iterate on solutions together. This approach works especially well when combined with effective learning strategies and mentoring practices.

What does 'inspiration is a discipline' mean in the context of AI?

It means that getting great results from AI isn't random—it requires being intentional about seeking new inputs, asking thoughtful questions, and bringing your own experience and curiosity to the collaboration. The quality of your AI outputs depends on what you bring to the partnership.

From Tools to Teammates: Transforming Your Workflow with AI (Inspired by Stanford's Jeremy Utley)

Today I took some time to watch Jeremy Utley's talk, "How Stanford Teaches AI-Powered Creativity in Just 13 Minutes". As a developer who's always curious about how technology can amplify our creativity, I found the session both practical and inspiring. Here's my point of view and the notes I jotted down—hoping these insights will spark fresh ideas for you as well.

1. AI as a Teammate, Not Just a Tool

Jeremy's central message hit home: most people still treat AI like any other tool, but the real leap happens when you start collaborating with AI as if it were a teammate. He describes how, if a tool gives you a mediocre result, you might just move on. But if a teammate hands you something that's not quite right, you give feedback, ask questions, and iterate together for a better outcome. That's exactly how we should approach AI—by coaching it, refining its output, and letting it ask us questions too.

2. Let AI Ask You Questions

One of the most actionable tips was to let AI ask you questions, rather than just firing prompts at it. This flips the dynamic and allows the AI to gather more context about your goals, workflows, and challenges. The result? More tailored, useful recommendations that go beyond generic answers. I'm definitely trying this next time I use ChatGPT or similar tools.

3. Real-World Impact: Non-Technical Wins

Jeremy shared a story about a National Park Service ranger who used AI to automate paperwork that used to take days—saving thousands of hours across the organization. The lesson: you don't need to be a hardcore engineer to make a big impact with AI. Sometimes, a willingness to experiment and a bit of creative thinking are all it takes.

4. Creativity Means Going Beyond Your First Idea

A quote that stuck with me: "Creativity is doing more than the first thing you think of." In the age of AI, it's easy to accept the first answer a model gives you. But if you want to produce something truly exceptional, you have to push past that initial result—explore alternatives, iterate, and keep asking better questions.

5. Inspiration Is a Discipline

Jeremy also emphasized that inspiration isn't just a random spark—it's a discipline. The most creative people are intentional about seeking new inputs and perspectives. What you bring to the table, in terms of your own experience and curiosity, will shape the quality of the outputs you get from AI.

My Reflections

As someone who's passionate about building maintainable, scalable solutions and mentoring others, these lessons resonate deeply. The idea of treating AI as a collaborator aligns with how I approach teamwork and code reviews. I'll be applying these insights not just in my own projects, but also as I mentor junior devs and contribute to open source.

💡 For Developers: These AI collaboration principles work especially well when combined with effective learning strategies. Check out my thoughts on rapid skill acquisition for full-stack developers.

If you're a developer (or in any field, really), I encourage you to shift your mindset: treat AI as a creative partner, not just a tool. Give feedback, ask it to ask you questions, and don't be afraid to push beyond the first answer. That's where the real breakthroughs happen.

Related Reading: Want to see AI principles applied to technical projects? Explore our Laravel & PHP tutorials where these collaborative approaches enhance development workflows.