@deshipu Write a lot of shitty code, knowing it's going to be shitty. Then discard it, because it's shitty, and write another pile of shitty code that does the same thing in a better way. Then figure out which shitty aspects of it are most important to improve, and improve it in those ways. This is a fast way to learn. It helps with motivation sometimes writing tests first.