This resonates — I build with it every day and still keep hard lines. Mine: the very first draft of anything where I’m still figuring out what I actually think (outsource that and you skip the thinking), any message that’s an apology or carries real emotional weight (people feel the generic instantly), and the final fact-check on anything that matters (I trust it to draft, never to be right). Funny how using it daily makes you more sure about where it doesn’t belong, not less. What’s the one line you’d never move?
Interesting to note the several contours of responses from AI use you have stated here, Matheus! You are right in saying that the more we use AI, the more we know when not to use it. For me, I'd always leave that first step in any workflow—be it ideation, raw insights, or my first impressions about products, models, etc— exclusively to my reasoning.
Exactly, Raghav — and I think that first step does more than produce ideas. It’s where you build the judgment to later tell when the AI is wrong. Skip it and you don’t just outsource the idea, you lose the calibration to catch a confident bad answer downstream. Guarding your own reasoning at step one is what earns you the right to trust the tool at step three. Appreciate you reading it so closely.
The line that stuck with me was "The machine doesn't know where to stop. That's your job."
Feels like a lot of AI discussions are about capability, while the harder question is still boundaries. Not what the system can do, but what it should do without us.
This resonates — I build with it every day and still keep hard lines. Mine: the very first draft of anything where I’m still figuring out what I actually think (outsource that and you skip the thinking), any message that’s an apology or carries real emotional weight (people feel the generic instantly), and the final fact-check on anything that matters (I trust it to draft, never to be right). Funny how using it daily makes you more sure about where it doesn’t belong, not less. What’s the one line you’d never move?
Interesting to note the several contours of responses from AI use you have stated here, Matheus! You are right in saying that the more we use AI, the more we know when not to use it. For me, I'd always leave that first step in any workflow—be it ideation, raw insights, or my first impressions about products, models, etc— exclusively to my reasoning.
Exactly, Raghav — and I think that first step does more than produce ideas. It’s where you build the judgment to later tell when the AI is wrong. Skip it and you don’t just outsource the idea, you lose the calibration to catch a confident bad answer downstream. Guarding your own reasoning at step one is what earns you the right to trust the tool at step three. Appreciate you reading it so closely.
The line that stuck with me was "The machine doesn't know where to stop. That's your job."
Feels like a lot of AI discussions are about capability, while the harder question is still boundaries. Not what the system can do, but what it should do without us.
Absolutely, first its critical to define AI boundaries before me move the discussion to capabilities and power of AI models! Thanks for reading, Om!