Learnings

<p>Index Selectivity: A Key to High Performance SQL </p>

<p>How to be a -10x Engineer </p>

<p>Ban 1+N in Django: </p>

<p>"Clean" Code, Horrible Performance </p>

<p>The truth about CSS selector performance </p>

<p>Vue Virtual Scroll List </p>

<p>In Postgres, "empty updates" have the same cost per row as any other update. Even if the values won't change after the <code>UPDATE</code>, the operation will still have the same performance: </p>

<p>Cacheable S3 signed URLs: </p>

<p>Profiling site speed with the Chrome DevTools Performance tab </p>

<p>How Does Dan Abramov Optimize After Be Complained about Website Speed? </p>

<p>CSS box-shadow Can Slow Down Scrolling: </p>

<p>You Are Doing SQL Pagination Wrong </p>

<p>Where’s your bottleneck? CPU time vs wallclock time </p>

<p>Use Partial Responses To Reduce Request Sizes </p>

<p>You don't need that CORS request: </p>

<p>django-raw-sugar: Turns your raw SQL into a QuerySet. </p>

<p>How Does Django's StreamingHttpResponse Work, Exactly? </p>

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

<p>You can run EXPLAIN on a SQL query directly from a Django queryset: </p>

<p>Beware of : PerformanceTiming.domInteractive</p>

<p>A dark launch sends a copy of real user-generated traffic to your new service, and discards the result from the new service before it's returned to the user. It helps to avoid regressions and test the new service under realistic load. </p>

<p>Heroku buildpack to remove unwanted files from the slug post-build, enabling the removal of node_modules and assets after webpack bundles are produced: </p>

<p>Context Manager to launch exceptions when Django makes unexpected queries to ensure explicit control over DB overhead: </p>

<p>How not to structure your database-backed web applications: a study of performance bugs in the wild - </p>