With feenk's Glamorous Toolkit, devs (and leaders) spend more time making decisions and less time researching systems via reading the codebase. Shifting from reading to deciding means everything happens faster.

Typically, legacy code needs to be read, then the reader writes down what they perceive the code they've just read to be doing. With feenk's Glamorous Toolkit, inspecting the code, mapping the system, and testing the system happen simultaneously, with no dependency on human comprehension, eliminating bias.

The information needed to make decisions about how the system functions and, correspondingly, how to change the system, comes directly from the system itself, not from a human's conceptual interpretation of the codebase, what different parts of the code are doing, and how they relate or interact.

Glamorous Toolkit enables the rapid creation of "micro-tools," in realtime, during code inspection, which means the tools relate the information needed to inform decisions. Just as unit or component tests (also micro-tools) are custom-built for each unique context, tools which inform about system behaviors, relationships, and products must also be custom-built to inform decision-making.

Instead of inferring data about the system and then using it to invent models (which are incomplete and misinterpreted), Moldable Development builds models with the system itself, in realtime, without interpretation or missing information. Think of the former like making a painting of the system, while the latter is like having a video stream of the system.

The typical approach of reading code, interpreting, and modeling some aspect of the system is an ad-hoc approach, contingent on where the reader wants to begin, and where they want to go. Moldable Development is a systemic, disciplined approach to modeling and mapping systems. Instead of picking a random direction and wandering off, we use cartography to build detailed maps with rigor and accuracy.