The important thing you missed then and are still missing now is that none of that stuff you mention happens in the Windows world.
We set up VPNs to our servers and access them via network paths or directly using Remote Desktop. One can go one's entire career without ever typing ssh-keygen into a terminal window. It's certainly not a step involved in setting up a client to talk to version control.
You don't have to believe me on this. You can read the article we're talking about here and see this same sentiment expressed by the GitHub team themselves.
Thanks to that team, folks in our side of the dev world now have an easy path into Git and GitHub, and can go about our merry way building things without ever having to parse what it was that you did in your second paragraph.
"Thanks to that team, folks in our side of the dev world now have an easy path into Git and GitHub, and can go about our merry way building things without ever having to parse what it was that you did in your second paragraph."
... except when github messes up, forces you to do a SSH key audit and then you're back to needing to know "scary crypto stuff".
We set up VPNs to our servers and access them via network paths or directly using Remote Desktop. One can go one's entire career without ever typing ssh-keygen into a terminal window. It's certainly not a step involved in setting up a client to talk to version control.
You don't have to believe me on this. You can read the article we're talking about here and see this same sentiment expressed by the GitHub team themselves.
Thanks to that team, folks in our side of the dev world now have an easy path into Git and GitHub, and can go about our merry way building things without ever having to parse what it was that you did in your second paragraph.