List of blogs and sites

Following the line of my last post, here is a list of blogs and sites that are useful to know and consult:

• philcalcado.com
• www.preethikasireddy.com/blog
• increment.com
• 12factor.net
• www.reactivemanifesto.org
• principlesofchaos.org
• www.hyrumslaw.com
• docs.aws.amazon.com/wellarchitected/latest/framework
• github.com/testdouble/contributing-tests/wiki
• oauth.net
• www.oauth.com
• jsonapi.org
• drtools.site

List of talks

Inspired by my "list of books" posts, I decided to make a list of some of the most interesting talks that I've watched in the last few years. Here it is:

• Managing Unconscious Bias: excellent Facebook content designed to help us recognize our biases so we can reduce their negative effects in the workplace.
• Python Concurrency From the Ground Up: LIVE!: all live demo talk by David Beazley about threads, event loops and coroutines in Python. The most epic live session I've ever seen!
• The Many Meanings of Event-Driven Architecture: event-driven systems are not all equal. In this talk, Martin Fowler presents four patterns which tend to appear under the title of "event-driven" (event notification, event-based state transfer, event sourcing, and CQRS) as well as the architectural assumptions and implications of each one.
• Beyond PEP 8 -- Best Practices For Beautiful Intelligible Code: Raymond Hettinger is one of my favorite speakers. In this fantastic talk, he shows how looking at Python code beyond the PEP 8 rules can lead to a higher quality (and more Pythonic) code.
• 10 Things I Regret About Node.js: In this iconic presentation, the creator of Node.js, Ryan Dahl, comments on the technical decisions he currently considers flaws in Node.js and uses them as motivators to introduce the public to his new project: Deno.
• Applied Performance Theory: Kavya Joshi offers a great content on performance theory and its uses in real systems. Mandatory talk for those who want to carry out load tests properly.
• The History of Fire Escapes: Tanya Reilly looks at what can be learned from real world fire codes about expecting failure and designing for it. A deep reflection showing that investing in more resilient and "fireproof" software can be much more effective than just investing in response to incidents.