Learnings

<p>“The most common mistake a Product Manager can make for the long term success of a product is to let the metric define the product versus letting the user needs define the product and the product define the metric.” </p>

<p>Accessibility checklist from Webflow </p>

<p>falls "mainly in the planes" </p>

<p>The Future of CSS: CSS Toggles </p>

<p>Data means nothing if you don't know about usefulness </p>

<p>Notes on debugging: </p>

<p>How to run Python in the browser </p>

<p>The Elephant in the Architecture </p>

<p>PEP 673 – Self Type </p>

<p>What is Progressive Delivery All About? </p>

<p>How to increase the UX maturity of Scrum teams </p>

<p>A primer on product management for engineers </p>

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

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

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

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

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

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

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

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

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

<p>Protocol: the keystone of type hints </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>“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>