Firstly, Git Blame's name is a bit silly. I propose renaming it git
who-what-where-when-why or git 5w for short.
From the command-line, it outputs the file you specify, but each line is
annotated with who changed it last, the commit message, and when it was changed.
That's not the most convenient use of it though. If you use VSCode, the GitLens
extension has the best blame features. This feature is also available in other
IDEs but GitLens is the best example I've seen.
* Who - Shown at theHow could we optimise the human condition using the personal data around us?There are things that others value highly, which I do not value at all.
There are things that others value highly, which I never valued at all.
There are things that I value highly, which others do not value at all.
There are things that I once valued highly, which I no longer value.
I once valued a good degree classification. I no longer value this so highly…
I once valued a degree. I was getting a degree to find my place in the world. It
was going to give me value. It was hence going to makeThe first few Hackathons may be hard. You may not be happy with what you
produce. You may compare yourself to everyone else and feel bad about it. But
keep persevering and you will come through it a great developer. Things get
Quantity over quality
*from *Art & Fear
by David Bales and Ted Orland:
> A ceramics teacher announced on opening day that he was dividing the class into
two groups. All those on the lefThe first part of the GitHub campus experts’ training is to write an impact
proposal. My impact proposal was largely focused on ensuring future generations
of organisers can effectively inherit the existing organisation and continue to
make the community their own.
Specifically - the concept of knowledge transfer was very central to my thoughts
throughout. As it happens, GitHub itself was a potential solution for this.
Knowledge transfer is important for student communities as churn rate of