Tech Insights

<p>Query Expressions are amazing </p>

<p>How to add a heroku remote #creating-a-heroku-remote</p>

<p>Never write to a model field or call save() directly </p>

<p>A SASS Style Guide: </p>

<p>Semantic vs. presentational SASS classes: </p>

<p>Nice strftime reference: </p>

<p>Use a custom loaddata management command to load data from stdin to production Django projects. Useful for loading data into Heroku: </p>

<p>Interesting rant about google platforms </p>

<p>Be careful when comparing <code>Decimal</code> and <code>float</code>: <code>Decimal('3.0') == 3.0</code> but <code>Decimal('3.2') != 3.2</code>.</p>

<p>The price of GPL </p>

<p>Parse and automatically capitalize human names with nameparser: </p>

<p>"Project delays: why good software estimates are impossible" </p>

<p>If you're using <code>CELERY_ALWAYS_EAGER = True</code>, probably you'll also want <code>CELERY_EAGER_PROPAGATES_EXCEPTIONS = True</code> to find bugs</p>

<p>Great article about employee retention: </p>

<p>"Write down any question you hear from customers more than twice. That'll feed your content marketing". From: </p>

<p>Great advice from top startups in 2016: </p>

<p>Django bugfix release: 1.10.5 - update your projects! </p>

<p>This is how you mock components when testing react with <code>jest</code>:</p> <p><code>// in your test file jest.mock('../path/to/component/to/Component.js');</code></p> <p>Create a <code>__mocks__</code> folder in the same directory of the component you want to test and a file with the same name of the component inside it:</p> <p><code>// __mocks__/Component.js import React from 'react'; export default function mock() { return (&lt;span&gt;Component mock&lt;/span&gt;); }</code></p>

<p>React tip: the solution to “how do I avoid passing props many levels down” can be surprisingly simple: </p>

<p>simple automated solution for dealing with trolls and toxic comments on your comments session: everyone has to rate before commenting and helps stoping hate speech</p>

<p>Want to exclude a directory from <code>git diff</code>? Use <code>git diff old new --name-only | grep -v '/tests/' | xargs git diff old new --</code>. Replace old/new with your branches. From: </p>

<p>On Django, validate ZIP codes, states, social security numbers and more with django-localflavor: </p>

<p>If there is an error with webpack build it will not stop your CI from deploying. Always use --bail </p>

<p>Subscribe to NN/g newsletter for top articles about UX backed by real-world data </p>