Weekly News - #15

Custom automation that lives outside standard CI platforms should be kept in the same repository as the main project and written in the same language to eliminate the friction of context switching and cross-team dependencies. The system is designed to auto-deploy through a self-bootstrapping script that continuously clones and runs the latest main branch, which means any developer with push access can change production automation through a simple pull request without ops involvement.

The unshare command creates isolated namespaces that virtualize core system resources—PIDs, network stacks, mount points, and user identities—allowing processes to operate with entirely separate views of the system than their parents. While container runtimes orchestrate multiple namespaces behind complex abstractions, unshare exposes this capability directly through the user namespace, which means unprivileged users can create lightweight sandboxes and gain root privileges within them without elevated permissions on the host.

A frontend system processing every customer request was rewritten from C++ to Rust despite functioning perfectly, driven by the friction of extending aging code in a language where safety is optional. Given that any bug could simultaneously affect all customers, the migration was validated through exhaustive testing including side-by-side proxy comparison of live traffic before the Rust version became authoritative.

The megamerge workflow uses an octopus merge commit as the parent of all active branches, allowing developers to simultaneously work on every stream of code they care about in a single combined context. By layering changes on top of this megamerge and using commands like `absorb` and `squash` to redistribute work to specific branches, the system eliminates context-switching friction and prevents surprise merge conflicts without requiring developers to push the merge commit itself.