feeds - Binary Igor

home | feeds |donate

Binary Igor

Some things are either 0 or I. Deeper and broader thinking on commanding binary machines; for programmers and developers driven not just to implement, but to understand deeply, design and build.

the joy and power of understanding

modern frontend complexity: essential or accidental?

json documents performance, storage and search: mongodb vs postgresql

data consistency: transactions, delays and long-running processes

mysql vs postgresql performance: throughput & latency, reads & writes

authentication: who are you? proofs are passwords, codes and keys

modular monolith and microservices: parallel work, independent deployments and organization scalability

modular monolith and microservices: data ownership, boundaries, consistency and synchronization

optimistic vs pessimistic locking: concurrency control, conflicts, lost updates, retries and blocking

bitcoin core code: c++, some python and a custom build system

centralized vs decentralized identity tradeoffs: twitter/x, youtube, mastodon, activitypub and nostr

eventsql: events over sql

bitcoin p2p network: peer discovery, reachability and resilience

multi vs single page apps: user experience, performance, complexity and more

react and htmx: different abstractions, different tradeoffs

sqlite db: simple, in-process, reliable, fast

mysql and postgresql: different approaches to solve the same problem

htmx with shoelace web components: using framework-agnostic components in an example app

programmer in wonderland

who controls the internet and how it works?

simple yet scalable web analytics: json in sql with batch inserts

modular monolith: dependencies and communication between modules

htmx: a setup ready for production

load testing: how many http requests/second can a single machine handle?

kubernetes: maybe a few bash/python scripts is enough

htmx and web components: a perfect match

modular monolith and microservices: modularity is what truly matters

unit, integration, e2e, contract, x tests: what should we focus on?

index: a crucial data structure for search performance

htmx: simpler web-based app/system

indexing, partitioning, sharding - it is all about reducing the search space