I agree that’s what I took out of it as well. The builder perspective is learning to design and implement from first principles, which isn’t very practical acco

I agree that’s what I took out of it as well. The builder perspective is learning to design and implement from first principles, which isn’t very practical according to the author because most of the information will not be used in day to day programming. The perspective the author is arguing for is understanding the principles behind how systems under the hood impact day to day programming. An example: you don’t care about how transistors work, unless you want to understand rowhammer. One theory I heard is: it works because small transistors get their electricity leaked away to bigger transistors that are reading out memory millions of times. Another: you don’t care about creating a game in assembly (hello Rollercoaster Tycoon!), but you do want to be able to read assembly with regards to do compiler and/or performance analysis. I wonder whether people agree with my examples or disagree.