Thank you Casey, so generous of you to post this.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks for sharing this! It's kinda crazy how rare education like this is. How do you recommend people actively practice optimizing code that they've recognized as slow? I imagine you could just watch for it in your own code, but you could also seek it out (e.g. open source).
-
As I showed in the video, the best practice to learn is to always estimate how fast a computer _should_ do something, and then compare that ballpark estimate to how fast it _is_ doing that thing. That's how you know whether you should be optimizing.
End of conversation
New conversation -
-
-
Thanks! This is exactly what I needed at exactly this moment! How did you know?!
-
Like the NSA, I run a giant datacenter that records all your calls, emails, and metadata. I know what you want before you do.
End of conversation
New conversation -
-
-
Good talk:D!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
how long did you practice before you could write backwards that fast/readable?
-
That's a joke, right?
- Show replies
New conversation -
-
-
Enjoyed the talk. Very much in spirit with what I've been preaching for the last years. Computers are fast if you don't give them unnecessary work. The trick you used for precomputing in the hit testing was neat! Maybe I'll get to use that someday.
-
This is a longstanding practice in ray intersection testing. Because the rays tested tend to vastly outnumber the primitives against which they are tested (at least at some part of the hierarchy), shifting computation away from the rays to the primitives tends to benefit.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.