I did not learn git until I started working professionally. In the university we learned about SVN. We did not really use branches, wee followed trunk based development in all of the group projects. At my second job I had to get into git quickly. It was overwhelming at first, but luckily I had patient mentors, who answered my questions with enthusiasm, and taught me best practices that I still carry with me. ...

I often need to present myself differently in git per project. When I work on a client’s own github, and they provide me an email address, it’s more professional, and most of the time a requirement, to use it to identify myself. Git, by default lets me specify configuration globally, or per repository. However, with a little trick I can set it on any abstraction level I need. ...

Have you ever been in a situation where you work for a few repositories over a prolonged time, and all of a sudden, you’re notified that you’ll no longer have access to these repos in a few weeks? ...

A few years ago I switched between a few machines on a daily basis, and tweaked my environments constantly. It was a tedious task to update each of them one by one, every time I changed configs or aliases in any of them. I figured this has got to be easier somehow, and found the hidden world of dotfiles. ...

My favourite place to deploy simple hobby and experimental web applications is heroku. It has a free plan, and it’s pretty easy to get started. ...

Imagine you want to submit a huge merge request (gitlab terminology), that has many changes from a bunch of commits. You realize that you don’t want to see some changes, but these changes are not in separate commits, so they can’t be easily reverted. There are a lot of small changes. You don’t want to type their reverse, or copy-paste for minutes. You want to keep the commits, not squash them together in the end. What would you do? ...