You don't need to master it. You need to understand it.
There is a quiet shift happening in how people work with technology. You no longer need to know Bash, Python, or SQL by heart to get things done. AI will write it for you. And for the most part, it will write it correctly.
I am not going to argue against that. I use it myself, constantly. But I want to make the case for something that I think gets lost in the enthusiasm: you still need to understand what you're executing.
Not write it, but understand it. The difference matters more than it sounds.
A tablespace, a well-known AI, and a near-disaster
A while back I was working with an Oracle database and needed to verify whether a particular tablespace had existed at some point. I asked an AI assistant something like: “how do I check if this tablespace existed?”
The AI came back with a DROP TABLESPACE command. Its logic was: try to drop it, and if it doesn't throw an error, it was there. As a detection method, it technically works.
Except that if the tablespace does exist, you just deleted it.
If you know Oracle, you immediately see the problem. If you don't, you paste that command into your terminal and walk away with data loss and a very bad afternoon. The AI wasn't wrong, exactly. It answered the question I asked. But it answered a slightly different version of it: one where “existed” meant “still exists now, and can be destroyed as a test.” I meant existed in the past, and wanted a safe way to find out.
That is a distinction no AI will reliably catch if you don't catch it yourself.
Understanding is the new minimum
For a long time, the basic for working with databases, scripting, or systems administration was knowing the tools. You had to learn the syntax, the gotchas, the edge cases. That bar has genuinely lowered. AI handles a lot of that now.
But the new minimum is understanding. You need to be able to read what AI gives you and know, at least roughly, what it does. Not because AI is unreliable, it is often very good, but because the failure modes are hard to spot. The command that destroys your data may look identical to the one that checks for it.
The good news is that this is a much easier bar to clear. You don't need to be able to write a Python script from scratch. You need to be able to look at one and ask: does this do what I think it does? And if you're not sure, you can ask the AI to explain it. That conversation is usually excellent.
Read what you're given. Ask for an explanation if something is unclear. Never run a command you couldn't describe in plain language, even roughly.
The blast radius of misplaced trust is real. Understanding is what keeps it small.
Written with assistance from Claude.
Want to reach out? Contact me.