[jackkinsella]

I found your idea of recording the screen during work very clever and I plan to replicate.

Some things that have worked for me:

— learning to type programming symbols accurately and with confidence. I realized when pair-programming that I lose a ton of time to backtracking due to typos. This is particularly bad when working in interactive code consoles where the poor editing capabilities mean typos are more costly. There are web applications out there like typing.io that help with this.

— keeping a "dumb mistake log" where I write up any silly errors that cost me too much time so I'll know to double check these things next time (e.g. "space instead of tab in Makefile > make tabs appear differently", "wrong file but with same name > keep an eye on the folder in the editor when switching files")

[Cthulhu_]

In addition to the "dumb mistake log", see if these things can be automated; for your Markdown example, set up your editor to format / fix issues automatically, e.g. using Markdownlint. Use the available tooling; take some time to tweak your editor, that kinda thing.