If 1) you’re smart or practised enough to be able to generate what you’re asking the AI to do for yourself, 2) you’re able to take what the AI generates and debug, check and correct it using non-AI tools like your own brain, 3) you’re sure this whole AI-inclusive process will save time and money, and 4) you’re sure using AI as a crutch won’t cause you brain-rot in the long term, go nuts.
Caveat: Those last two are tricky traps. You can be sure and wrong.
Otherwise, grab the documentation or a bunch of examples and start hacking and crafting. Leave the AI alone. Maybe ask it a question about something that isn’t clear, but on no account trust it. It might have developed the same confusion that you have for precisely the same reasons.
So anyway, Linus clearly fits 1 and 2, and believes 3 and 4 or else he wouldn’t be using an AI. Let’s just hope he hasn’t fallen into the traps.
history | grep -E '(sed|grep|awk|perl)' | wc -l107Dang. That’s out of 1000. I need to up my game. Also three of those
seds are part of something with a-basedirand don’t count.So yeah, about 10% of my commands are iterating shell pipe things for poops and giggles, I guess.
… and this got me going down the rabbit hole of writing a filter for my history to pull out the first command on the line. This is non-trivial because of potential preceding variable assignments. Most used commands are currently
aptandmanandls. I thinkaptis a Spiders Georg situation because the system is fairly fresh and I keep finding things that I haven’t installed yet. Also I went through a patch of trying to parse its output.… oh, er… unga bunga.