Learnings

<p>12 Signs You're Working in a Feature Factory </p>

<p>The path to technical leadership: how to go from developer to team leader </p>

<p><em>Don’t lead by example</em> :eyes: </p>

<p>You can find bugs in your machine learning pipeline by checking how each feature interferes to the error of the model using XAI methods: </p>

<p>a statement on why done is better than perfect with a way to work with constraints to force less-than-optimal deliveries </p>

<p>A curated list of awesome test automation frameworks, tools, libraries, and software for different programming languages. </p>

<p>Work with yarn/npm packages locally for package development purposes, without publishing those packages to the remote registry. </p>

<p>A terminology guide to make our interfaces more consistent. </p>

<p>UI cheat-sheet for buttons </p>

<p>The best products &amp; websites for UI/UX designers.</p>

<p>Forgiveness as a design principle </p>

<p>Quickly improve code readability with Proximity Refactorings: "Functions that are changed together should be moved closer together" </p>

<p>Interesting comparison of JavaScript bundlers </p>

<p>Algorithms Behind Modern Storage Systems: </p>

<p>5 arguments to make managers care about technical debt: </p>

<p>Metrics, tracing, and logging and how they fit together? </p>

<p>Convince managers to address Tech Debt with Enclosure Diagrams: </p>

<p>If you mock, are you even testing? </p>

<p>How to apply friction in UI design to prevent user errors. </p>

<p>Eight tips to relieve those Postgres headaches: </p>

<p>The process of mastering a skill: </p>

<p>Case study about Notion performance </p>

<p>Pickle’s nine flaws: </p>

<p>Workshop - How to identify failures and then find solutions (design, workshop, strategy)</p>