Post
Building with Rust Inside an Existing Stack
Written during the very early days of Floe, this post reflects on how technical decisions emerge through constraints, discussion, and experimentation.
This article was written during the very early days of Floe, when the project was still taking shape inside an existing engineering organization with its own history, tooling, and technical constraints.
More than a post about Rust itself, it became a reflection on how technical decisions actually emerge in real teams:
- through prototypes,
- discussions,
- constraints,
- existing ecosystems,
- and gradual experimentation rather than clean architectural diagrams.
It also captures part of the atmosphere around the beginning of Floe: small teams, new ideas, a lot of discussions, and the tension between moving quickly and building something maintainable.
The article includes some simplified examples around concurrency, speculative metadata fetching, and the trade-offs we explored while evaluating different parts of the stack.