You want to make your way in the CS field? Simple. Calculate rough time of amnesia (hell, 10 years is plenty, probably 10 months is plenty), go to the dusty archives, dig out something fun, and go for it. It’s worked for many people, and it can work for you.
None of those things are intractable, I have had scripts handle them all.
On top of that, writing scripts educates you on how such systems work. It really isn't challenging.
I know that there is nothing that an add-in can do that a scripting environment can't and it is not a that difficult, which is the assertion I am responding to. Sooner or later the dialog box driven tool will prevent you from doing what you want.
I would still like an example of a series of Http:// requests that is "difficult" to do with just curl, wget and a bit of shell script.
If you have to fiddle with the command line, you're doing it wrong.
It drives us nuts in the Plan9 community that Bash history and readline is seen as some sort of productivity tool. We have powerful shell primitives but the command line is seen as the last resort of composing them. Admittedly we have a terminal window with which you can edit text in two dimensions but use a proper set of tools with a bit of forethought and you get much more done.
If you need an oauth client, write one with a few bits of script and use it everywhere. It's the Unix way.
I doubt it
You want to make your way in the CS field? Simple. Calculate rough time of amnesia (hell, 10 years is plenty, probably 10 months is plenty), go to the dusty archives, dig out something fun, and go for it. It’s worked for many people, and it can work for you.
If you don't know Ron - http://www.socallinuxexpo.org/scale8x/blog/interview-ron-min...
People today could do well reading
Computer Architecture and Parallel Processing Paperback – International Edition, January 1, 1986
by Kai Hwang (Author)
https://www.amazon.com/Computer-Architecture-Parallel-Proces...