Casey Muratori
Everything, newest first — across every channel. Their profile →
Hiding
9 September
26 August
From one piece Why performant code matters (but gets widely ignored), with Casey Muratori 12 beliefs, in the piece's order there
-
Their words
I want to recommend that people read a paper. I'm trying to get more people to just to just read papers because I realized I read a ton of papers.
-
Their words
I find there's a lot of like received programming wisdom that's just nonsense. Like clearly no one's ever tested it and if they did they would have found out that it's that there's no actual basis for it.
-
Their words
But it's the cost of the compiler not being able to do any optimizations. That's the actual cost. And that cost can be severe.
+ 9 more
-
Their words
If you look at those things, they're kind of just bad programming practices. I I don't really know how else to say them. They don't mesh well when you put them together.
-
Their words
You go to school for four years to learn this. There's no reason you can't learn this in a few months. It's not that hard.
-
Their words
So the good news is in order to write software that's much better than a lot of the software you use today, you don't have to know that much.
-
Their words
everybody on your team who is making architectural decisions, those people must know performance and they must make decisions that will allow the other people downstream of them to use an architecture which can be optimized later. If you don't do that, you're just rolling the dice.
-
Their words
If every uh software engineer knew to watch out for false serial dependency chains, things where they were creating series of dependent operations that could not be optimized away or other sorts of architectural problems like that that cannot be easily fixed, then the world would look more like just wait and optimize the hotspot, right?
-
Their words
the performance of your software is generally determined by the longest serial dependency chain because it's something that cannot be parallelized.
-
Their words
If I look at the assembly language output from that compiler, I know exactly what the CPU is being asked to do. And it's not that hard to be able to learn to read assembly language so that you can see very quickly is the CPU being asked to do the things that I think it should be asked to do them.
-
Their words
I also see people attacking major product categories now with performance-based pitches. Things like File Pilot or the Blick video editor, like things like this that have been coming out lately where it's like, oh, really performant software to try to take on uh incumbents in a space and they've been getting traction.
-
Their words
It's just like we are massively underperforming and people don't believe it when you say 10x 100x but it's actually true and we've seen a lot of proof of it as you point out.
16 June
Nothing matches.
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.