As nice as this tutorial is, I don't think git is ever really going to have widespread appeal outside of (semi-)professional SWEs who are forced to use it due to community size and ubiquity.
The commands are simply too badly thought out and the staging, pushing, pulling, merging process is too complex.
E.g. want to switch branches? git checkout. Wtf why not "git switch-branch" or something. Want to send your code to the master? Is it git push? git pull? Well, its sort of both but hey.
>The banks care less about their qualifications than their work ethic. Being a Rhodes Scholar doesn't make much of a difference when you're a young banker. More of it is being willing to stay at the office for 120 hours a week.
This is very, very true. In my experience, investment banking is by no means a particularly difficult thing to do, given enough capital to play around with. Quants aside, the concepts that are used (take, for example, "mezzanine capital") are mostly buzzwords used to give a professional air to really very simple processes/ideas. It is a far cry from the serious, dedicated abstract thought demanded by fields such as software engineering/machine learning/data science etc.
However, what large financial institutions need are people who are extremely assiduous to small details, have a work ethic in which 7am-11pm hours creating powerpoints are no big deal (and have good sounding qualifications to impress investors).
It totally depends on the department and position you're applying for, and the people who'll be interviewing you.
There's so many different things - I'll send you an email and we can chat over the weekend if you want?