robcornelius<p>When your teams <a href="https://climatejustice.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devops</span></a> and cloud lead person doesn't know how to use <a href="https://climatejustice.social/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> from the <a href="https://climatejustice.social/tags/CommandLine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommandLine</span></a> then there is going to be a problem sooner or later.</p><p>He was saying, "there is a vscode project you can open up, but it's not on the main branch yet. So you can't start vscode to change branches." Then he complained I didn't have <a href="https://climatejustice.social/tags/TortoiseGit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TortoiseGit</span></a> installed and asked how I managed to use git at all. He was amazed when I typed the magic incantation of `git checkout $$BRACH_NAME$$` on the keyboard and hit enter and it worked. I told him I had a paper manual on the bookshelf on git and had read it carefully. It doesn't mention a <a href="https://climatejustice.social/tags/gui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gui</span></a> beyond <a href="https://climatejustice.social/tags/gitk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gitk</span></a></p><p>FFS. How dense are these people? RTFM, It's not hard really.</p>