patchwork VS gitplay

You can read the markdown version [here](https://github.com/brainless/gitplay/issues/5)

## Problem statement

We all have worked on a feature intensively and had to refractor a lot of the code base (in early projects). But can't spend the mental expense to context switch from `writing code` to `make meaningful commit messages`.

A good commit history is at the expense of the developer, which results in breaking the "flow". As pg mentioned in his blog post [Holding a program in one's head][1], it be better to work in long stretches to have better developer productivity. And it is very common for devs to have to make code cleanups which are unrelated to the feature they are working on ([example tweet][2])

* Commit small and commit often

What are you starting with? I re-started my Rust learning last month. I am very slow at learning but Rust makes digging into systems stuff so much fun. I am from Python/JS background. I start with Rustlings every time.

Now building a Git player - basically watch a Git repo history unfold like a movie, for learning purposes [1].

Please ping me if you have some ideas, looking for learning peers.

1. https://github.com/brainless/gitplay