The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
kunzimariano
/ git-commit-template.md
Created
February 24, 2023 14:02
— forked from lisawolderiksen/git-commit-template.md
Use a Git commit message template to write better commit messages
kunzimariano
/ System Design.md
Created
December 18, 2021 23:37
— forked from vasanthk/System Design.md
System Design Cheatsheet
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
kunzimariano
/ LearnGoIn5mins.md
Created
January 19, 2021 02:25
— forked from prologic/LearnGoIn5mins.md
Learn Go in ~5mins
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
kunzimariano
/ tmux-cheatsheet.markdown
Created
April 29, 2019 15:09
— forked from MohamedAlaa/tmux-cheatsheet.markdown
tmux shortcuts & cheatsheet