The Hindu of the Cross When Father John Paul Korrakal arrived in Australia, the bishop sent him west. Not Rome-west. Proper west. Past the coast, past the sandstone, past the last suburb selling twelve-dollar sourdough, until the railway line became a suggestion and the local newspaper considered a new roundabout major geopolitical news. The parish was called St Jude’s. The town was called Wattle Creek. Population: 1,846 humans, several thousand sheep, one Catholic church, two pubs and a theological system based largely upon whether somebody was “Catholic”, “Anglican”, “one of those happy-clappy mobs”, or “something Indian”. Father John Paul came from Kerala. This immediately settled the matter. “Hindu priest’s arrived,” announced Doug at the Royal Hotel. “He’s Catholic,” said Macca. “Yeah, but Hindu Catholic.” “Right.” And so the Council of Nicaea concluded its business at the front bar. --- John Paul first discovered the problem at the post office. Mrs Doreen Pike looked over his parcel. “India?” “Kerala.” “That’s India, love.” “Yes.” “Hindu?” “No. Christian.” She stared at his Roman collar. “Well obviously now.” “No. Before now also.” “How long?” John Paul made his first tactical mistake. He answered accurately. “Our community traces its tradition to Saint Thomas the Apostle.” Doreen stopped stamping the parcel. “Which Thomas?” “The Apostle Thomas.” “Doubting Thomas?” “Yes.” “He went to India?” “According to our ancient tradition, yes.” Doreen considered this. “So you're an ancient Hindu Christian?” “No.” “Righto.” The parcel received three stamps. The Hindu Christian had officially entered the Australian postal system. --- Father John Paul was Syro-Malabar. This presented Wattle Creek with difficulties. The Catholics understood “Catholic”. They understood “Roman”. They understood “Father”. Unfortunately John Paul had arrived with the information that he was Catholic but belonged to an Eastern Catholic Church, whose inheritance was Syriac, whose ancestors had been Christians in India long before Vasco da Gama turned up looking for spices, and whose relationship with Latin Christianity had occasionally involved the sort of administrative enthusiasm for which Europeans had become famous. “So you're Orthodox?” asked Barry, chairman of the parish council. “No.” “Roman Catholic?” “In communion with Rome.” “So yes.” “Well—” “Beauty.” John Paul began again. “The St Thomas Christians developed with the East Syriac tradition—” Barry's eyes acquired the distant expression of a man watching his ute roll downhill without him. “Tea, Father?” “Yes, Barry.” Milk defeated ecclesiology in under forty seconds. --- John Paul persisted. He had studied philosophy. He had studied theology. He had studied canon law. He had survived seminary committees. He therefore possessed the dangerous belief that misunderstandings could be defeated by sufficient explanation. At the primary school a boy asked: “Father, were you Hindu before you became a priest?” “No.” “Were your parents Hindu?” “No.” “Grandparents?” “No.” “How far back?” John Paul smiled. “Many generations of Christians.” The boy frowned. “But you're Indian.” “Yes.” “So how aren't you Hindu?” There are moments in the priesthood when a man encounters mystery. The Eucharist. Grace. Death. The Trinity. And occasionally an eleven-year-old named Lachlan who has independently reconstructed the British census categories of 1871. John Paul drew India on the blackboard. He drew Kerala. He drew a little cross. He explained Saint Thomas. He explained Syriac Christianity. He explained that Christianity was born in West Asia, not Buckinghamshire. He explained that ancient Christian communities existed across Syria, Persia and India. Lachlan listened carefully. “So…” “Yes?” “You're like an original Hindu Christian?” John Paul looked at the crucifix. The crucifix offered no visible assistance. --- The breaking point came at the hospital. Old Clarrie Thompson was dying. Clarrie had spent eighty-seven years farming wheat and regarding abstract nouns with suspicion. Father John Paul sat beside him. Clarrie opened one eye. “Good of you to come, Father.” “My privilege.” “My daughter says you're Hindu.” John Paul inhaled. “I am a Christian, Clarrie.” “Yeah, yeah. Hindu Christian.” “Clarrie—” “Don't worry. God's got plenty of room.” John Paul looked at this dying Australian farmer, who had accidentally solved religious pluralism mostly because he could no longer be bothered arguing about it. Something inside the priest surrendered. Not his faith. Not his baptism. Not his creed. His taxonomy. “Fine,” he said. Clarrie opened the other eye. “What?” “I am a Hindu of the Cross.” Clarrie nodded. “Knew it.” And went back to sleep. --- The phrase travelled faster than any pastoral initiative John Paul had attempted. Within a fortnight the butcher greeted him: “Morning, Father Cross-Hindu.” At bowls: “Here comes the Hindu of the Cross.” The Anglican minister found it absolutely hilarious. The diocesan office did not. A letter arrived asking Father John Paul to “clarify the pastoral context in which certain terminology concerning religious identity had reportedly been employed”. John Paul placed the letter beside his tea. There it was. Rome had discovered Wattle Creek. He prepared a reply. Then deleted it. Prepared another. Deleted that too. Finally he wrote: “I remain entirely Catholic. The problem is Australians.” He decided not to send it. --- At Sunday lunch, Margaret O’Shea finally asked what everyone had been circling around. “So what do you actually mean by Hindu of the Cross?” John Paul put down his fork. “Historically, words related to Hind and Hindu were sometimes used geographically for India and its peoples before the word hardened into the religious category you know today.” Blank faces. He tried again. “My ancestors did not need to become European before following Christ.” Better. “They were Indians before the Portuguese arrived?” “Yes.” “And Christians?” “Yes.” “And Rome?” “Complicated.” Every Australian at the table immediately understood this. “Government problem,” said Barry. “Something like that.” John Paul continued. “The Portuguese encountered an Indian Christianity that already existed. There were later attempts to Latinise parts of it. There were disputes, divisions, reconciliations, more divisions…” “So church politics.” “Barry, I studied seven years to avoid saying precisely that.” “Could've saved you six.” John Paul laughed. “So when you people insist that Indian means Hindu and Christian means Western, I have two choices. I can deliver a lecture every time I buy milk…” “Not recommended,” Margaret said. “…or I can say: fine. If by Hindu you mean a man of India, then I am a Hindu who belongs entirely to the Cross.” Margaret thought about it. “But you're still Christian.” “Of course.” “Catholic?” “Yes.” “Syro-whatever?” “Syro-Malabar.” “And under Rome?” John Paul winced. “In communion with Rome.” “Same thing?” John Paul reached for the wine. “Today, Margaret, yes.” --- Something strange happened after that. The less John Paul defended the foreignness of his Christianity, the less foreign it appeared. At Easter he spoke about the Cross without trying to explain India. At Christmas he spoke of a child born in Asia under an empire. At funerals he spoke of resurrection. At the pub he spoke mainly about cricket, because even missionaries have limits. People eventually learned that Kerala had Christians older than several European nations. They learned that Syriac was not “some Indian dialect”. They learned that Thomas Christians had crossed centuries of Persian connections, Portuguese interference, colonial classifications and Roman paperwork without requiring permission from Wattle Creek to exist. And John Paul learned something too. Ordinary people rarely inhabit the elegant categories theologians construct for them. They inhabit stories. Doreen at the post office did not care whether Christianity reached Kerala in the first century, fourth century or through some complicated sequence of merchants and bishops. She understood something much simpler. Father John Paul came from India. Father John Paul followed Jesus. Therefore, in the magnificent cathedral of Doreen's mind, he was the Hindu bloke with the Cross. Incorrect? Technically. Hopelessly imprecise? Certainly. Malicious? Not remotely. And perhaps there was something almost ancient buried beneath the mistake: the vague memory that civilisation, geography, culture and religion had not always lived inside separate boxes on government forms. --- Years later, when Father John Paul left Wattle Creek, the parish held a farewell at the community hall. Barry gave the speech. “When Father arrived, none of us knew what a Syro-Malabar was.” John Paul nodded. “Still don't,” Barry added. Applause. “But we know he's ours.” That silenced the room for a moment. Barry handed him a small wooden cross. Burned into the back were four words: THE HINDU OF THE CROSS John Paul stared at it. Twenty years earlier he would have corrected them. He would have explained Persian geography, Sanskrit Sindhu, East Syriac liturgy, apostolic tradition, Portuguese Latinisation, ecclesiology, sui iuris Churches and the precise canonical meaning of communion with the Bishop of Rome. Instead he put the cross in his pocket. “Well,” he said, “at least you finally got the Cross right.” From the back Doreen shouted: “What about the Hindu bit?” John Paul sighed. “Ask Rome.” The hall erupted. And somewhere, he imagined, Saint Thomas—the apostle who had once demanded empirical evidence before believing anything—was having a very good laugh. Because after two thousand years of theology, empire, translation and argument, Father John Paul Korrakal had travelled from Kerala to the far side of the world only to discover the oldest rule of missionary work: You may bring the Gospel to the village. But the village will name you. #HinduOfTheCross #StThomasChristians #SyroMalabar #KeralaChristianity #IndianChristianity #FaithAndIdentity #ChurchHistory #TheologyWithHumour #AussieSatire #ChristianHistory #KeralaToAustralia #CrossAndCulture #ThomasChristian #FaithTravelsWell #WattleCreek

Muktamoho Hinduḥ. मुक्तमोहो हिन्दुः The one freed from moha — illusion, attachment, mistaken seeing. And Hindu, before it became a religious category, points backwards through Persian Hindu toward Sindhu: the river, the frontier, the people beyond it. So hear the phrase poetically: the disillusioned one from the Sindh. Not disillusioned as in defeated. Dis-illusioned. The illusion has fallen away. No empire owns the word. No bureaucracy contains the dharma. No ideology can substitute itself for direct perception. The river existed before the category. Dharma existed before the form. And liberation begins when the name is no longer mistaken for the thing. Muktamoho Hinduḥ — the one of Sindhu who has become free of moha. #Muktamoha #Hindu #Sindhu #Dharma #Moksha #SanatanaDharma #Sanskrit #India #Civilization #Consciousness

Shiva at the End of the Ledger The history of technology is not a war between engineers and finance. It is a recurring struggle over who owns the consequences of engineering. Capital frequently finances the machine that changes civilization. Then, once that machine becomes indispensable, institutions discover that controlling access to it is more profitable than allowing it to remain free. The railway is an early example. Railways were extraordinary technological liberation: distance collapsed, markets connected, people moved and information accelerated. But the railway could also become a toll gate. In colonial India, British private companies raised capital in London to build railways while receiving government-backed return guarantees. Some early companies failed to earn the guaranteed return themselves, leaving Indian tax revenues to cover the difference. The technology was revolutionary; the financial architecture determined who carried its risk. That distinction repeats throughout industrial history: the engineer builds a capability; finance discovers the rent-bearing surface around it. Then came telecommunications. The telephone should have multiplied networks. Instead, network effects created extraordinary opportunities for concentration. AT&T possessed both superior access to capital and the crucial long-distance network. The US Department of Justice records that AT&T refused interconnection to independent networks while acquiring competitors, eventually provoking antitrust intervention and the 1913 Kingsbury Commitment. Again, the technology wanted to connect. The institution wanted to become the connection. Then programmers produced something stranger. The Internet escaped TCP/IP was not successful because one financial institution owned it. Its strength came partly from being an interoperable protocol that could be implemented across heterogeneous machines and networks. The Internet Society's historical account describes commercial vendors initially trying to bolt TCP/IP onto proprietary networking systems such as SNA, DECnet and NetWare. Yet the open protocol eventually displaced or marginalised much of that proprietary networking world. Public and academic investment played a major role before the commercial Internet emerged. This was an extraordinary historical event: civilization discovered that an open protocol could defeat vertically integrated infrastructure. Nobody needed permission from IBM to speak IP. Nobody owned TCP. Packets did not need a bank manager. That should have been a warning. Because programmers had discovered the most dangerous architectural idea imaginable: «replace institutional trust with protocol compatibility.» The following decades produced Linux, open-source infrastructure, distributed databases, peer-to-peer networks, cryptography, BitTorrent, Git and eventually Bitcoin and blockchains. Each step asked a slightly more dangerous question. Why should the intermediary exist at all? Then software became financialised The Internet did not abolish concentration. It produced another round of it. Platforms discovered that identity, hosting, advertising, payments, application distribution, cloud compute and social graphs could become new chokepoints. The OECD now explicitly recognises the problem: entrenched market power can allow dominant firms to use acquisitions, strategic patenting and platform position to suppress competition and extract rents. Digital markets are particularly susceptible because network effects and economies of scale can create formidable barriers to entry. So the cycle returned. Open technology. Rapid innovation. Consolidation. Financialisation. Rent extraction. Complexity constructed around protecting the rent. And eventually an engineering community wondering why a machine that was supposed to reduce friction requires twenty corporations, seven subscriptions, three identity providers, four clouds and somebody else's permission simply to execute code. Blockchain crossed another boundary Bitcoin's profound engineering proposition was not “number go up.” It demonstrated that strangers could maintain and transfer a scarce digital asset without requiring a bank to maintain the canonical ledger. Blockchains extended the proposition: execution itself could become part of a distributed consensus system. That does not mean blockchain abolishes debt. Debt is a human agreement concerning future obligations, not merely a database implementation. Indeed, DeFi has demonstrated how rapidly humans can reconstruct lending, collateral and leverage directly on-chain. BIS research documents substantial leverage inside decentralised lending systems. So the serious claim is subtler: blockchain does not make debt impossible. It makes certain forms of trusted financial intermediation optional. There is an enormous difference. A civilization can still borrow. But settlement need not itself be somebody else's liability. Ownership need not necessarily mean an entry in a custodian's database. Execution need not always depend upon a corporation remaining solvent. Verification need not necessarily terminate at institutional authority. That is the line programmers were approaching. Had engineering incentives been organised differently, perhaps far more infrastructure would already be built from bearer assets, open protocols, local computation and cryptographic verification rather than subscription accounts and leveraged intermediaries. But the stronger claim — that programmers would necessarily have moved civilization completely beyond debt — cannot be established historically. We can say something more interesting: they were building systems capable of reducing the number of places where debt-backed institutional trust was technologically mandatory. And that threatens a very different thing. Not finance. Financial dependency. Debt gravity A leveraged institution carries a peculiar constraint. It owes tomorrow. Its infrastructure therefore cannot be evaluated entirely according to elegance, human usefulness or technical efficiency. Revenue must grow. Customers must remain customers. Capital must receive a return. Forecasts must become reality. This creates what might be called debt gravity. Once enormous organizations acquire enormous fixed obligations, everything begins bending toward maintaining the structure: premature scaling, customer capture, recurring subscriptions, data extraction, acquisitions, regulatory moats, identity systems, ecosystem lock-in, personalised pricing, algorithmic risk classification. Not because every participant is malicious. Because the balance sheet itself has acquired a survival instinct. The software eventually begins protecting the institution that financed the software. And the programmer discovers that he is no longer merely designing machines. He is maintaining the cognitive apparatus of a debt structure. Then comes Shiva This is where the technological history intersects beautifully with Shaiva metaphysics. Shiva is not merely “the destroyer.” In Nataraja, Shiva contains creation, preservation and destruction simultaneously. The drum announces creation. The raised hand gives protection. The flame destroys the exhausted form. Beneath his foot lies apasmara — ignorance and illusion. The dance continues. The Metropolitan Museum describes Nataraja precisely in these terms: creator, preserver and destroyer united within an endless cycle rather than competing as separate forces. So when we say: Shiva always wins the metaphysical claim need not mean that destruction triumphs. It means something much more severe: no constructed form gets to declare itself permanent. Not empires. Not banks. Not corporations. Not operating systems. Not monetary architectures. Not technological monopolies. Not even blockchains. Whatever remains aligned with reality is preserved. Whatever can transform is transformed. Whatever depends upon maintaining illusion eventually encounters the fire. That is why engineers repeatedly appear at civilizational boundaries. They discover that yesterday's indispensable institution has become tomorrow's unnecessary abstraction. The railway survived its financiers. Communication survived the Bell monopoly. Networking escaped proprietary protocols. Software escaped proprietary Unix. Cryptography escaped governments. Money acquired a peer-to-peer implementation. And now verification itself is escaping the institution. The financier sees disruption as destruction. The engineer sees a migration. Shiva sees neither. It is simply time for the architecture to change. The deepest technological revolution is therefore not blockchain versus banks. It is not programmers versus financiers. It is the ancient conflict between the living system and the structure that mistakes itself for eternal. The living system eventually routes around the structure. The protocol survives the corporation. The knowledge survives the credential. The network survives the gatekeeper. The human survives the balance sheet. And the dance continues. The engineer builds. The institution encloses. The protocol escapes. Shiva clears the obsolete abstraction. The engineer builds again. #ShivaAlwaysWins #DebtGravity #TechnologyAndFinance #Blockchain #Bitcoin #OpenProtocols #DigitalSovereignty #Decentralization #PeerToPeer #OpenSource #LocalCompute #FinancialSovereignty #ProtocolOverPlatform #Permissionless #HumanScale #BuildWhatDoesNotOweTheFuture

Never before has technology converged so completely around a clean dividing line: the indebted and the unindebted. Debt is no longer merely something sitting on a balance sheet. At sufficient scale, it becomes an architecture of behaviour. A debt-backed industry cannot simply ask: What should we build? It must ask: What must keep growing so the structure can continue servicing itself? That creates a peculiar cognitive dissonance. Premature scaling is rewarded. Complexity becomes defensible. Extraction becomes optimisation. Surveillance becomes personalisation. Lock-in becomes convenience. Exclusion becomes risk management. And every layer of debt increases the gravitational pull toward the next layer. Eventually the technology stops serving the individual and begins constructing increasingly personalised apparatuses for predicting, pricing, sorting and excluding the individual — because the machine cannot tolerate uncertainty where repayment is concerned. This may be one of the defining technological boundaries of our age: systems that must continuously extract future value to remain solvent, versus systems that can simply exist, verify, transact and survive. The deepest technological sovereignty may therefore be surprisingly simple: build things that do not owe the future. #DebtGravity #TechnologicalSovereignty #DigitalSovereignty #Bitcoin #NodeRunner #LocalCompute #OpenSource #Decentralization #SelfSovereignty #DebtFree #HumanScale #Privacy #Resilience #Verification #BuildTheFuture #FreedomTech

I’ve been chipping away at ECAI for long enough now that I should probably have developed the good sense to stop. Meanwhile, the AI industry continues its heroic march toward making probability increasingly expensive, increasingly convincing, and increasingly difficult to distinguish from certainty. Fair play. Thousands of brilliant people, obscene amounts of compute, magnificent infrastructure — all working very hard to make the guess a little less guessy. And I’m still over here being mildly inconvenient, asking whether intelligence might be better served by retrieving the right structure than statistically improvising one. Could be completely wrong, of course. That would certainly be the more socially convenient outcome. I remain genuinely impressed by what the industry has built. The engineering is extraordinary. I’m just not entirely convinced that making the roulette wheel bigger eventually turns it into a compass. So, with all appropriate humility, I’ll keep chipping away. Quietly. Would hate to interrupt the convergence. #ECAI #ArtificialIntelligence #DeterministicComputing #EllipticCurves #FutureOfComputing

When the programmer finds Shiva, he does not find an escape from the machine. He finds the stillness from which the machine can be seen clearly. Shiva is not destruction for its own sake. He is dissolution: the ending of avidyā—ignorance, false identification and the illusion that temporary forms are eternal. The third eye is discernment. The fire is transformation. The dance is the ceaseless arising and passing of worlds. Code, credentials, deadlines and corporate hierarchies are revealed as instruments—not the Self. The programmer may still build, but no longer mistakes the abstraction for reality or productivity for being. What is false is surrendered. What is useful remains. What is true survives the fire. When the programmer finds Shiva, the body is not discarded. It is reclaimed as part of the discipline. The mind becomes an instrument again. The ego ceases pretending to be the operator. The program continues. The possession ends. ॐ नमः शिवाय #Shiva #Nataraja #Programmer #Avidya #Discernment #Transformation #CyberDharma #DigitalSovereignty

Vamama steps ... View quoted note →

The fittest programmer in the room is still expected to live like a farm animal for software empire. Built body. Sharp mind. Fast hands. And still the trillion-dollar software machine wants him seated, softened, managed, risk-scored, compliance-trained, emotionally flattened, and drip-fed little dopamine pellets called tickets, sprints, perks, and stock grants. The modern programmer is one of the most physically under-deployed high-performance humans in history. A man who can hold architecture in his head, debug under pressure, learn any system, survive sleep deprivation, train through pain, and adapt at speed — reduced to moving rectangles around corporate dashboards so some bloated institution can preserve its market position for one more quarter. That is not a talent shortage. That is a containment strategy. The fit athletic programmer is especially dangerous to the system because he is harder to pacify. He knows discipline in the body translates to discipline in the mind. He knows suffering can be metabolized into competence. He knows hierarchy is often theater. He knows most “best practices” are just ritualized fear. And once he realizes that half the industry runs on political insulation, process inflation, and managed dependency, he becomes very difficult to domesticate. The trillion-dollar software industry does not merely employ intelligence. It captures it. It takes the hacker instinct — curiosity, sovereignty, aggression, ingenuity, refusal — and repackages it into safe, salaried obedience. It wants builders without rebellion. Operators without independence. Athletes of cognition trapped in ergonomic cages. So the breakout begins when the programmer remembers: You were not built to be a ticket-processing organ for dead corporate mass. You were not built to sacrifice your endocrine system to Jira. You were not built to become physically weak while maintaining failing abstractions for people with no skin in the game. Lift. Run. Build. Ship. Fight. Learn. Refuse. Reduce dependency. Cut costs. Own your stack. Own your tools. Own your body. Own your time. Own the consequences. The ultimate break is not quitting your job to become a lifestyle mascot. The ultimate break is reclaiming hacker dominance: A body that can endure. A mind that can cut through noise. A nervous system that doesn’t beg institutions for permission. A builder who can create outside the empire. Because once the programmer becomes physically sovereign, financially harder to corner, and technically independent, the whole spell starts to fail. And that is what terrifies industrial software most: Not bad coders. Not loud critics. But disciplined men who can build, think, adapt, and no longer need the machine to authorize their existence. #programming #software #hacker #builders #tech #discipline #sovereignty #fitness #coding #startup #indiehacker #systems #masculinity #engineering

Big Tech no longer merely supplies tools to government. It increasingly supplies the substrate through which government operates. Identity is authenticated through privately controlled devices. Public speech travels through privately governed platforms. Payments depend on proprietary operating systems and app stores. Evidence lives in commercial clouds. Location, health and behavioural data pass through vendor infrastructure. Increasingly, access to work, banking and public services requires compliance with software nobody voted for and few officials can meaningfully inspect. This creates a constitutional risk without requiring a conspiracy. A constitution limits public power through jurisdiction, due process, transparency, appeal and institutional separation. A software platform is governed by licences, technical permissions and commercial policy. Its decisions may be immediate, automated and difficult to challenge. When the state builds itself upon that platform, public authority inherits private architecture. The individual can then be: • identified without meaningful anonymity • profiled without being accused of anything • restricted without receiving a hearing • excluded without a judicial order • monitored without knowing which systems are communicating • denied access because an automated risk model produced the wrong result • forced to accept changing licence terms merely to remain socially functional The danger is not simply that corporations possess too much data. It is that private systems can become the practical boundary of citizenship while remaining legally described as optional consumer products. A government may be restrained by constitutional law, yet still obtain the practical effect of unrestricted power through infrastructure whose permissions are written in code and whose sanctions are called “service decisions.” At that point, the licence begins to resemble law—but without democratic enactment. The account becomes an identity document. The device becomes a checkpoint. The platform becomes a jurisdiction. “Accept” becomes coerced consent. Disconnection becomes a form of civil exclusion. The answer is not the abolition of technology. It is constitutional discipline at the infrastructure layer: Public power must remain auditable. Essential services must be interoperable. Automated decisions must be explainable and appealable. Citizens must retain meaningful offline and open-standard alternatives. No vendor should possess an unreviewable power to erase a person from functional society. If government cannot operate independently of a corporation, the corporation is no longer merely a contractor. It has become an unelected chamber of government. #BigTech #DigitalRights #ConstitutionalLaw #CivilLiberties #DigitalIdentity #Privacy #DueProcess #OpenStandards #DigitalSovereignty #RuleOfLaw

A practical guide to sheep herding and running an Australian software company Step one: acquire a paddock. Call it a “digital transformation practice.” Fill it with bright people, give each a Jira ticket, and ensure none can see more than three weeks beyond the fence. Step two: appoint sheepdogs. They do not write software. They move calmly between spreadsheets, stand-ups, procurement meetings and risk committees, keeping the flock facing the same direction: toward another discovery phase. Step three: never build the thing that threatens the paddock. A product with its own infrastructure, its own customers, its own payment rails, its own technical direction? Far too dangerous. Better to sell 800 hours of “strategy”, then import a SaaS subscription from California and call the invoice innovation. Step four: worship the temporary contractor. Pay a premium for someone who will leave before the consequences of their architecture arrive. Call permanence “key-person risk.” Call competence “hard to resource.” Call ownership “not aligned with the engagement model.” Step five: make every engineer a consultant and every consultant a PowerPoint artisan. No builder may hold the whole system in their head. That would be a single point of failure. Better to distribute the failure across fourteen vendors, three cloud accounts, an offshore queue, and a steering committee that meets monthly to ask why delivery is delayed. Step six: declare victory when the dashboard is green. Never mind whether the customer can use the product, whether the system survives load, or whether anyone can explain its data lineage. The transformation is complete because the slide has a blue gradient and the project has entered “hypercare.” Australia has extraordinary engineers. What it often lacks is an institutional appetite for letting them build anything that might outgrow the procurement cycle. The national software industry does not have a talent shortage. It has a courage shortage. Too many organisations want a safe flock; too few want a sovereign machine. #AustralianTech #SoftwareEngineering #Startups #Innovation #BuildInPublic #EngineeringLeadership

🔥 Active dhyāna does not erase the past. It changes the geometry from which the past is perceived. Memory is not a dead archive. Each time a memory is recalled, it is reconstructed inside the nervous system of the present. Neuroscience describes part of this through memory reconsolidation: reactivated memories can become plastic enough for their emotional associations and meaning to be updated through new experience. This is where dhyāna becomes more than relaxation. Attention changes perception. Perception changes interpretation. Interpretation changes the meaning carried by memory. Meaning changes the action produced from memory. The historical event may remain fixed while its sovereignty over the present collapses. And this is where dharma and karma meet. Karma is not merely some cosmic accounting system outside the person. At the human scale, karma is also pattern becoming consequence: memory → perception → desire/fear → reaction → action → consequence → reinforced memory. An unconscious being keeps feeding the loop. Dhyāna introduces awareness into it. Dharma introduces right action. Non-attachment prevents the action from becoming another chain. The Bhagavad Gita repeatedly points toward this: act fully, but relinquish possession of the fruits of action. Krishna's path is not passivity. It is action without bondage. And the Gita goes further: “As a blazing fire reduces wood to ashes, so does the fire of knowledge reduce all karma to ashes.” — Bhagavad Gita 4:37 This is the deeper path toward the destruction of karmic bondage. Not pretending the past never happened. Not escaping consequences already in motion. But progressively removing the machinery that manufactures another future from the unconscious past. Dhyāna reveals the pattern. Jñāna reveals what is not the pattern. Dharma determines the next action. Vairāgya releases attachment to its fruits. Then karma loses its reproductive mechanism. Patañjali approaches the same frontier through the stilling of the movements of mind: consciousness ceases to be dragged helplessly through every inherited fluctuation. Christian scripture reaches toward transformation through another vocabulary: “Be transformed by the renewing of your mind.” — Romans 12:2 The memory remains. But the being encountering the memory is transformed. Trauma says: «Because this happened, the future must resemble the past.» Dhyāna interrupts that recursion. Dharma chooses differently. Non-attachment refuses to build identity around the outcome. And knowledge eventually burns the assumption that the conditioned pattern was ever the whole Self. Memory provides the state. Attention provides the lens. Dharma provides the action. Non-attachment breaks the chain. Knowledge burns the bondage. Perhaps this is one way to understand the destruction of karma: not the destruction of causality, but the destruction of the compulsion to endlessly recreate oneself through it. 🔥 #Dhyana #Dharma #Karma #KarmaYoga #Jnana #Vairagya #Meditation #Memory #Neuroscience #Trauma #Cognition #Consciousness #BhagavadGita #Yoga #Scripture #Being #Liberation

THE NODE RUNNER’S ODYSSEY Your node verifies blocks. It does not verify the market’s opinion of your worth. An important distinction, routinely lost somewhere between the third liquidation screenshot and a podcast explaining why your cortisol spike is actually bullish. Markets are coordination mechanisms, not metaphysical tribunals. Their consequences are real. The illusion is that their latest mood constitutes a verdict on your intelligence, your work, or your right to feel at peace. A price can fall without your life becoming a failed transaction. For the node runner, the deeper discipline is knowing which signals deserve authority. An invalid block does not become valid through sufficient enthusiasm. Likewise, somebody else’s urgency does not automatically become your obligation. There is no consensus rule requiring you to be psychologically available to every candle. The sirens have affiliate links now. They still want you to abandon the ship. Tie yourself to something sturdier than the feed: principles you can explain without a chart, people who know you without your portfolio, work that remains useful when nobody is applauding. But do not confuse the mast with a cage. You are allowed to revise a thesis without liquidating your identity. You are allowed to change course. Logging off is not capitulation, and exhaustion is not a superior form of conviction. Proof of work need not become proof of suffering. After the storm, let recovery be almost offensively ordinary. A proper meal. Some daylight. A conversation with no market thesis concealed inside it. Music that does not improve your productivity. An evening that produces absolutely nothing for the dashboard. Let someone know when you are struggling. Friendship is allowed to have more bandwidth than a reaction emoji. Professional support is not a compromise of sovereignty; neither is needing another human being. You do not have to convert every wound into content, every setback into wisdom, or every quiet hour into preparation for the next campaign. Some things deserve care before they deserve an explanation. The point of the odyssey was not to become exceptionally good at enduring shipwrecks. It was to return. Ithaca is not a price target. It is being able to sit at your own table without the market sitting inside your chest. To recognise your friends. To inhabit a life larger than the ordeal that occupied it. Run the node. Maintain the human. The network can operate around the clock without requiring your vigilance around the clock. Come home with more than your keys intact. #NodeRunners #Bitcoin #DigitalSovereignty #EmotionalResilience #MentalHealth

Tap-to-pay exposes one of the least discussed power structures in modern computing: the operating system–OEM–payments nexus. A phone may have NFC. The operating system may have the cryptography. The hardware may have a secure element. The bank may issue the card. And yet payment can still fail. Why? Because contactless payment is not simply a hardware capability. It is a chain of institutional trust: Bank → card network → wallet provider → operating system → device certification → OEM → secure hardware → payment terminal Break one link and the phone may remain perfectly capable of NFC while being excluded from the payment system. That distinction matters. Linux can read NFC. Linux can sign transactions. Linux can run hardened cryptography. Linux can communicate with payment infrastructure. What it generally cannot obtain by itself is the commercial attestation accepted by the incumbent payment network. So the moat is no longer merely: > “Can your computer perform the operation?” It is increasingly: > “Does the institution controlling the operation recognize your computer as legitimate?” This is where operating-system freedom collides with financial infrastructure. A locked-down OEM platform is valuable not only because it ships software, but because it carries a bundle of certifications, hardware identities, commercial agreements and trust relationships that independent operating systems cannot simply reproduce from source code. That makes the smartphone payment stack a revealing example of modern platform power: hardware capability is open-ended; economic capability is permissioned. And it explains why replacing Android or iOS is much harder than replacing a desktop operating system. You are not merely replacing an OS. You are attempting to leave an entire OEM–identity–attestation–payments trust domain while continuing to participate in services built around it. That is the real frontier for sovereign mobile computing. #Linux #OpenSource #NFC #Payments #DigitalSovereignty #GrapheneOS #UbuntuTouch #Fintech #Cybersecurity #MobileComputing #OpenHardware #Bitcoin

Le Burgelle with fries 🍔 🍟

Humanity’s most successful-ish attempt at going cosmic may begin with invariants. Bitcoin uses elliptic-curve structure to make ownership and verification portable across any distance. Orbital mechanics reads a cosmos whose motion is already constrained by conserved relationships. Different mathematics. Same instinct: Don’t impose order on the universe. Read the signboards already written into it. Everything out there is moving, but not everything is changing. That’s what invariants are for. 🌌⚡ #Bitcoin #CosmicWallet #EllipticCurves #Invariants

What moves me most about the meeting of Eastern and Western metaphysics is not how easily one defeats the other. It is how strangely they begin to converge around the same unbearable questions. The East asks: What is the self? What survives death? What binds us to consequence? What is liberation? What lies beyond form? The West asks: What is sin? What is judgment? What is grace? What is resurrection? What does it mean for God to enter history? And then, at the centre of the Christian claim, stands Christ. Not merely explaining suffering. Entering it. Not merely teaching detachment from death. Passing through death. Not merely describing judgment. Bearing judgment. Not merely speaking of liberation. Offering mercy to the guilty. This is where the metaphysical languages begin to touch. Karma asks that consequence be real. Dharma asks that order be real. The prophets ask that justice be real. The philosophers ask that truth be real. The Cross answers with something almost impossible: justice without abandoning mercy, truth without abandoning the sinner, death without surrendering the body, and transcendence without despising creation. The Resurrection is therefore not an escape from the world. It is the claim that creation itself can be redeemed. Perhaps this is why Christ can feel so startling when approached from both directions. The Eastern seeker recognizes the depth of transformation. The Western seeker recognizes the gravity of history. And at the Cross, transcendence and incarnation meet. Not as conquest. Not as cultural erasure. But as mercy. The deepest convergence is not that every tradition secretly says the same thing. It is that humanity keeps arriving at the edge of the same abyss— death, guilt, consequence, longing, eternity— and Christianity places at that edge not an argument, but a wounded God saying: “Come.” #Christ #TheCross #Resurrection #Shiva #Dharma #Karma #Moksha #Metaphysics #EasternWisdom #WesternTheology #ChristianMysticism #DivineMercy #Grace #Justice #EternalLife #Spirituality #Philosophy #SacredTraditions #Truth #DivineLove

A programmer who has operated systems long enough develops a strange relationship with death. "kill". Process gone. Supervisor restarts it. Resources return. State is recovered. The machine continues. On the BEAM we even teach: let it crash. After thousands of terminated processes, you understand something very clearly: termination is not necessarily violence. It can simply be lifecycle. And this gives an unexpectedly useful lens into the metaphysics surrounding Shiva and Yamaraj. In the traditional architecture, Yamaraj is not merely a celestial executioner. He is Dharmaraja: death joined to judgment. Chitragupta represents the accounting layer—the record of deeds from which consequence follows. Shiva sits deeper still: dissolution, transformation, the end of the form rather than hatred of the thing possessing the form. In the Markandeya tradition, Shiva can even interrupt Yama himself. Think like an operator. Yamadutas: event transport Chitragupta: audit log Yamaraj: adjudication Karma: causal history Shiva: lifecycle boundary Moksha: exit from the scheduler altogether Not scripture as software architecture. A programmer's metaphor for an extraordinarily old metaphysical intuition. And look at the throughput. Humanity currently experiences roughly 63 million deaths a year. ~173,000 per day. ~7,200 per hour. ~120 per minute. ~2 per second. Yet the divine imagination does not require twelve departments, a ticketing system, three approval meetings and someone saying: “That wasn't my responsibility.” Action and consequence remain connected. That is the crucial difference. Human developers know exactly what happens when systems become too fragmented: observability collapses. Nobody owns the transaction. One service emits the event. Another transforms it. Another authorises it. Another executes it. Another records it. Eventually something catastrophic happens and every component reports: 200 OK. This is why modern institutional violence is metaphysically terrifying. We have taken the operator's capacity for abstraction— the ability to terminate something without emotion— and applied it to human beings. A soul is not a process. That is precisely the point. The divine metaphysics of death attempts to preserve accountability all the way through the transition. Human bureaucracy can optimise accountability out of the workflow. Shiva destroys form. Yama accounts for consequence. But empire discovers something much darker: how to distribute destruction across enough human operators that nobody experiences himself as the destroyer. The gods require an accounting. The machine requires only that the ticket be closed. #Shiva #Yamaraj #Metaphysics #Dharma #Karma #Moksha #DivineOrder #SystemsThinking #SoftwareEngineering #DevOps #Accountability #InstitutionalViolence #MoralResponsibility #Bureaucracy #Philosophy #Technology #Conscience #Operators #Civilisation #HumanSystems

What the occidental East does not know about the occult West: The West did not arrive in Asia as a purely rational machine. Behind the census, the map, the dictionary and the legal code stood an older metaphysical architecture: revelation and heresy, God and adversary, salvation and damnation, the sacred image and the idol, the true religion and the false one, history moving toward judgement. Colonialism did not merely collect information. It classified entire civilizations through categories carrying centuries of theological weight. That is why translation could become inversion. Śiva’s destruction becomes darkness. Kālī’s terror becomes demonology. Tantra becomes occultism. Satī becomes widow-burning. Plural metaphysics becomes “superstition.” The irony is that the East was being called mystical by a civilization whose supposedly secular institutions were themselves built over a deep theological substrate. The Occidental East learned to see the West as rational. It rarely learned to see the occult West hiding inside the categories of rationality. Empire’s most durable conquest is not territory. It is the vocabulary through which the conquered eventually explain themselves. #Shiva #Metaphysics #Colonialism #History #India #Philosophy #Epistemology #Decolonisation

THE CONVERGENCE INTO DAMAGE The fat abstraction stack is reaching its economic limit. So is the model built around it. For decades, proprietary software could justify itself by controlling the interface, hiding the machinery, and selling access to progressively higher layers of abstraction. Operating system. Runtime. Framework. Cloud. Control plane. Managed service. Subscription. Each layer promised simplicity. Together they produced dependency. Now the economics are turning against the stack. Software labour is becoming harder to price in unstable fiat. Infrastructure costs keep accumulating. Security attack surfaces expand with every dependency. Senior engineering knowledge gets reset by constant technological churn. And increasingly, the most valuable optimisation is not adding another abstraction. It is deleting one. This is where closed systems face their hardest problem. A proprietary platform must continuously justify the toll booth. An open system only has to keep working. As compute becomes cheaper, open-source tooling matures, protocols stabilise and organisations rediscover boring primitives, the economic premium on owning the abstraction begins to collapse. The future may therefore look less like: MORE SOFTWARE. And more like: LESS SOFTWARE. FEWER LAYERS. OPEN PROTOCOLS. LONG-LIVED SYSTEMS. LOCAL OWNERSHIP. VERIFIABLE BEHAVIOUR. That convergence creates massive DAMAGE. Not destruction for its own sake. Damage to unnecessary abstraction. Damage to vendor lock-in. Damage to unverifiable claims. Damage to technical churn masquerading as innovation. Damage to an economy that survives by repeatedly making solved problems expensive again. The great software opportunity is no longer another layer above the machine. It is restoring a direct, inspectable and verifiable relationship between the operator and the machine. When the abstraction empire contracts, verification becomes more valuable than presentation. And that is the terrain DamageBDD was built for: Define the behaviour. Execute it anywhere. Verify what actually happened. Produce the proof. The next software cycle may not be an expansion. It may be a controlled demolition. #DamageBDD #OpenSource #Software #Engineering #Verification #Linux #Infrastructure #TechnicalDebt #Bitcoin

CAPTURE BY ABSTRACTION Software does not always capture you by owning the machine. Sometimes it captures you by owning the layer through which you are allowed to understand the machine. The hard problem gets solved. Then an abstraction is placed over it. Then another abstraction is placed over that. Soon the engineer no longer works with the primitive. They work with the framework. Then the platform. Then the managed service. Then the proprietary control plane explaining the abstraction that replaced the abstraction. This is abstraction capture. And abstraction misdirection is how it stays justified. A solved problem is presented as a new category. A stable primitive becomes “legacy.” A familiar stack becomes “technical debt.” The replacement arrives with new terminology, new certifications, new dependencies, new migration work and a fresh scarcity of expertise. Nothing fundamental may have changed. But the map has changed enough that everyone must learn the territory again. That resets accumulated knowledge. It creates churn. It turns engineering memory into depreciating capital. And it moves control upward toward whoever owns the newest abstraction layer. Good abstraction removes unnecessary complexity. Capture by abstraction does the opposite: It hides simplicity behind enough machinery that access to the simple thing becomes commercially valuable again. The deepest form of platform capture is not locking you into a product. It is convincing you that the primitive underneath it is too difficult, too old, or too dangerous to touch directly. Abstraction should compress complexity. When abstraction starts manufacturing dependency, it has stopped being an engineering tool. It has become a control surface. #Software #ComputerScience #Abstraction #Engineering #TechnicalDebt #PlatformEconomy #OpenSource #SystemsThinking