The things we write about.
A single source of truth for languages, frameworks, databases, architectures, patterns and concepts. Every entity is a canonical hub.
Programming language
Framework
Laravel
Productivity-focused PHP framework with an Active Record ORM (Eloquent) and a rich ecosystem.
Symfony
Explicit, component-based PHP framework with a Data Mapper ORM (Doctrine) and a strict architecture.
React
JavaScript library for user interfaces with Server Components and a component-based model.
Vue
Progressive JavaScript framework for user interfaces with the Composition API.
Next.js
React framework with the App Router, Server Components and server-side rendering.
Technology
Architecture
Pattern
Strangler Fig
Incremental replacement of a legacy system behind a facade, one slice at a time.
Expand/Contract
Backward-compatible change in three steps: add the new, migrate, remove the old.
Outbox Pattern
Write state and event atomically, then deliver via a relay — solves the dual-write problem.
Event Sourcing
State stored as a sequence of immutable events instead of as a current value.
Concept
Long-lived Software
Software that still runs in ten years and can still be changed safely — the purpose of our work.
Reversibility
Keep change cheap instead of predicting the future — build in small, reversible steps.
Domain Logic
Business rules belong in a framework-independent domain, not in controllers or models.
Idempotency
Running an operation several times produces the same state as running it once — essential in distributed systems.
API
The contract through which systems talk to each other — the longest-lived thing a company owns.
API Versioning
Evolve an API without breaking customers — extend compatibly, version cleanly.
Queues & Async
Process work outside the critical path asynchronously — with at-least-once delivery and idempotency.
Multi-Tenancy
One instance serves multiple customers with separated data — the foundation of every SaaS platform.
Observability
Seeing from the outside what happens inside — a design property, not an afterthought.
OIDC
Authentication layer on top of OAuth 2.0 — the foundation for single sign-on.
Testing Strategy
Test where failures are expensive — a question of economics, not coverage.
Caching
A second, faster copy of data — an architectural decision that trades latency against consistency and complexity, not an after-the-fact optimization.
AI
Probabilistic rather than deterministic systems — brought into production with evaluation, guardrails and clear boundaries, not as a demo.
Agentic Coding
Agents that read a repository, plan in multiple steps, change several files and react to test results — in Batunet's reading, the bottleneck shifts away from producing the code.
Resilience
A system whose failure modes are unknown is not finished — contain failures instead of preventing them, retry safely, degrade gracefully, rehearse the failure case.
Data Model
The shape of the data decides a system's longevity more than any choice of framework or database — it outlives the interface, the framework and the database.
Security
Not a feature you bolt on but a property you build into the design — least privilege, defense in depth, secure defaults, trust boundaries.