#[0] is there a video of your discussion with Casey Muratori about clean code killing performance?
Discussion
Was there such a thing or am I hallucinating?
He kicked the whole discussion off with a youtube video that was highly critical of Clean Code.
https://www.youtube.com/watch?v=tD5NrevFtbU&t=11s
Other people wanted me to respond and that led to the github discussion.
>From: fiatjaf at 03/20/23 21:54:25 on wss://relay.nostriches.org
>---------------
>Was there such a thing or am I hallucinating?
Can also be audio. The important thing is that I can't read.
Oh, #[0] could read that if it was a written discussion! If only we had a system to pay sats to make some articles more attractive for him to pick than others...
Would you like me to create a video/audio where I read the whole thing aloud? It's not very long.
>From: fiatjaf at 03/20/23 21:54:47 on wss://relay.nostriches.org
>---------------
>Can also be audio. The important thing is that I can't read.
So far it's all been conducted on github: https://github.com/unclebob/cmuratori-discussion/blob/main/cleancodeqa.md
There are no current plans for a video; but you never know about things like that.
>From: fiatjaf at 03/20/23 21:54:13 on wss://relay.nostriches.org
>---------------
>#[3] is there a video of your discussion with Casey Muratori about clean code killing performance?
I’ve now watched Casey’s video and skimmed the discussion. The video was about a CPU-bound program. Most of the software I’ve worked on has been I/O-bound. I’m not sure I would have noticed a difference had I adopted anti-clean-code principles.
Yeah, that's Casey's main point. He works in the game industry where nanoseconds count for a lot. He wrote a gaming framework that I think is pretty popular. So his focus was on deep CPU bound issues that most of us seldom encounter.
>From: (43ddb32...) at 03/21/23 10:15:54 on wss://relay.nostrplebs.com
>---------------
>I’ve now watched Casey’s video and skimmed the discussion. The video was about a CPU-bound program. Most of the software I’ve worked on has been I/O-bound. I’m not sure I would have noticed a difference had I adopted anti-clean-code principles.