Have you ever seen a book about a Windows app? 1200 pages, 1000 of them screenshots.

An insane way to do computing.

its how we roll in Windows land, GUIs over command line mostly

true, you need some screenshots to teach someone a new trick

but then when they've done it once they'll remember it because GUIs really help for that kind of stuff

whereas for command line you'll have to google it every single time for the rest of your life unless its something you do regularly

...Or just commit the terminal commands and/or resulting dotfiles to git.

Which the GUI paradigm has no built in equivalent to

Equivalent GUI paradigm : macro recording?

Not really, at least not in Windows. There are no cross-application macros in Windows, just intra-application ones, and that only for some applications.

It is a little better on MacOS with AppleScript, which can be used to bind different applications together. But not all of them, and it is far from ideal.

In the end, nothing of this is command-line equivalent.

Btw, if you want to see a GUI application that can do really really good macros, learn Blender! E.g. you can bind any button and knob to keyframes to change them in animations. That would be the level of macro-integration required to be CLI-like...

I rather roll with Xerox, Dec, Apple and ETHZ way of computing with OLE Automation, COM, WMI, .NET, VBScript and PowerShell REPLs and scripts.

there's AutoHotKey on windows, among a ton of other automation tools.

Until the UI changes and a button moves or is renamed.

Generally the word DBA has a pretty broad meaning - and one of them is that you were a click admin that got hoisted into being responsible for your database servers, and things like software engineering tools (git, shell scripting in general) are a few years off.

The number of databases I have seen out of source control is too many to count, the number of times I had people who understood SQL very well but couldn't use git worth a damn. Some of them have been modifying the top of the file of a stored procedure for decades

  2024-01-01 hobs - changed even more shit
  2023-07-24 hobs - minor tweaks
  2001-02-04 hobs - created

I am reasonably confident that Oracle keeps its code under source control, but the PL/SQL packages it supplied start with a lot of this. The package WWV_FLOW, central to the APEX/ORDS product has more than 500 lines like

  --    MODIFIED   (MM/DD/YYYY)
  --      mhichwa   08/04/1999 - Created
  --      mhichwa   09/30/1999 - Removed g_show_reset global
  --      mhichwa   10/09/1999 - Added g_last_query_text global for error reporting
  --      mhichwa   10/09/1999 - Removed g_success_procedure, g_success_url
  --      mhichwa   10/09/1999 - Removed g_step_sub_title_font_color   --
  --      mhichwa   10/14/1999 - Added 10 extra inputs v26 ... v35

Thanks for the good laugh, but yeah, the time before source control is not that far behind some of us.

It's a very old way to use git, too. There's a CLI client for windows which doesn't require the old git bash program or mingw. You can install it via widget, scoop, or chocolatey and run it in windows terminal

It's that lots of db people don't understand anything about VCS period. They don't use them. (it's my piece)