Strategic Doc Reading
Context:
Ever since I read this Post I have been wanting to put that technique to good use.
With a bit of self-reflection, I believe I am the perfect candidate to test it because:
- That technique seemed like the typical one that doesn’t work for regular people
- I am pretty proud of my will power, and this would put it to a test
- I tend to forget stuff that I learnt months ago, and it frustrates me a lot
So… here is my current list (and the reading time needed for each topic):
- AWS VPC
- How it works - 12 mins
- VPC Peering - 2 mins
- AWS RDS
- Best Practices - 23 mins for MySQL and PostgreSQL
- Common DBA Tasks - 15 mins
- Advanced Aurora Auditing - 7 mins
- AWS EKS - 4 mins
- Security best practices - 6 mins
- IAM and ServiceAccounts - 2 mins
- OIDC provider - 2 mins
- Create IAM role and policy - 4 mins
- Associate an IAM role to a service account - 5 mins
- AWS App Mesh - 7 mins
- Best practices - 9 mins
- K8S
- Components - 9 mins
- API - 3 mins
- Architecture
- Nodes - 21 mins
- Control plane <-> node comms - 6 mins
- Controllers - 9 mins
- Cloud controller manager - 6 mins
- Well Known labels, annotations and taints - 8 mins
I continue adding details as I progress, but mostly these are the premises for this system to work (in order of importance):
- Do it regularly (starting with once a week, 1.5hrs.)
- Read the same docs again and again
- Prepare the next reading session in advance
- Balance between having too many docs to read and reading relevant docs. Expect constant corrections to the list because of this.
I also added some automation to the formula:
I put together this tiny application in Rust to get all docs together in one or several EPUBs, to be able to read them on an ebook reader. It requires Calibre, though
Written on March 20, 2021