A Guide to the World of Post-Truth: Connecting Lies, Code Tags, and Organized Programming

A Guide to the World of Post-Truth: Connecting Lies, Code Tags, and Organized Programming

In a world where misinformation and deception have become increasingly prevalent, it is important to navigate through the complexities of the post-truth era. Benjamin Disraeli, the former British prime minister, once said that there are three types of lies: lies, blatant lies, and statistics. While this statement sheds light on the deceptive nature of statistics, it is essential to expand upon this classification.

Similarly, in the world of programming, we encounter a different kind of deception, one that hides behind the guise of code tags. These code tags, commonly referred to as TODOs, serve as comments within the code, holding specific meanings for different tools and developers. IDEs and their extensions often scan code for comments that begin with TODO, FIXME, HACK, XXX, DONE, UNDONE, ASAP, REMOVE, NOTE, BUG, ISSUE, ERROR, BROKEN, GLITCH, REVIEW, WTF, and more.

These tags are cataloged by various tools to ensure that incomplete or attention-worthy code is not accidentally overlooked. While it is possible to customize these tags, it is crucial not to go overboard, as excessive tags can hinder usability. Generally, the first three tags (TODO, FIXME, HACK) prove to be the most useful, while the others serve as variations, specializations, exaggerations, or require better tools. A more detailed description typically follows the colon in these tags, helping the tool identify the semantics of the comment.

Organized programmers employ this practice to ensure code clarity and facilitate communication within their teams. However, it is important to note that excessive use of these tags without proper management can be counterproductive. Some teams even prohibit committing code with these tags, unless it is intended for communication purposes. The argument is that if something is planned but not implemented, it should be documented, and if something is missing to fulfill the planned implementation, the commit cannot be made until it is complete. In reality, this workflow is often compromised, and individuals resort to removing these tags from the code and placing them elsewhere, simply to bypass these rules.

In connecting the world of post-truth and organized programming, we find common ground in the need for transparency and clarity. Both contexts require us to identify and address deception, be it through misinformation or incomplete code. By recognizing the importance of clear communication and documentation, we can navigate through the complexities of the post-truth era and ensure the integrity of our work.

Actionable Advice: