Thank you, Joseph! :)
I have a cool clickable version on my website (great for bookmarking) —
I assumed truth-seeking behaviour when I wrote this, as those are the people who’d take out the time to read this.
My biggest fear with the Dunning Kruger effect, or why I’d like to evaluate my knowledge correctly, is to stop being dumb. (People falling for the DK effect are unaware of their incompetence)
Hey Mirek, thanks!
I disagree on your distinction between manual and automated testing. What I meant here was, once I know what I’m testing and for what reason, I’d always try and automate it away.
Once the brain has figured out a way to test things reliably, I want the machine to take over and do it for me every time I deploy — instead of me doing it manually.
Yep, I agree with the figuring out the right level of abstraction being a problem.
I think being explicit about current understanding is step 1 to generating new insights. Without the base of knowledge, how do you figure out if what you discovered is “new” or something you implicitly knew already?
Hey Ben! Thank you :)
Usually, the end goal is to be comfortable using Python to do what you wanted to get done in the first place. I think of it as a tool — to help you get better at building stuff.
In that sense, the best way is to build something.