@charles_irl: many are saying this
Summary
A quote tweet pushing back on trendy 'performance slop' in timelines, arguing that real performance engineering means profiling CPU, heap, disk, and network and shrinking the biggest bars on those profiles.
View Cached Full Text
Cached at: 11/02/26, 08:13 PM
many are saying this https://t.co/2JRGL85TPM
Botir Khaltaev (@botirkhaltaevv): i’m seeing so much performance slop in the timeline.
> “How can we use data-oriented design principles”
> “Can we turn this pointer into an index”
Perf eng is get CPU flamegraph, maybe some heap , disk , and network profiles.
Make biggest bar on these profiles smaller, if
Similar Articles
@GergelyOrosz: So much sw today doesn’t care much about perf. It just feels sluggish. And everyone seems to have accepted it. Except w…
Gergely Orosz discusses how modern software often neglects performance, citing examples like Bun and Linear, and highlights a fast demo of Superlogical for tmux by Mitchell Hashimoto.
Optimize for change not application performance
The article argues that software teams often over-optimise for micro-performance benchmarks at the expense of developer experience and engineering throughput, which are the true bottlenecks for long-term delivery speed and maintainability.
@GergelyOrosz: More engineers should do this kind of napkin math and ask: “what is the *theoretical* limit of throughput for this syst…
The tweet highlights a fireside chat at AIE Worlds Fair where Simon Eskildsen emphasizes the value of napkin math for estimating theoretical system throughput limits and understanding why actual performance differs.
@GergelyOrosz: Have we been using "premature optimization is the root of all evil" wrong, all this time? I always assumed this means "…
A discussion questioning the common interpretation of premature optimization in software development, referencing insights from performance expert Casey Muratori.
When Impressive Performance Gains Do Not Matter
A blog post discussing how performance improvements that fail to cross the 10-second attention threshold may not yield user experience benefits, using examples from database query optimization and process automation.