Learnings

<p>How to fix bugs that you can’t reproduce </p>

<p>Big Design Up Front is not always the enemy of good agile development </p>

<p>Tips to design &amp; write good design documentation, from the Dropbox team </p>

<p>Prefect: an Airflow alternative: </p>

<p>Why is it worth doing Story Kick-offs </p>

<p>BLUF: a strategy for effective communication </p>

<p>how to prepare a company for remote work in an emergency </p>

<p>a neat glossary for UX terms: </p>

<p>a thoughtful (and a bit controversial) reflection on the state of Agile Workflow </p>

<p>“In software, the greatest source of waste <em>is building the wrong thing</em>, period, not building the right thing slowly, not building the wrong thing slowly, just flat-out building things that add no value.” </p>

<p>how to maintain a pattern library inside Zeplin </p>

<p>A very insightful article on how designers deal with tools </p>

<p>a bunch of useful tips on how to process design feedback from stakeholders </p>

<p>why pair-designing might be great for our team </p>

<p>a quick way to relink local symbols to a shared library on Sketch: </p>

<p>the importance of a physical space to serve as spatial memory for a project </p>

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

<p>cool tips for handling design specs on Zeplin </p>

<p>Wireflows: a UX deliverable for workflows and apps </p>

<p>sketching on whiteboards and sticking post-its on walls can do a lot for a product team </p>