The Cake Goes First, The Cherry Tops It #

An eloquent one liner in software. A short sentence that conveys more meaning than a book. The pure display of strength when snatching a 32kg KettleBell for reps.

As a beginners is all that you can see. A glimpse of those peak performance moments. But what you can see in public is not what makes it possible. Attempting to perform the highlight without going through all the preparation required that enables that one moment in time is a recipe for failure. Worst even, you will reach the conclusion that you are not suited for it and give up on even trying to get better.

Imagine trying to learn to walk by looking at Usain Bolt running a World Record 100m dash, attempt it, fail at it, and concluding you are not suited for walking.

It's normal to be amazed by the highlights but these aren't the starting point. For the cherry to be at the top there needs to be a cake first and for the cherry to be highlight the cake needs to be perfect. Using the top performers highlights as guiding starts to "One day that will be me!" while grinding the basics is the only way to get there.

Writing your first "Hello World!" script is the very first step. Learning about variables, functions, data structures and algorithms goes next. Using these primitive building blocks to create reusable components goes next. Combine these patterns to build programs and services goes next. Scope these complete units to different sizes and responsibilities in the last step in building a complete system.

Swinging a KettleBell goes first. Developing the hip-hinge to maximize the power output goes next. Timing the inhale-exhale respiration for efficient oxygen management goes next. Learning new exercises like the clean, press, front-squat and snatch goes next. Combining these exercises into complex sequences goes next. Arranging these sequences into blocks that form an entire practice goes next. Organizing the practices into variations of explosive, strength and endurance practices is the last step in the practice of KettleBells.

Mastering one level before going up to the next is not a requirements, sometimes is even beneficial to attempt a big leap forward way beyond your knowledge just as an attempt to broaden your perspective. Unless a catastrophe happens, there is only upside potential from all the exposure to nex things. Having even a vague idea on how things interplay at higher levels will guide the decision making process about the current that will make it even better.

It is a requirement, nevertheless, to maintain at high standard at any level below the one you are acting on. Cutting corners because you are above it is not acceptable and will taint the perceived quality of any kind of excellent work you might do. If a project requires you to do architecture and also write boilerplate code, both these things have to be handled with exceptional care.

All along the journey there will be a few cherries atop of a few cakes. Spontaneous moments of pure skill display. Moments that for much that you try you can't reproduce because they happened within a context that you don't yet have the necessary skills to reproduce. These moments are the confirmation that you are on the right path but there still a lot of work to do.

This way, when all the cake's layers are baked correctly, lined up perfectly, the glazing is sweet but not too sweet, when you can test all the ingredients not only the sugar, when the individual slice is not too big nor too small; then and only then the cherry becomes the highlight.