Tech Insights

<p>The best engineering interview question I’ve ever gotten: </p>

<p>Programming and Cognitive Load, with a Django REST Framework example: </p>

<p>A smarter Dockerfile linter that helps you build best practice Docker images. </p>

<p>Understanding Layout Algorithms: The mental model shift that makes CSS more intuitive </p>

<p>Future Javascript: Records and Tuples </p>

<p>Best practices to containerize web applications with Docker Node.js</p>

<p>Miscellaneous features of javascript: Currying </p>

<p>Passing callbacks down with React Hooks </p>

<p>Protocol: the keystone of type hints </p>

<p>User Stories are ill-suited for expressing requirements </p>

<p>“Medium’s audience mostly favors articles between 1,100 words and 2,000 words. The data is similar across platforms. Orbit Media estimates 1,500 words makes for a perfect blog post.” </p>

<p>We should avoid "snacking" and "preening" (Preening is doing low-impact high-visibility work. - from "Staff Engineer: Leadership beyond the management track)</p>

<p>Open collection of customized MUI components </p>

<p>Idiomatic Redux: Designing the Redux Toolkit Listener Middleware: </p>

<p>Django Generic Functionality without Generic Relations: </p>

<p>Which Kinds of Tests Should I Write? </p>

<p>Does my React app render too often? </p>

<p>How many re-renders is too many? </p>

Local Azure Storage Emulation with Azurite and Azure Functions — A Dummies Guide

<p>If you're pair programming, you can add <code>Co-authored-by: Author Name &lt;author@&gt;</code> for all developers in the pairing session to the commit body and they'll be recognized as co-commiters. Works for Github and Gitlab </p>

<p>How to manage toil as you scale </p>

<p>In some cases you can avoid circular import if you import the module instead of the member </p>

Type-safe API mocking with Mock Service Worker and TypeScript

<p>The Saff Squeeze: </p>