Being the maintainer of a fairly active oss project (MetalLB) over the past year, I reviewed a substantial amount of contributions. During this process, I identified a set of recurring idioms and patterns that less experienced contributors keep missing, making the codebase harder to read and to maintain. In this talk I will describe what cognitive load is and why it matters, and provide a way to reduce it via a set of quick and easy recipes. Using this set of actionable recipes the audience will be able to drastically improve the quality of their Go code with relatively low effort.