Learnings

<p>4 key lessons I’ve learned about OKRs </p>

<p>Prefetch: A modern data workflow platform </p>

<p>filprofiler, a memory profiler for data batch processing applications: </p>

<p>How to build effective product tours </p>

<p>Visualizing Class-Based Views: </p>

<p>Must read if you need to know if multiple tables are empty in SQL. Small story: Once I had count check taking hours to run just to assert if the table was empty, this post explains how to fix it: </p>

<p>Figma: Prototyping and Developer Handoff </p>

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

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

<p>The big picture (strategy and company goals) needs to be crystal-clear before we start prioritizing and estimating features. </p>

<p>How to write a project proposal that will get other stakeholders on board with your idea: </p>

<p>How to plan, write, and deliver technical documentation that works: </p>

<p>2020 Stack Overflow Developer Survey: #overview</p>

<p>some techniques to prioritize decisions with a team </p>

<p>When Perfect Is (and Isn’t) the Enemy of Good </p>

<p>Joblib: running Python functions as pipeline jobs: </p>

<p>Why Percentiles Don’t Work the Way You Think: </p>

<p>Why feature-based roadmaps fail in rapidly changing markets </p>

<p>A handy list of questions to be applied in user-feedback surveys, from IDF </p>

<p>How to build solid hypotheses to guide our design process: </p>

<p>Simple rules that will help you design forms users will like to complete </p>

<p>A framework for Engineering Career Ladders: </p>

<p>Latency in Asynchronous Python: </p>

<p>Discussion on the various ways to wait for results in asyncio: </p>