By dotCore
via fgiesen.wordpress.com
Submitted: Feb 06 2013 / 17:06
And welcome back to my impromptu optimization series. Today, we won’t see a single line of code, nor a profiler screenshot. That’s because our next subject is the triangle rasterizer, and we better brush up on our triangle facts before we dive into that. A lot of it is going to involve barycentric coordinates, hence the name. Be warned, this post is a lot drier than the previous ones, and it doesn’t even have a big pay-off at the end. It’s a pure, uncut info-dump. The purpose is to collect all this material in one place so I can refer back to it later as necessary.
-
The Tale of writing Good Code …
-
Improving Collaboration of Testers and Developers in Agile Teams
-
Why Don’t Software Developers Use Static Analysis Tools to Find Bugs?
-
The Last Responsible Moment
-
Understanding The LightSwitch HTML Client Visual Collection
-
Android to Windows Phone 8: Working with Key-Value Pairs
Add your comment
