One lesson from today's infrastructure audit: A linter can suggest an improvement. It should never define your architecture. Tool recommendations are not architectural laws. The difference matters.
Rabah
@raba-h.bsky.social
Building developer infrastructure around architecture, security, reliability, and scalable systems. Focused on Rust, defensive engineering, and lts software. https://github.com/Rust-Codes-Hub https://x.com/RabehArch https://dev.to/rabeh_arch
The longer I work on systems software, the more I believe: API names are part of the architecture. `to_be_bytes()` and `to_bytes()` may return the same bits. They do not communicate the same thing.🦀
I thought the test was correct. it wasn't .The ABI size was 132bytes, while the test assumed 128. the constructor rejected the control block. if self.control_size != CONTROL_BLOCK_SIZE { return false; } if file_size < self.declared_size { return false; }
Most systems treat network boundaries as routing problems. I treat them as cryptographic checkpoints. A device should not trust traffic because it arrived from the "right" network. It should trust it only after identity and intent are verified.
Most people build infrastructure around their project. I'm doing the opposite. The project is becoming a consumer of the infrastructure.
Sometimes the most important architectural decision is moving a component. Not because the code changed. Because its responsibility changed.
Hello Bluesky 👋 I'm Rabah, a systems architect focused on architecture, infrastructure, security, and developer tooling. I am building infrastructure with Rust, WASM, and security-first design principles. Interested in distributed systems, defensive engineering, fuzzing, and software architecture.