Learnings

<p>Know thy enemy: How to prioritize and communicate risks—CRE life lessons: </p>

<p>Lessons Learned by reading Postmortems: </p>

<p>A dark launch sends a copy of real user-generated traffic to your new service, and discards the result from the new service before it's returned to the user. It helps to avoid regressions and test the new service under realistic load. </p>

<p>How Much Does It Cost To Deploy an NFT Project on Ethereum? </p>

<p>A Guide to Building, Testing, and Deploying your First DApp with Truffle, , Ganache, and React</p>

<p>websockets is a library for building WebSocket servers and clients in Python with a focus on correctness, simplicity, robustness, and performance </p>

<p>Trojan Source: Invisible Vulnerabilities </p>

<p>A program that determines wether a python package is well maintained </p>

<p>The Verica Open Incident Database (VOID) makes public software-related incident reports available to everyone, increasing understanding of software-based failures in order to make the internet a more resilient and safe place. </p>

<p>What wipes in Star Wars teach us about the brain and also interface design: </p>

<p>State Management: Separation of Concerns </p>

<p>A tool for scanning Python environments for known vulnerabilities: </p>

<p>One must be aware of putting their time into valuable things. However, valuable does not always mean a myopic focus on one thing </p>

<p>Trust models: </p>

<p>Async requests-like httplib for python: </p>

<p>Heroku buildpack to remove unwanted files from the slug post-build, enabling the removal of node_modules and assets after webpack bundles are produced: </p>

<p>WCAG : What you need to know about the future of accessibility standards </p>

<p>Advanced error handling with Apollo Link </p>

<p>How to make smarter design tradeoffs </p>

<p>Building a design system as a solo designer in a startup </p>

<p>"How smart and versatile should our function be? [..] A useful principle is to not add cleverness unless you are absolutely sure you’re going to need it. It can be tempting to write general “frameworks” for every bit of functionality you come across. Resist that urge. You won’t get any real work done—you’ll just be writing code that you never use" </p>

<p>"How difficult it is to find a good name for a function is a good indication of how clear a concept it is that you’re trying to wrap" </p>

<p>A Universal Way to Set Up a Harmonious Line Spacing </p>

<p>MTTR is a Misleading Metric—Now What? </p>