You are a 1000x maker, and you can't think of how to make your stack 10x better?

José Valim challenges the impulse to surrender system-level improvements to generative agents and instead urges experienced engineers - those he calls "1000x makers" - to use their leverage to make entire stacks dramatically better. He argues that focusing solely on language switches like Rust misses broader opportunities: make Ruby an order of magnitude faster, give Rails real concurrency, design a powerful gradual type system that can offer safety beyond current options, embed SQLite with a replication protocol to shrink deployment complexity, and harden critical infrastructure like database pools to preempt frequent bugs. He points to Phoenix shipping presence as an example of solving a deceptively hard systems problem well, and asserts that improving core platform primitives matters more than letting agents merely churn out application code.

Responses in the thread reflect the debate: one contributor urges epistemic humility about any single new technology being the universal answer, while others note core teams and community members are already working on many of these improvements and emphasize building for human needs. A specific technical counterpoint highlights fiber-based advances that already make Ruby stronger at concurrency, underscoring that both tooling shifts and deliberate platform engineering deserve attention rather than abandoning one for the other.