# 2023 August

# 08/22

# Talks seen

https://www.deconstructconf.com/2019/dan-abramov-the-wet-codebase

  • Somewhat useful
  • Main takeaway #1: Don't abstract too early. Feel free to inline code (un-abstract), and then re-abstract later if needed.
  • Main takeaway #2: Best practices might be summarized, so really think about the underlying reason for the best practice before applying it.

https://www.deconstructconf.com/2019/vaidehi-joshi-setting-up-to-fail

  • Goes over some types of distributed system failures
  • Useful if you are a new SDE in the industry, working on distributed systems. Else, not.
  • Main takeaway: Distributed systems can fail in various ways and if you work with distributed systems, it may be useful to learn this (+ ways to address these, which the talk doesn't cover)

# 08/24

# Talks seen

https://www.deconstructconf.com/2019/hillary-anderson-the-odyssey-lessons-learned-from-learning

  • Didn't find it too useful
  • About learning, working in the data science field
  • Main takeaway: Teach others to learn better. Community helps.

https://www.deconstructconf.com/2019/karla-burnett-2-factor-4-humans

  • Useful and highly recommended if you are new to security & interested to learn.
  • Main takeaway: Too many to list.

# 08/25

# Talks seen

https://www.deconstructconf.com/2019/allison-kaptur-clock-skew-and-you

  • Worth a watch if you work with distributed systems.
  • SSL certs are affected by clock skew. This was solved by shipping a key with chrome, maintaining time servers in google's DC to know accurate times, and prompting users to fix their client clock, which surfaced that most ssl issues are due to time.
  • How NTP works (layers of computers from high accuracy to lower). SNTP differs in that it is P2P synchronization (? not explained in talk, independent research)
  • Shows how to calculate clock skew, but only if skew is symmetric in request & response.