Hacker News Reader

Perhaps the more important practice is to establish visibility into which areas of your code are the performance bottlenecks. If you're developing in an environment where you're comfortable quickly profiling things with low friction, then it's much easier to know where to spend your time optimizing data structures and algorithms.

This is now one of my favorite technical talks. Very salient points!

I absolutely love his section on how calling some programmers lazy when all visible evidence shows otherwise is silly.

This is a pretty awesome talk. I wish he expanded on the "array of records" thing and how he implemented it.

Maybe an array of key-value pairs?