git-me(1) skill/c -- Toon Claes

82f3ab3 (skill/c) skill: Learning about the Git source code

Date: 2020-05-26

Interest in the Git^[1] project kept growing, Toon wanted to be involved in that project. Toon participated on the mailing list and when he was getting into SHA256 support^[2] he managed to get his first changes merged.

^[1]: git-scm.com ^[2]: git-scm.com/docs/hash-function-transition

f9a9597 skill: Advanced C++ course

Date: 2010-10-18

After a few years Toon got the opportunity to follow a three-day Advanced C++ course. This was really insightful to learn about the internals of iterators and traits and what not.

C++11 was around the corner, and there was plenty exciting stuff coming to the language.

38d1aa4 skill: Use C/C++ professionally

Date: 2008-08-01

At his first job Toon worked in C++. His job was building software for an embedded Linux payment terminal device. These applications were written in C++, but his job also involved bits of plain C when working on GNU/Linux kernel drivers.

953a905 skill: Programming in C++

Date: 2005-01-03

C++ was the first real programming language Toon was thaught in school. A pretty advanced language to get started with, but it thaught him a lot about programming in general.

↩ back

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%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 2022-06-16 GIT-ME(1)