Small programming tricks

In the realm of programming, it's often the smallest pieces of knowledge that yield significant productivity gains. These nuggets of information, such as being cognizant of existing language features, understanding the implications of certain settings like TCP_NO_DELAY and the principles of Nagle's algorithm, or knowing the appropriate git commands to resolve issues, are the building blocks of efficient engineering.

A single piece of knowledge, it would seem, forms the foundation upon which more complex understanding is built. It's clear that these smaller bits of wisdom matter greatly. Yet, some of these fundamental pieces of knowledge prove particularly valuable, requiring minimal additional mental scaffolding. For instance, the command python3 -m http.server can be used to initiate a basic server within a directory without prior Python expertise, yet it may still streamline one's workflow.

Examples of such nuggets abound. Some may already be familiar with these concepts, while others may find them inapplicable to their domain. Regardless of their relevance to you, I am confident that everyone possesses a collection of similar tricks honed through years of experience, which undoubtedly makes their work more manageable.

Within a corporate setting, the accumulation of such high-leverage knowledge tends to be even more pronounced. At a prior company, sharing a daily tip—technical or otherwise—with the engineering team proved beneficial. The ideal count was ten per day, ensuring knowledge dissemination remained manageable and occasionally stimulating engaging discussions.

If you're a more seasoned engineer at your organization, consider cultivating and sharing similar practices. The idea of disseminating small bits of knowledge, as eloquently articulated by Julia Evans on her blog, is undeniably powerful. Her writing aptly captures the essence of this post: emphasizing the importance of these seemingly minor yet impactful pieces of information.