Last night I was nearly tearing my hair out trying to get a crappy inkjet printer installed when I turned to ChatGPT for help; 5 minutes later it was done (driver issues).
I realised that I use it a lot for all sorts of things but haven’t really seen any posts on here about it, and was wondering if other people do the same.
I’ve used it to create bash scripts, write small, niche python programs (eg sort photos into separate folders based on their orientation), and create cron jobs among other things.
In particular, I find it useful when I want to use a command line program that has a complicated set of options / syntax, but I might only ever want to use it once, or very infrequently. So I tell it what I want to accomplish, and ask it to give me the correct command to run with the options I specify in plain language.
Example:
User
Give me the correct rsync command to recursively copy all files in /home/user/Documents that are image files of any type but were created more recently than 1/1/2024. The destination is /home/user/foo
Break down the command and explain each part of it in dot point format.
ChatGPT
- rsync`: Invokes the rsync program, which is used for efficiently transferring and synchronizing files across systems or within a system.
-avm:
-a: Archive mode, which preserves permissions, symlinks, modification times, group, and ownership. Implicitly includes recursion.
-v: Verbose mode, which provides detailed output of what rsync is doing.
-m: Prune empty directory chains from the file-list.
--include='*/': Include directories themselves, which is necessary for recursion.
--include='*.jpg' --include='*.jpeg' --include='*.png' --include='*.gif' --include='*.bmp' --include='*.tiff' --include='*.svg': Include files that match these image file extensions.
--exclude='*': Exclude all other files that do not match the previously stated include patterns.
--prune-empty-dirs: Exclude empty directories that result from the inclusion/exclusion pattern.
--min-age=$(date -d '2024-01-01' +%s): Exclude files that are older than the timestamp for January 1, 2024. This uses date -d to convert a date string into a timestamp, which rsync uses to filter files.
/home/user/Documents/: Source directory from which files are being synchronized.
/home/user/foo/: Destination directory to which files are being synchronized.`
It’s also really good for explaining concepts / commands in plain language.
It’s like having a 24 hour on call Linux expert :)
#Things to note:
- Get the subscription. ChatGPT 3.5 is pretty useless. ChatGPT4 is fine, but I’m pretty sure you need the subscription to access it.
- Give it pre-instructions. I have told mine what distro, what shell I’m using and the make and model of my laptop. If you have a subscription you can add these as permanent pre-instructions, so to speak. That way it will be much more likely to give you correct answers.
- It’s not magic In order to get what you want, you have to be able to ask the right questions. It will boost your ability but won’t turn you in to a 1337 haxx0r
-Ask questions As always, don’t run any commands that you don’t understand. Ask it to break down any commands it tells you to run if you don’t understand them.
-Sometimes it goofs For various reasons, sometimes it will ask you to install a package that no longer exists, or will give you a command that doesn’t work. When that happens, I just feed the error message back into ChatGPT and it usually is able to correct itself.
-Ask “Is there a better or easier way to do this?” This is probably the most valuable question I’ve found to ask chatGPT. Sometimes it gets so far in the weeds looking for a solution to a problem that you need to pull back and start fresh.
I'll confess that I only tried gpt 3.5 (and the mistral one but it was actually consistantly worse) given that there's no way in the world I'm actually giving openAI any money.
Having said that I don't think it fundamently changes the way it works. Basically I think it's fine as some sort of interactive man/stackoverflow parser. It can reduce frictions of having to read the man yourself, but I do think it could do things a lot better for new user onboarding, as you seem to suggest in the comments that it's one of the useful aspect.
Basically it should drop the whole "intelligent expert" thing and just tell you straight away where it got the info from (and actually link the bloody man pages. At the end of the day the goal is still for you te be able to maintain your own effing system). I should also learn to tell you when it actually doesn't know instead of inventing some plausible answer out of nowhere (but I guess that's a consequence of how those models work, being optimized for plausibility rather than correctness).
As for the quality of the answer, usually it's kind of good to save you from googling how to do simple one liners. For script it actually shat the bed every single time I tried it. In some instances it gave me 3 ways to do slightly different things all in the same loop. In other straight up conflicting code blocks. Maybe that part is better in GPT 4 I don't know.
It also gives you outdated answers without specifying the version of the packages it targets. Which can be really problematic.
Basically where I'm going with this is that if you're coding, or maintaining any server at all, you really should learn how to track the state of your infra (including package versions) and read man pages anyway. If you're just a user, nowadays you don't really have to get your hands in the terminal.
At the end of the day, it can be useful as some sort of interactive meta search engine that you have to double check.
I'm really not getting into the whole "automated garbage that's filling up the internet, including bug reports and pull request" debate. I do think that all things considered, those models are a net negative for the web.
As an example of what's possible with GPT4. Client wanted DNS auth in Letsencrypt instead of HTTPS, so we can close incoming port 80. They're using a registar with a proprietary API. With ChatGPT I created a certbot plugin in about 10 minutes, feeding it a pdf with API description.
I know how to do every step of this myself, but it's a 4-8 hour task to research the registar's API and how certbot plugins interface. Instead, I took another 15 minutes to review the code, ran it, and it's done.