Three more ways of learning before you commit, and they are easy to mix up.
Spike
A small throwaway program written to answer one question, such as whether a library can do something or how a function really behaves. You keep the answer and delete the code.
Agents make these nearly free, so there is little reason to argue about something you could run in a minute. The usual failure is the spike's rough code quietly becoming the real code, so say at the start that it will be deleted.
Say it to your agent
“Spike this in a scratch folder, not in the repo: can SQLite enforce a case-insensitive unique email? Write the smallest script that proves it, run it, paste the output, and delete the script. No changes to our code.”