Learnings

<p>Services Don’t Have to Be Eight-9s Reliable </p>

<p>10 Usability Heuristics Applied to Complex Applications. </p>

<p>Improve Serialization Performance in Django Rest Framework </p>

<p>Alexandrian Patterns - A solution to a problem in a context:</p>

<p>Organizational culture that is high-trust and emphasizes information flow is predictive of software delivery performance and organizational performance in technology: </p>

<p>Heuristics That Almost Always Work: </p>

<p>The Factorio Mindset: </p>

<p>Django’s Field Choices Don’t Constrain Your Data </p>

<p>How to build software that’s ready for the handoff: </p>

<p>Figma Tokens - Figma plugin to create, use and manage design tokens, either inside figma itself, or to export to a github source of truth. </p>

<p>If one is seeing a lot of Accidental Difficulty caused by boiler-plate code or hand-written translations to and from tools and interfaces, something in the system is likely Simply Simplistic. Simply Simplistic models and services and interfaces are too simple, failing to capture the Essential Difficulty, and thus force the Essential Difficulty to be duplicated by each user, increasing the Accidental Difficulty with each duplication. Sometimes you can extract this Accidental Difficulty into a library or helper Once And Only Once. Sometimes you cannot. If you cannot, your language tool may be Simply Simplistic itself, subject to the Missing Feature Smell. </p>

<p>Simplistic protocols and models and language features can end up becoming <em>complexity multipliers</em> because the complexity is duplicated by each and every <em>user</em> of the model or protocol. They are also effort multipliers. Fortunately, one can sometimes solve this problem by wrapping or refactoring the protocol or model or language feature within a library to utilize it, thus capturing the Essential Complexity into the library and thus creating the feature/language/model that should have existed in the first place. </p>

<p>12 templates and checklists to get you started with usability testing. </p>

<p>Encourage emoji: Rather than cluttering up discussion threads with short messages such as “Got it” or “I agree,” encourage team members to use reaction emoji to get their point across. This will keep conversations streamlined and minimize the amount of scrolling that readers need to do. </p>

<p>Short explanation of the issues faced when trying to create a PostgreSQL index using the date() function and how to resolve it. </p>

<p>Detach components, just like you detach instances with this simple plugin. </p>

<p>Find all Instances of a Component used in your file. </p>

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

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

<p><em>Software Architecture Monday with Mark Richards</em> is a free bi-weekly software architecture lesson containing a short video about some aspect of software architecture. These lessons contain tips, techniques, and advice to help you in your journey from developer to architect. </p>

<p>A free, open-source app to quickly generate beautiful <em>screenshots</em>. Apply backgrounds, shadows, add rounded corners and more </p>

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

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

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