I wouldn't say I'm great, but the best ones I know have been excellent at understanding code just by reading it. Lots of stuff gets abstracted out from docs, of

I wouldn't say I'm great, but the best ones I know have been excellent at understanding code just by reading it. Lots of stuff gets abstracted out from docs, often at the drivers level. It's not just about knowing the framework, but where it breaks, where it shines, how it's meant to be used. Which part is being held together with duct tape? How is it processing a certain graphics type?