Learnings

<p>Strong Opinions Loosely Held Might be the Worst Idea in Tech: </p>

<p>Add context to sections of the code that were not triggered by the user (e.g., requests) but have impact on them by taking advantage of the Sentry SDK scope context #capturing-the-user</p>

<p>Write tests. Not too many. Mostly integration. </p>

<p>About using stopPropagation "this solution is roughly equivalent to fixing a leaky shower by turning off the water to the bathroom": </p>

<p>Be aware of Javascript numeric precision issue when using integers as ids -&gt; <code>Boolean((2^53 + 1) === 2^53)</code> is equal to <code>true</code>: </p>

<p>the Krav Maga of UI design </p>

<p>Accessible color generator </p>

<p>a beginner-friendly explanation of the HSB color system </p>

<p>Indicators, Validations, and Notifications: Pick the Correct Communication Option </p>

<p>Validate GitHub Webhook Signatures: </p>

<p>What about business logic in Django projects: </p>

<p>A Complete UI cheat sheet for Buttons </p>

<p>Django Mock Queries, a library for mocking Django queryset functions in memory for testing: </p>

<p>Mozilla's file sending service with end-to-end cryptography. </p>

<p>Why reselect is useful to increase the performance of a React Redux app </p>

<p>Painting on a Distributed Canvas: An Advanced Guide to Celery Workflows </p>

<p>This post comments the insight: software systems need to be livable. Can a system be too clean? Is it possible to focus so much on cleanliness that no one can practically work in the system? </p>

<p>state-based immutability library </p>

<p>setting up Digitalocean Monitoring alerts </p>

<p>open source awards for react projects </p>

<p>The dot problem on emails: how to scam a Gmail user </p>

<p>binary releases of VS Code without MS branding/telemetry/licensing </p>

<p>A few things to keep in mind when dockerizing your app </p>

<p>High-Performing Teams Need Psychological Safety. Here’s How to Create It: </p>