Advent Calendar: Gimmicks and Git
This is the forth and final post in the advent calendar series, if you want to see the the other three posts, follow the links below:
Today is the forth advent sunday. Most of you might already be on vacation, preparing and organizing the last bits before and hopefully you are in the mood for the holidays. The last three weeks have been quite interesting for me. I had the chance to learn about new topics but also met and worked with new people, who helped me writing these posts and provided valuable input. I’d like to thank all of you, who provided feedback, helped with any topic or named a topic that should have been included in the first place. Thanks a lot for this.
And to not further stretch this out, now follow some gimmicky tools, pages or talks that I found out in the last weeks and think deserve a share.
This will be controversial. I personally like Emojis and use them, not in an excessive amount, but from time to time. What does this have to do with development or work? Well I have a habit of writing terrible commit messages. In the first steps i keep the log as clean as it can get, but after a while I just write whatever comes in my mind. When trying to find a way to “solve” this problem, I found out about gitmoji. Since Github allows some emojis basically anywhere, You can use them to visually seperate specific commits, PRs, comments and what not. I like them (from time to time) but am usually a bit to lazy to really append an emoji marker to each of my commits. However, what I keep doing is the seperation of commits. Usually I commit when changing something in the behavior of the software and I do a separate commit when changing the structure. This helps reducing those pesky “15k lines changed” commits, which no one likes.
While at the topic of git, it’s easy to break anything in your repository. I often forget to work in my own branch and try to push to main, which is not possible. Usually I’m able to correct this by moving the commits to the correct branch and pull-requesting the commits in main, as our process defines. But what if are the exact commands i ave to issue into my terminal. I admit, i usually use Gitkraken for my work and dont touch the Git CLI, as I cant remember anything with the CLI to be honest. But some things are not accessible from within Gitkraken, so I have to use the CLI and especially “repairing” is one of those areas. In comes Oh Shit, Git?!?, which provides most commands that are needed to fix up a repository and reset it to a state that can be worked on. Especially when beginning with git, this page can save your butt.
While we are at it with fixing wrong commands, thefuck helps me with fixing all my bash mistakes. I make so many typos or order flags the wrong way, this helps me with finding and fixing them. All it does is fixing up previous shell commands, but it works for me and I have no complaint. Also after a longer debug session when some mistakes could not be fixed, typing fuck in the command line feels empowering, not gonna lie.
There are a lot of Dev Talks out there, which can be recommended. Some show in detail how a specific library works or present new features in a language, some are just interesting. And then there are the funny lighning talks. I think one that everyone should have heard is WAT. I think most of you have seen this, but its such an classic talk that always pops up when looking into the of-topic channels of anything.So I thought I would also add it to this list.
Today is a bit shorter post. Time management is not my strongest suit, so I have to do the last holiday preparation. I guess everyone has the same problems, so I don’t want to keep you away from your duties.
I had a great experience writing those blog posts and really enjoyed them. Maybe next year we will do the same thing, with a little bit more preparation. So everyone can participate and help.
Have a nice holiday, celebrate as much as possible and stay healthy. Lets hope we can meet up in 2021 and talk without a mask covering us.