Every Team's Rust Evangelist vs. Sprint Progress
Description
This is a meme using a still from the TV show 'The Office.' It depicts a man in a blue shirt (representing 'the rest of the devs working through sprint tickets') looking down with intense focus. Behind him, a woman with glasses and a red patterned shirt has her hand on his shoulder and is smiling with overwhelming enthusiasm. She represents 'that one dev who wants to re-write everything in Rust.' The meme humorously captures a common team dynamic where the majority of developers are pragmatically focused on completing their assigned tasks within a sprint, while a single, passionate developer advocates for a complete and often disruptive rewrite using a trendy or technically 'superior' language like Rust. For senior developers, this resonates with the constant tension between maintaining velocity on existing projects and indulging in large-scale refactoring or technology migration projects that, while potentially beneficial in the long run, are high-risk and derail short-term goals
Comments
7Comment deleted
That Rust evangelist has a point. If we rewrite everything, we'll finally have a bug-free system... right around the time the company goes out of business from us not shipping anything
Burndown was looking healthy until the Rust evangelist opened a PR called “cargo new prod” - apparently sprint capacity can’t be borrowed as mutable
Every team has that one senior engineer who's convinced the entire legacy codebase would run 10x faster if we just rewrote it in Rust - meanwhile, the rest of us are trying to explain to stakeholders why the login button moved 2 pixels to the left
Every sprint planning has that one engineer who's read the Rust book over the weekend and is now convinced the entire codebase's memory safety issues can only be solved by a six-month rewrite. Meanwhile, the rest of the team is just trying to ship the authentication bug fix that's been in 'In Progress' for three sprints because someone keeps bikeshedding about whether we should use bcrypt or argon2
Big‑bang rewrites are org-wide GC pauses - the borrow checker won’t negotiate with sales or the SLA
Team closes tickets; that dev closes lifetimes - sprint velocity optional
That dev pushing a Rust rewrite during sprint? Great - until cargo hits the FFI boundary with our 2003 Oracle driver and the CFO marks the ROI “unsafe”