I am in the process of preparing a video class on Core Bluetooth (the native Apple framework).
I thought that I knew it all pretty well, but I found plenty of places that I needed to recalibrate, as I reviewed my materials.
I am now a great deal more confident in my grasp of the technology; thanks to my class.
I do a lot of writing, cast as a "teaching" exercise; even though no one cares. Doing this helps me to understand the material much more comprehensively.
When I teach, I then have a Responsibility. It is even more important to know the material than if I am developing a shipping application.
Speaking of "shipping"...
I write every line of code as "ship quality" code; even if I never have any intentions of shipping it (like test harnesses). That also helps me to make sure that I know what I'm doing. I heavily document my code, because explaining the code is like a built-in "self-peer-review." It helps me to see the code through fresh eyes.
I also write about my personal processes and approach to engineering, as that helps me to focus and make sure that I am speaking from a position of knowledge and experience.
I thought that I knew it all pretty well, but I found plenty of places that I needed to recalibrate, as I reviewed my materials.
I am now a great deal more confident in my grasp of the technology; thanks to my class.
I do a lot of writing, cast as a "teaching" exercise; even though no one cares. Doing this helps me to understand the material much more comprehensively.
When I teach, I then have a Responsibility. It is even more important to know the material than if I am developing a shipping application.
Speaking of "shipping"...
I write every line of code as "ship quality" code; even if I never have any intentions of shipping it (like test harnesses). That also helps me to make sure that I know what I'm doing. I heavily document my code, because explaining the code is like a built-in "self-peer-review." It helps me to see the code through fresh eyes.
I also write about my personal processes and approach to engineering, as that helps me to focus and make sure that I am speaking from a position of knowledge and experience.
I don't claim expertise I don't have, but I am constantly trying stuff I don't know how to do (I write about that here: https://medium.com/chrismarshallny/thats-not-what-ships-are-...). That's how I learn new stuff.
"The most erroneous stories are those we think we know best -and therefore never scrutinize or question." -Stephen Jay Gould