Learnings

<p>Preventing Data Loss When Using Messaging: </p>

<p>Reading Your Own Writes: </p>

<p>Team Topologies at Atlassian: How four fundamental topologies influence a DevOps transformation. </p>

<p>Code Colocation is King: keep the code that changes together close together </p>

<p>PostgreSQL-based Task Queue for Python: </p>

<p>10 Unknown Security Pitfalls for Python: </p>

<p>Inclusive Design </p>

<p>Recruiting User Research Participants by Email </p>

<p>TMUX cheat sheet for who wants to try it out </p>

<p>Reliable Microservices Data Exchange With the Outbox Pattern: </p>

<p>Prints the SQL for the named migration </p>

<p>Hacking Your Head: Managing Information Overload, by Jo Pearce </p>

<p>Measuring product design impact — KPIs, NPS, etc. </p>

<p>How and Why We Do UX Research </p>

<p>A collection of product frameworks to help you create better products </p>

<p>DRF serializer to_representation is not called if field value is None </p>

<p>Post-mortem on Roblox 73-hour outage: </p>

<p>Stop using 40px touch targets </p>

<p>SRE and the Practice of Practice </p>

<p>An extremely casual code review of MetaMask’s crypto: </p>

<p>Dashboard design: 6 things every UX designer should know </p>

<p>Conhecendo o dual track: foco na entrega de valor (Workflow similar ao que usamos atualmente no AL e no PP) </p>

<p>Design system: LEGO kits syndrome </p>

<p><em>The stages of growing a UX Research team</em> </p>