This is where JS shines (we all have browsers). I think dedicating 10 minutes to ensure `docker run --rm -it -v $PWD:/srv python bash` should suffice, without digging into what it does.
This is one of the most frustrating parts of learning ANY language. The assumed knowledge and supposed "here's a quick start guide" actually starts on step 8.
Don't assume the beginner knows what docker is.
Don't assume the beginner knows what a shell is.
I've tried to learn 3-4 languages or frameworks over the years, and I have only a vague idea of how to move between directories in the command prompt. Nevermind where I should download or extract files.
I've found people's attitude when I tell them this is dismissive. But I sold a business for 6 figures last year that was parimarily automation scripts in PHP. Figure that one out.
I'd be keen to learn more, can I reach out? I'm not really looking for guidance or ideas to do the same, I just genuinely enjoy reading these kinds of stories-like a weird Reader's Digest sort of thing but for entrepreneurs.
It's ok that you don't know what docker is.
It's ok that you don't know what a shell is.
What exactly is the nature of the dismissive attitude from others that has held you back from learning? Perhaps these are real opinions, but consider the source. If they are smarter than they are rude, and their opinions hold value, maybe suck it up and learn something. If it's not worth it to you, ignore them and walk away. Regardless, don't let other people's feelings hold you back from learning. And don't let other people's feelings about you dictate your feelings about yourself.
On the other hand, perhaps these attitudes are partly a projection of your own feelings. Use it as motivation to learn the things that you feel like you should know.
That shit is discouraging and the annoying thing--coming from some who first wrote a Tetris clone a decade ago--is that it's recent. A decade ago you just downloaded a library and put it in the folder you were writing in. Now while that still probably works library how-tos have all either gotten complicated or assume you've already complicated that shit.
And you run software by downloading a .zip, unpacking it and executing the program in that folder.
I miss the times when both development and use was that simple. And it was what, like 10 years ago?
I was more trying to make a point that if you're writing a guide or tutorial, actually start from the beginning.
Part of learning to learn is learning to keep going through things even when you don't fully understand.
This is something I've tried to tell my teams over the years... There is no direct correlation between technical complexity and business value!
Some problems require complex engineering to be solved, but value and even durability do not come from technical excellence for 99.99% of businesses... Of course as a software developer I prefer to walk pristine halls of cutting edge software with perfect tests but the businesses I've sold/run have numbed me to the idea that fancy code makes the big bucks...
1. Install docker using Apt or Yum 1a. So for CentOS i had to download and run a script on my machine to add the repository and install. 1b. Setup autostart of the service 1c. Configure my user so i can manage docker without sudo.
Then once its installed: 2a. Lookup the correct flags to use 2b. Find the correct image to run 2c. Learn how to map a local folder for persistence 2d. Learn how to open ports for the program to be accessible.
As a system administrator with 15+ years of experience, this is easy for me. But if I where to ask someone without any system experience to do this, I can for-see a lot of frustrating moments where they would give up.
Im sure that VMs have been tested and done as well, bringing their own different issues. We could add another layer of abstraction, like some type of orchestration tool, but then that needs to be supported and there will still be issues with the system underneath.
Maybe stat with something like lambda in AWS using their cloud9 instance as an IDE? It will cost a few $ but might help with the basics. However, this would only be good for very limited learning, so maybe add a small sysadmin crash course after that?
So maybe schedule it similar to this:
Basics: 10 days of coding in lambda using dynodb etc.
Systems: 2 days of devops using python to setup and control the environment
Rest of the course ....