How abstraction grows in the mind through experience, and what happens when it reaches the core.
There is a quality of thinking I have come to call abstraction authenticity. It is the difference between abstraction as a technique you apply and abstraction as a faculty you have become. The first is learned in a classroom or a design review. The second is earned, slowly, through decades of real work, and once it is earned, it changes what you are able to see in everything you touch.
What abstraction actually means
Abstraction is the act of removing everything about a thing that is incidental until only what is essential remains. It is not summarising, which shortens. It is not generalising, which blurs. Abstraction is subtraction with judgement: you take away detail after detail, and the test at every step is whether the thing still behaves the same without it. What survives that test is the essence, and the essence is always smaller, simpler, and more powerful than the thing you started with.
Three simple examples. A map is an abstraction of terrain: it removes every tree and building and keeps only what you need to navigate, and precisely because it removes so much, it is more useful for the journey than the terrain itself. A balance sheet is an abstraction of a business: thousands of transactions, contracts and judgements reduced to a single structured statement of position, and an experienced reader sees the health of an enterprise in it faster than by walking its corridors. A recipe is an abstraction of a cook: it captures what the cook does that matters and discards everything personal, so that the dish can be reproduced by someone who has never met the cook.
Notice what all three have in common. Each abstraction is not a poorer version of the original. It is a more usable version, because usefulness lives in the essential, and the incidental only obscures it.
Abstraction is grown, not taught.
Here is the part that is rarely said honestly. The mechanics of abstraction can be taught in an afternoon. The judgement inside it, knowing which detail is incidental and which is essential, cannot be taught at all. It grows, one layer at a time, through exposure to reality: every project, every client conversation, every observation, every defeat, every success, every insight adds a thin layer. A defeat teaches you which detail you wrongly dismissed as incidental. A success confirms which essence you correctly kept. Over years, the layers compound into something that no longer feels like a method. It feels like sight.
This is why I call it authenticity. An authentic abstraction ability cannot be faked, borrowed, or rushed, because it is made of digested experience. Two people can look at the same messy business process. One sees forty steps. The other sees three decisions wearing forty costumes. The second person is not cleverer. The second person has simply paid, over decades, for the judgement of what to remove.
Where abstraction sits in the thinking gradient
Thinking has a gradient, and it is worth naming its levels plainly. At the base is observation: seeing what is there. Above it is pattern recognition: seeing that this resembles that. Above that is analysis: taking a thing apart to understand how its pieces relate. Then comes abstraction: discarding the pieces that do not matter and keeping the structure that does. And at the top sits modelling: reassembling the surviving essentials into a structure that not only explains what you saw but predicts what you have not yet seen.
Most professional thinking lives at analysis and stops there, and analysis is genuinely valuable. But analysis multiplies detail while abstraction divides it, and only what has been divided down to essence can be built into a model. Abstraction is therefore the gate in the gradient. Below the gate, knowledge accumulates. Above the gate, knowledge compounds, because essences connect with each other in a way that details never do.
Connecting the dots into a model
This is where sustained abstraction pays its real dividend. When you abstract one domain to its core, you hold one essence. When you have done it across many domains over many years, the essences begin to recognise each other. The control structure inside an audit turns out to share a skeleton with the validation structure inside a software module. The way a tax treaty allocates rights resembles the way a well-designed system allocates permissions. The discipline of a going-concern judgement rhymes with the discipline of deciding what belongs in a product and what does not. None of these connections is visible at the level of detail. All of them are obvious at the level of essence.
A model built this way is far superior to one built from a single domain, for a simple reason: it has been stress-tested from many directions before it was ever written down. Each new experience either fits the model, which strengthens it, or breaks it, which improves it. Do this without pause for long enough and the model stops being a description of things you have seen. It becomes a machine for understanding things you have not yet seen. That is the perfection the connecting of dots moves toward, never fully reached, always approached.
When the model becomes the product
I will end with the conviction that this journey has left me with, because it is the foundation on which we build at Sathguru Soft. If abstraction is carried far enough, the model does not merely describe the work. The model can do the work.
An enterprise application, abstracted honestly, is not its screens and not its code. Those are incidental. The essence is a model: entities, relationships, rules, computations, and flows. For decades, the industry has treated code as the product and the model as documentation. Sustained abstraction says the opposite. The model is the product, and everything else can be generated from it, or dispensed with entirely. When the application executes from the model itself, the largest incidental of all, the code, is removed, and what remains is the essence, running.
That is what abstraction authenticity ultimately delivers. Not cleverness, not shortcuts, but the earned ability to see the core of anything and to build from the core alone. It grows one project, one conversation, one defeat and one insight at a time, and there is no other way to grow it. Which is precisely why, once grown, it is very hard to compete with.
Happy Reading!!
(Ragu)nathan Kannan
raguk@sathgurusoft.com