Learnings

<p>How do I assign the right number of Test Analysts to a scrum team? </p>

<p>How many developers does it take to test a product? </p>

<p>How to build a design system if you’re the only designer in a startup </p>

<p>A (Mostly) Complete Guide to React Rendering Behavior: </p>

<p>Interfaces, Mixins and Building Powerful Custom Data Structures in Python: </p>

<p>A tool to detect and prevent secrets from getting checked in </p>

<p>VSCode extension to test APIs: </p>

<p>Python News: What's New From July 2021? </p>

<p>How can you find time to design? </p>

<p>AHA (Avoid Hasty Abstractions) Programming </p>

<p>Pytest - Factories as fixtures </p>

<p>If You Want To Transform IT, Start With Finance </p>

<p>Discontinuing Google Sign-In JavaScript Platform Library for web </p>

<p>Celery in production: Three more years of fixing bugs </p>

<p>Using Django Check Constraints to Prevent the Storage of The Empty String </p>

<p>The World of CSS Transforms. "Unless you eat CSS for breakfast, I bet you'll learn something neat!" </p>

<p><em>Reflections on 10,000 Hours of Programming:</em> </p>

<p>Visualizing a codebase: </p>

<p>django-recaptcha now requires mocking for unit testing: </p>

<p>How to know what to test </p>

<p>Testing Implementation Details </p>

<p>Nice tool for understanding those confusing regexes </p>

<p>Heuristics for Effective Software Development </p>

<p>The XY problem is a communication problem encountered in help desk and similar situations in which the person asking for help obscures the real issue, X, because instead of asking directly about issue X, they ask how to solve a secondary issue, Y, which they believe will allow them to resolve issue X. However, resolving issue <em>Y</em> often does not resolve issue <em>X</em>, or is a poor way to resolve it, and the obscuring of the real issue and the introduction of the potentially strange secondary issue can lead to the person trying to help having unnecessary difficulties in communication and/or offering poor solutions. </p>