↓ Skip to main content

Yearly review

Trigger
#

Every year, either at the beginning or end of the year.

Duration
#

A few hours spread over the course of a few days.

Steps
#

  • Review year according to various facets
  • Plan the next year according to the same facets

Notes
#

  • I use a mind map software to do my yearly review and plan.

References
#









Learning - 2021

  • A/B testing
  • Continuous experimentation
  • Kubernetes
  • Helm
  • GCP
    • Kubernetes Engine
    • BigQuery
    • Dataflow
    • Kubeflow
    • Airflow/Composer
    • VPC/Network/Firewall/Cloud armor
    • Cloud profiling
  • Go
  • GRPC
  • Terraform
  • Prometheus
    • Alerts
    • Recording rules
  • Grafana
  • Datadog
  • Kafka
  • Load balancing
    • GRPC
    • Kafka
  • Lens (GUI for Kubernetes)

Book rating

In this article I define a 1-5 rating scale for books in order to be consistent across my evaluations. Given that rating books is somewhat subjective, introducing some amount of standardization on how I rate them should help with managing my reading.

Format of presentation:

Score (from 1 to 5) Representative emoji

  • Satisfaction
  • Words expressing the level of satisfaction
  • Strength of recommendation

1 🤮

  • unsatisfactory
  • very bad, horrible, boring, repetitive, disagreeable to read, waste of time, can’t force myself to read
  • strongly not recommended

2 ☹️

  • unsatisfactory
  • bad
  • not recommended

3 😐

  • satisfactory
  • neutral
  • might want to read

4 ☺️

  • satisfactory
  • good
  • recommended

5 😍

  • satisfactory
  • very good, great, amazing, exciting, intriguing, fascinating, full of new knowledge, can’t stop reading
  • strongly recommended

References
#