Learnings

<p>a thoughtful argument in the endless “should designers code” discussion </p>

<p>Webpack build has a --watch flag when you want to build your project but also keep watching for new changes.</p>

<p>Markov Chains explained visually: </p>

<p>The 3-click rule and the user hunt for “information scent” </p>

<p>Configuring CSS Modules and Sass in your create-react-app project </p>

<p>Difference between shallow, mount and render of Enzyme </p>

<p>The Biggest Problem with (Most) User Onboarding Experiences </p>

<p>Experience rot: the danger of bloating your product with needless features </p>

<p>Online Style Guide Generator [Styleguides] @laisvarejao @aline</p>

<p>Project Include has many recommendations and processes for solving the diversity problem in tech companies: </p>

<p>You should try this lib in order to keep your Rest API safe </p>

<p>tips for building a great product dashboard </p>

<p>Website Style Guide Resources </p>

<p>Designing notifications for apps </p>

<p>Is the Lean Startup Dead? </p>

<p>Now that's really serverless! Serving with 99.82% cache hit ratio with Cloudflare Workers and Azure Functions: </p>

<p>How relaxing constraints on tech, cost, knowledge, and time can improve your product vision: </p>

<p>Startup Playbook </p>

<p>Cool tutorial/overview on what's Docker and how to use it/best practices: </p>

<p>Quantitative User-Research Methodologies: An Overview </p>

<p>a few ways to deal with inline editing </p>

<p>a good explanation of the "jobs to be done" framework </p>

<p>An infinite library of patterns for designers #knitting</p>

<p>Meetings get a bad rap. People hate them. But they can be productive.</p>