akdas

31 ms·

1. 181.▲
   by akdas 8y ago

   For context, I agree with you that understanding compilers is very important to a deep understanding of the tools used by programmers. Knowing how languages are implemented sheds light into why certain design decisions are made and why cert
2. 182.▲
   by akdas 8y ago

   I learned Vim after switching to Dvorak, so the Dvorak positions of hjkl are what I'm used to. I don't have to think about the key I pressed.
3. 183.▲
   by akdas 8y ago

   I use Vim with Dvorak. No remapping required. The keys are just in different places than on Qwerty.
4. 184.▲
   by akdas 8y ago

   Know you're talking about. That alone will make the talk more natural, as you'll be able to adapt to your audience due to having knowledge outside of just your research. This was the biggest change between the presentations I had
5. 185.▲
   by akdas 8y ago

   Java streams are great. Having to go from collections to streams (`.stream()`) and back (`.collect(...)`) is annoying, but understandable from a compositional point of view. For fun, you can further reduce the size of the code above (and IM
6. 186.▲
   by akdas 8y ago

   I work on Primitive, a novel way of visualizing and interacting with code in VR: https://primitive.io/ Half of the technical work is built around compiler technology (and more generally the implementation of programming lan
7. 187.▲
   by akdas 9y ago

   You're absolutely right. Normally, the surroundings provide a form of area lighting that my image doesn't have.
8. 188.▲
   by akdas 9y ago

   I use the Phong reflection model ( https://en.wikipedia.org/wiki/Phong_reflection_model ), which gives materials a distinct plasticky look. Peter's materials are either purely diffuse, purely reflective or glass-lik
9. 189.▲
   by akdas 9y ago

   Related to the ray tracing materials, I taught a two-day crash course on writing a ray tracer. The materials are available online: https://avik-das.github.io/build-your-own-raytracer/