Engineering notes about systems, not buzzwords.
Practical material on problems that repeat across real systems: architecture, data, operations, recovery and controlled production change.
Why an IT project should not start with the stack
Technology choices become useful only after the process, constraints, data and definition of success are understood.
Read note ↗Offline-first is not simply “works without Internet”
The difficult part is not the local copy — it is versioning, synchronisation and conflict resolution.
Read note ↗Private communications infrastructure: what matters beyond installing a server
A production system also includes identity, media, backup, migration, monitoring and operations.
Read note ↗1C is more than application configuration: stability starts with infrastructure
Performance and reliability depend on the server environment, PostgreSQL, resources, backups and operational discipline.
Read note ↗A backup is not operational until restore has been tested
A backup becomes part of data protection only when recovery is reproducible and verified.
Read note ↗A production update is a transaction, and rollback is part of the release
A safe release records the starting state, checks preconditions and knows the return path before it changes production.
Read note ↗