←

All artices

• Moral Illusions
• The Cage of the Language
• On Stateless Societies
• Technocratic Plimsoll Line
• On Chesterton's Fence
• Jean Monnet: The Guerilla Bureaucrat
• Teaching to Compromise
• On the Nature of Reputation
• Democracy, Bureaucracy, Central Banking
• The Story of the Reichstag
• Musical moment in d minor
• Political Lottery in Switzerland
• Simplest Possible Graph Database
• Steampunk in XIX. century
• Split-a-Dollar Game
• The Human Condition
• Swiss Political System: More than You ever Wanted to Know (III.)
• Swiss Political System: More than You ever Wanted to Know (II.)
• Swiss Political System: More than You ever Wanted to Know (I.)
• Institutional Senescence
• In Search of Slack
• Partying over Internet: Technological Aspects
• The Missing Piece
• Happy Petrov Day!
• On Becoming Clueless
• Type-safeness in Shell
• Hull: An alternative to shell that I'll never have time to implement
• On the Nature of Programming Languages
• The Politics of Age (the Young vs. the Old)
• Muqaata'a by Fahad Himsi (I.)
• Programmatic Code Generation: Composability
• Lydian song
• Tiles: Report on Programmatic Code Generation
• Graceful Shutdown
• Structured Concurrency Cross-language Forum
• Confessions of an Abstraction Hater
• Announcement: A talk about structured concurrency at FOSDEM
• State Machines and the Strange Case of Mutating API
• Equivalence of State Machines and Coroutines
• On Rigorous Error Handling
• Two Approaches to Structured Concurrency
• Unikernels: No Longer an Academic Exercise
• Update on Structured Concurrency
• Coordination Problems in Evolution: The Rise of Eukaryotes
• Coordination Problems in Evolution: Eigen's Paradox
• One-person Universe
• What Can Philosophers Learn from Programmers?
• Anti-social Punishment
• The Eb
• On Interstellar Communication
• The Garden of Forking Paths
• Inadequate Equilibria vs. Governance of the Commons
• Soviet-era Jokes, Common Knowledge, Irony
• Musings on Social Capital
• Research: Rescuers during the Holocaust
• Structured Concurrency in High-level Languages
• Progressivism vs. Conservatism: A Game-theoretic Approach
• Schooling in your Head
• Composable Network Protocols vs. Encapsulation
• Mojim Spoluobčanom (To My Compatriots)
• Documentation Driven Design
• Game-theoretic Approach to Tradition
• Crypto for Kids: Messenger's Story
• Your Share of National Wealth for a Microwave Oven!
• Computational Complexity as a Law of Nature
• Inadequate Equilibria
• Suicide by Culture
• Low Hanging Fruit of Programming Language Design
• Evolving towards Extinction
• Hard Things in Computer Science: Naming things
• A Microstory
• On Modern Propaganda
• Ontogeny Recapitulates Phylogeny
• A Thought on the AI Risk
• On Intellectual Honesty
• A Tale of Two Countries
• Moral Dunning-Kruger
• Kaizen of Programming
• Gift vs. Reputation in OSS
• "Being from a Worker Family"
• On Tolerance
• Infinite Mirrors and Sexual Selection
• Game with Infinite Mirrors
• Reputation Engineering, part III
• Linguistics and Programming Languages
• Reputation Engineering, part II
• Note on Homesteading the Noosphere
• Reputation Engineering, Part I
• Sure, we have imperative and functional. But what about cartesian programming?
• Why is my TCP not reliable (expert edition)
• Digital encoding. Legacy software. Evolution.
• SRE's review of Democracy
• Few thoughts on current political situation
• The Cost of Abstraction
• Debt Cancellation Referendum
• The Birch
• The Awe of Cryptography
• Software Licenses and Failed States
• Performance of green threads and why it matters
• The Nanny World
• Three simple pieces for piano
• The Adventures of Boltzmann Brain (part III)
• The Adventures of Boltzmann Brain (part II)
• Uncertainty principle in economics
• On printing money
• The Adventures of Boltzmann Brain (part I)
• Footnotes to "Select Statement Considered Harmful"
• Select Statement Considered Harmful
• Structured Concurrency
• Getting rid of state machines (II)
• Getting rid of state machines (I)
• Enforced Error Handling
• Software Totemism
• Centrifugal Governor or Why I am not a Libertarian
• Ecology of Software Quality
• Celestial Emporium of Benevolent Knowledge
• Saving the journalism. With bitcoin.
• A really hard problem
• You cannot have at-least-once broadcast
• Be just or be data-driven?
• OO languages spend most effort addressing a minority use case
• Documentation at scale: The principles
• Document intent not algorithm: A use case
• Advanced metaprogramming in C
• Let's stop kidding ourselves about APIs
• The Second Use Case for Literate Programming
• A case for unstructured programming
• Where are Python macros?
• Dissecting Software Component's Reproductive System
• Finish your stuff
• Reusability Trap
• Coroutines in C with Arbitrary Arguments
• A cryptopuzzle. Ready, steady, go!
• Non-interactive zero knowledge proofs for fun and profit
• The Clockwork inside Game of Thrones
• Bullshit jobs
• Magic numbers in C
• Are you a programmer-mathematician or a programmer-handyman?
• Idiot's Guide to ABI Versioning
• Unit Test Fetish
• Design of PUB/SUB subsystem in ØMQ
• Code Generation & Visual Smog in Code (part II)
• Code Generation & Visual Smog in Code (part I)
• In the Defense of Spaghetti Code
• Poor Man's Scientific Method
• The Second Step Towards Immortality
• Bitcoins & Deflation
• Fighting Efficiency
• The Pashalik Syndrome
• Beyond Rational Idiotism
• Tragedy of the Commons and Tragedy of the Privately Owned Land
• Public Key Encryption for Kids
• Backdoors in Encryption Standards and How To Fight Them
• nanomsg: Towards Full-Blown Configuration Management
• Event-driven architecture, state machines et al.
• The Callback Hell
• Getting Rid of ZeroMQ-style Contexts
• TCP and heartbeats
• How to Write a Language Binding for nanomsg
• Using Survey Protocol for High Availability
• Optimising Subscriptions in nanomsg
• Messaging & Multiplexing
• Bus Messaging Pattern
• Implementing Network Protocols in User Space
• Why Communication Infrastructure Should Use Permissive Licenses
• Priotitised Load Balancing with nanomsg
• Location-independent Addressing with Messaging Middleware
• EINTR and What It Is Good For
• The Merit of AMQP (part I)
• Getting Rid of Domain Registrars Using Bitcoin Algorithm
• Enclave Pattern
• Why should I have written ZeroMQ in C, not C++ (part II)
• Does GPL hurt free software?
• Using likely() and unlikely()
• Distributed Computing: The Survey Pattern
• Why should I have written ZeroMQ in C, not C++ (part I)
• Silicon Valley, Hollywood and Iceland as the New Superpower
• Economics of Messaging Software
• ØMQ: Mission Accomplished

Discussion Forum