Unfortunately you sometimes need to do the thing

In the course of writing, I've observed numerous instances where a certain principle holds true: you often must do the thing you want to learn, even if you're not yet proficient at it. This is especially relevant when learning creative skills, such as programming in Rust or any other discipline. One key challenge many face is perfectionism, which can impede progress.

The frustration arises from the recognition that the finished product is never quite what was initially envisioned, but perfectionism can lead to paralysis and hinder learning.

To overcome this, it's essential to understand that the first version of anything created is almost always flawed, and striving for perfection can prevent you from even starting or never allowing you to refine your work. Our brains tend to be efficient, favoring skills that are used over those left unused. Thus, engaging in the act of creation itself is crucial, even if it means initially being bad at it.

The act of creating, whether coding or writing, involves two layers of understanding – the high-level view and the low-level work. The high-level view encompasses the overarching goals and overall approach, while the low-level work involves the actual mechanics and execution. Initially, it's essential to grasp the high-level understanding, but it's only through doing the low-level work that one can truly improve and refine their knowledge.

In programming Rust, the recommendation is to start by reading the Rust Book, particularly the beginning sections, and then immediately begin writing some code. Engage in small projects or utilize resources like rustlings or tutorials. Remember, it's vital to write the code yourself rather than just reading or analyzing it, as passive learning often leads to misconceptions. Although the code may initially appear imperfect or not compile, this is a natural part of the learning process.

Rust's forgiving nature, where terrible code that works counts as "working," can be beneficial for beginners. With time, you can focus on refining and improving your code, starting with understanding the high-level approach, then moving on to the low-level implementation. Similarly, in writing, the high-level view is the outline and thesis, while the low-level work involves crafting sentences, paragraphs, and ensuring they effectively convey the desired message.

Remember, the first step is always to create something, regardless of its imperfections, before worrying about polishing it.