Heute auf DiscoverToday on Discover
Entdecke, was andere bewegt.Find what moves people.
Geschichten, Gespräche und Ideen aus dem offenen Netz.Stories, conversations and ideas from the open web.
HörbuchAudiobookDas verlorene Bit der Berufung_Teil-1
FolgeEpisode#024 Hol dir die Kontrolle über deine Dateien zurück mit deinem eigenen Home-Server
ArtikelArticleIn Search of Freedom: Life, Death, and Sovereignty in the Himalaya
HörbuchAudiobookDer gläserne Mensch - Aza und Avatar - Die Bytes Detektive
HörbuchAudiobookDas verlorene Bit der Berufung _ Teil-2
Neu zum HörenNew to listen
Alles in HörenAll in Listen#023 Deine SIM-Karte verrät dich!
breakfree
#022 Nur so sind deine Bitcoin wirklich privat
breakfree
#021 Dein Vermögen gehört nicht dir (mit einer einzigen Ausnahme)!
breakfree
#020 So bezahlst du, ohne Datenspuren zu hinterlassen
breakfree
#019 Dein Laptop spioniert dich nicht mehr aus, ist dafür aber schneller
breakfree
#018 So entkommst du der Spyware von Microsoft und Apple
breakfree
#017 Der Algorithmus kontrolliert dich!
breakfree
#016 Wie gefährlich sind Updates wirklich?
breakfree
#015 Ist dein soziales Umfeld dein größtes Datenleck?
breakfree
#014 Unsere Wohnungen sind voll mit Technik, aber nicht verwanzt
breakfree
MenschenPeople
PublikationenPublications
Alle ansehenView allNoch mehr zu entdecken.Keep exploring.
6 Beiträge geladen.6 stories loaded.

THE LIFE OF AN INDUSTRIALISED PROGRAMMER
The Life of an Industrialised Programmer From women's work to disposable human infrastructure. 1843: Ada Lovelace imagines a world of computation before the machine even exists. 1940s: Programming is often classified as women's work. Women develop algorithms, operate early computers and solve problems nobody has solved before. Management frequently treats it as clerical labour. 1950s–60s: Grace Hopper helps revolutionise programming languages. Margaret Hamilton helps put humans on the Moon. Software is suddenly recognised as critical engineering. The profession gains prestige. The gatekeepers arrive. 1970s–80s: Computing becomes institutionalised. The programmer becomes a professional identity. Computers are increasingly marketed to boys. 1990s: The great object-oriented industrial revolution. Objects need factories. Factories need interfaces. Interfaces need architects. Architects need managers. Managers need meetings. Somewhere in the process, the original problem disappears beneath the abstractions. 2000s: The software factory. Agile. Scrum. Stand-ups. Sprints. Story points. Velocity. The programmer becomes an interchangeable unit of delivery capacity. Human intelligence, measured in Jira tickets. 2010s: The cloud cathedral. Microservices. Containers. Kubernetes. YAML. DevOps. Entire teams maintain infrastructure for software nobody fully understands anymore. Production fails at 3 AM. The programmer wakes up. Management calls it ownership. 2020s: The final industrial insult. After decades of reducing programmers to mechanical units of production, the industry announces that machines can now perform their mechanical tasks. The executives celebrate. The programmer develops back pain. The AI generates code. The enterprise generates meetings. The production incident still requires a human. And somewhere, another Jira ticket is born. THEN COMES THE REVELATION. An exhausted programmer discovers Erlang. A language developed back in the 1980s. Processes. Message passing. Isolation. Supervision. Recovery. He reads Joe Armstrong. "Let it crash." Twenty years of enterprise architecture suddenly flash before his eyes. It was there all along. The alternative wasn't waiting to be invented. It was waiting to be understood. And that's the tragedy. The pioneers of computing were exploring the foundations of computation itself. The industrialised programmer inherited factories, frameworks, methodologies and an infinite backlog. We confused industrialising software production with advancing computer science. Now we're industrialising intelligence itself. Perhaps it's time we returned to the foundations. The programmer closes Jira. Opens Erlang. And begins again. The supervision tree is alive. The realm is locked. THE VERIFIED SURVIVE. #Programming #SoftwareEngineering #WomenInComputing #Erlang #JoeArmstrong #BEAM #AI #ComputerScience #DistributedSystems #DamageBDD

THE FINAL VERIFICATION
Technical Report from the Last Standing DamageBDD Node Status: Operational Network condition: Fragmented Model endpoints: Unreachable Consensus peers: One Verification authority: Evidence Final result: The system behaved exactly as the evidence records.

The Tokamak Compiler Platform
The tokamak is not just a fusion reactor. It is a toroidal state machine fighting collapse at the boundary of heat, field, and geometry. The Tokamak Compiler Platform is the natural extension of the elliptical compiler: a deterministic layer for verifying plasma states, compiling lawful field transitions, and recovering stability before disruption becomes damage. Fusion does not need a better guesser. It needs a compiler for the torus. #ECAI #TokamakCompilerPlatform #EllipticalCompiler #FusionEnergy #PlasmaPhysics #DeterministicAI #ToroidalArchitecture #Verification #DeepTech

DNA, elliptic curves, and ECAI compression effects
This is not an article claiming that DNA is secretly an elliptic curve. It is about something more useful: how nature, cryptography, and intelligence all become powerful when information is compressed into structure that can survive transformation. DNA compresses life into sequence, pairing, folding, repair, and replication. Elliptic curves compress trust into compact mathematical proofs. BDD compresses intent into executable behaviour. ECAI points toward the next layer: intelligence compressed into verifiable algebraic movement instead of endless probabilistic prose. The connection is not visual decoration. It is structural. Serious systems do not survive by being flat. They survive by carrying meaning through constraint, curvature, error correction, and verification. That is why this matters. In biology, corrupted structure can become disease. In cryptography, corrupted proof fails verification. In software, corrupted behaviour fails the test. In AI, corrupted meaning becomes hallucination, misinformation, and institutional damage. The thesis is simple: DNA is biological compression. Elliptic curves are trust compression. BDD is behavioural compression. ECAI is intelligence compression. And the Mercy Isogeny is the metaphor for what every serious system needs: a way to transform without losing the truth that makes redemption possible. #ECAI #EllipticCurves #DNA #Compression #AI #Cryptography #Verification #BehaviourDrivenDevelopment #DamageBDD #Bioinformatics #Genomics #TrustInfrastructure #FaithAndReason #TheMercyOfChrist #Truth

Recruiting Christ the Software Engineer
I used the Christ figure here not as decoration, shock value, or religious marketing, but as the strongest available symbol for **truth under execution pressure**. Christ represents the Word made flesh. In software terms, that is the difference between an idea and a working system. A claim that remains abstract can be argued with forever. A claim that becomes code, test, behaviour, verification, and release has entered the world. That is why the image matters. ECAI is not being framed as another fashionable AI tool. It is being framed as a discipline of incarnation: take the highest claim — deterministic intelligence, retrieval instead of guessing, algebraic structure instead of statistical fog — and force it through the narrow gate of engineering. The Christ figure becomes the extreme programming partner because he represents the partner who will not tolerate falsehood. He does not ask for hype. He asks for the failing test. He does not bless architecture theatre. He demands the behaviour. He does not permit the founder to hide inside prophecy, rage, or abstraction. He brings the whole thing back to the workstation: **Does it compile? Does it verify? Does it serve? Does it resurrect after failure?** That is the point of the article. “Recruiting Christ the Software Engineer” is a metaphor for recruiting the highest possible engineering conscience: humility before truth, discipline before spectacle, refactoring before ego, and verification before announcement. In that frame, DamageBDD becomes the body of ECAI. ECAI may begin as a mathematical revelation, but DamageBDD gives it wounds that can be inspected: scenarios, tests, logs, records, outcomes, payments, and proofs. The Christ figure makes that relationship legible. The Word must become executable. Truth must compile. Claims must pass through behaviour. So the image is not saying Christ belongs to software. It is saying software, at its highest level, must answer to truth. #ECAI #DamageBDD #ChristTheSoftwareEngineer #ExtremeProgramming #SoftwareEngineering #BDD #TestDrivenDevelopment #DeterministicAI #Verification #TruthMustCompile #TheWordShips #Erlang #Bitcoin #LightningNetwork #BuildInPublic #FounderMode #RefactorTheWorld

Two mathematicians at lunch, trying to understand modern AI
Two accomplished mathematicians sit down for coffee and try to understand the modern AI paradigm. No panic. No hype. No pitch deck. Just proof-minded people watching an industry confuse probability with intelligence, benchmarks with truth, and agents with accountability. A light-hearted conversation about the clown show — and why the future belongs to systems that can prove behaviour under pressure. #ECAI #DamageBDD #AI #Mathematics #DeterministicAI #FormalVerification #Cryptography #EllipticCurves #BDD #Verification #TechLeadership #SoftwareEngineering #Nostr #LinkedIn






























