git-me(1) job/gitlab -- Toon Claes

17c3c5e job/gitlab Transition to Gitaly team

Date: 2020-10-01

5bf285f job: Promoted to Senior Backend Engineer

Date: 2019-11-25

After years of hard work Toon's efforts were recognized with a promotion to Senior Backend Engineer.

225e784 achievement: Contribute to the migration to GCP

Date: 2018-07-28

In 2018 GitLab decided to migrate from Azure to GCP. GitLab Geo played a key role in this migration. It allowed us to have a hot standby in GCP, so the migration could happen with a minimal on downtime.

Many skilled people, including Toon as one of the experts on the Geo team, made the migration happen as smooth as possible.

about.gitlab.com/blog/2018/06/25/moving-to-gcp/

3296a7e job: Transition to GitLab Geo team

Date: 2017-06-01

After working in the Platform team, Toon moved to the Geo team. That team is responsible of building a Geo-distributed solution into GitLab. With GitLab Geo customers can install GitLab at their different offices and have them synchronize data between those installations. This allows their employees to have quick access to everything to do their job.

f342b8e achievement: Lead introduction of API v4

Date: 2017-03-22

Toon was responsible of the maintenance of the REST API, and he led the path to introduce API v4. All deprecations and breaking changes we wanted to make had to happen in the upcoming major release GitLab v9.0.

96f6cb8 job: Start at GitLab as Backend Developer

Date: 2017-01-02

Toon started in the so-called Platform team at GitLab. That team was responsible for Git operations, Merge Requests, and more.

GIT-ME(1) Toon Claes's resume GIT-ME(1) NAME git-me - Show Toon Claes's resume SYNOPSIS git me [<branch-name>] DESCRIPTION Show Toon Claes's resume in a git(1) history. You can clone this git repository containing Toon's complete resume, but when you do, you will get an empty tree. The data for Toon's resume isn't stored in any file in this repository, but it's in the git-log(1) history itself. git(1) is a great tool to track the history of a bunch of text files, and it's most often used to store computer source code. But it allows you to completely rewrite the history of a git repository. This makes is possible to create a fully arbitrary history. I'm using this to write everything one would write in their resume into the git commit log. USAGE You can visit this project in your browser at https://git-me.tech. Or you can visit it through curl: curl -L git-me.tech If you like to have a local copy of the git repo, run: git clone https://git-me.tech The following command will add the `git me` alias: git config alias.me '!f() { git log --graph --date-order \ --format="%Cred%h%Cgreen%d%Creset%C(bold) %s%Creset%C(\ )%n%C(italic)Date: %Cblue%as%Creset%n%b" \ origin/${1:-$(git rev-parse --abbrev-ref HEAD)}; }; f' Or if you want to use the automated installation: curl -L# git-me.tech/install.sh | sh This will clone the repo in a temporary directory, and install the git-me alias in it. Nothing is installed permanently on your computer. BRANCHES When you're using this project on the command line you can pass the branch name as an argument, when you're looking at this project rendered as a webpage, you can click on the branch names. <branch-name> By default you'll get my full resume, but that output can quite overwhelming. So you can slim down the output by passing a branch name. Here are a few examples: jobs This only prints info related to my job history. job/gitlab This narrows history down to my job at GitLab. education This shows my education. skills Lists all my skills I've gathered through the years. AUTHOR Written by Toon Claes. CONTRIBUTING If you have a suggestion, or if you've found a bug or a typo, you're welcome to file an issue or open a merge request at: https://gitlab.com/to1ne/git-me GIT This is *not* part of the git(1) suite. Git is a trademark of the Software Freedom Conservancy. Toon Claes 1.0 2023-07-14 GIT-ME(1)