Tech Insights

<p>Pipenv by @kennethreitz checkout at </p>

<p>Always have a quick and friendly feedback feature on your product. Besides all the metrics you can get from it, it helps users to give you a second chance by telling you what didn't work for them.</p>

<p>Really good blog post telling the experience of re-writing an app in React: #.sl07j8rbq</p>

<p>Continuous Integration Certification </p>

<p>Don't hurry your team! </p>

<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>