Notes

I use Got Your Back to backup my Gmail emails every night.: I stopped using GYB because the credentials it uses stop working after 7 days for regular Gmail accounts. I switched to OfflineIMAP instead. Here are some helpful commands: # Initial setup. ./bin/gyb/gyb \ --email [email protected] \ --local-folder /srv/dev-disk-by-uuid-28fd4901-c675-430d-be16-e1ffddc50727/Backups/GYB-GMail-Backup/[email protected] \ --action create-project # Quick way to test if everything is setup as expected. ./bin/gyb/gyb \ --email [email protected] \ --local-folder /srv/dev-disk-by-uuid-28fd4901-c675-430d-be16-e1ffddc50727/Backups/GYB-GMail-Backup/[email protected] \ --action estimate # Backup. Omit the last term to backup everything. # The last three parameters are optional to speed things up or make them run in less-memory environments. /home/pi/bin/gyb/gyb \ --email [email protected] \ --local-folder /srv/dev-disk-by-uuid-28fd4901-c675-430d-be16-e1ffddc50727/Backups/GYB-GMail-Backup/[email protected] \ --action backup \ --search "newer_than:7d" \ --memory-limit 100 \ --batch-size 4 Other tools that I checked but didn’t use: ...

Intentionality - really important. Awareness = paying attention to your surrounding as well. (I guess the default is to have a monologue with yourself about yourself.)

Here is my attempt to design a system for a tiny URL service.

I should practice all the system design questions from that PDF. That includes going through the material once, presenting it to the camera, analyzing the recordings and revising the content after a few days. Should quickly do all of them. The questions shouldn’t be too hard. TBD ETA and I should strive to finish be then. Next step is to do mock interviews. Aim to do both system design and behavioral.

MD5 hashes and UUIDs are 128 bits. So, if you encode them using hexadecimals, each hex character will encode 4 bits of information, so resultant “string” will be 128/4=32 character/bytes long. If you store UUIDs as string, you need 4 additional characters for the hyphens. If you store them in binary format, you just need 128/8 = 16 bytes because each byte will encode 8 bits of information.

Architects should question axioms from the past - the software world changes fast and some of those axioms may no longer be true. Hopefully, the book will give examples. In the past, I used to worry about not knowing non-AWS (for example, Kubernetes) or older technologies deeply enough. That’s actually okay. I don’t have anything more because I’ve dropped the book for now.

Until end of April, I won’t use my phone in the following situations: Restaurants, shops, malls, hikes or other external activities. (Only exception is when I am expecting a phone call from my parents.) Meal time. In bed. (Get alarm clock from parents and use that instead. Leave phone outside the bedroom, if possible.)

See this Also, if you want to print some part of your file, make sure that the starting page number is odd, otherwise you’ll get wrong results.

The following seem to be good: https://faxzero.com/ https://www.gotfreefax.com/

Traefik through Docker Compose seems to be a much cleaner way than manually installing and configuring Nginx, like I used to do earlier. traefik.yaml: entryPoints: web: address: ":80" http: redirections: entryPoint: to: websecure websecure: address: ":443" providers: docker: {} certificatesResolvers: myresolver: acme: email: [email protected] storage: /data/letsencrypt.json httpChallenge: entryPoint: web And docker-compose should contain something like the following: services: traefik: image: traefik:v2.5 # TODO: try with "latest" instead of "2.5". restart: unless-stopped ports: - "80:80" - "443:443" volumes: - "./traefik.yaml:/etc/traefik/traefik.yaml" - "./traefik/data:/data" - "/var/run/docker.sock:/var/run/docker.sock" some-web-service-that-needs-a-reverse-proxy: # ... labels: - "traefik.http.routers.photoprism.rule=Host(`example.com`)" - "traefik.http.routers.photoprism.tls=true" - "traefik.http.routers.photoprism.tls.certresolver=myresolver"