Learnings

<p>an important reminder of why trying to have an empathetic team is no excuse to not care about inclusion </p>

<p>Outcome Over Output </p>

<p>Best Python retrying library: </p>

<p>Common Issues Using Celery (And Other Task Queues) </p>

<p>RESTler is a stateful REST API fuzzing tool for automatically testing cloud services through their REST APIs and finding security and reliability bugs in these services. </p>

<p>Online editor to create and manipulate SVG paths </p>

<p>8 minutes tutorial with a good example of WASM + React </p>

<p>9 things that I've found improve development team velocity </p>

<p>React, Inline Functions, and Performance </p>

<p>5 Uses of Asterisks in Python </p>

<p>Navigating team friction </p>

<p>Detecting slow tests with pytest </p>

<p>The cost of a join and some benchmarks </p>

<p>Find your broken links, so users don't: </p>

<p>Learn from Apple’s art of tech explanation: </p>

<p>Help your team work together effectively by clarifying individual responsibilities and finding gaps that need to be filled: </p>

<p>10 tips to strengthen your Product Design and Product Management relationship: </p>

<p>Introduction to Linear Algebra for Applied Machine Learning with Python: </p>

<p>Detection of elements in viewport &amp; smooth scrolling with parallax </p>

<p>Being Glue</p>

<p>Collaborative git repository for awesome design tools (accessibility, animation, AR, color picking, handoff and much more) </p>

<p>“I would consider it a red flag if a team isn’t doing exploratory testing at all - even if their automated testing was excellent. Even the best automated testing is inherently scripted testing - and that alone is not good enough.” </p>

<p>How “Export to Excel” Almost Killed Our System </p>

<p>A nice guide on how and when to tweak Postgres work_mem configuration variable </p>