Learnings

<p>Is always good to have some docker-compose samples, here are some: </p>

<p>Why we have a research plan at Nubank: </p>

<p>How Spotify organises work in Figma to improve collaboration </p>

<p>Is it worth it to run VACUUM on a table that only receives INSERTs? </p>

<p>Avoiding the new-manager syndrome in design </p>

<p>Great tips on how to deal with mental exhaustion </p>

<p>A complete post: Automating safe, hands-off deployments </p>

<p>Common mistakes with React Testing Library </p>

<p>Software Engineering is different from Programming </p>

<p>Always good to remember: use <code>git diff -w</code> to ignore whitespace. Very useful for finding bad edits on commits that should only affect indentation! #Documentation/git-diff.txt--w</p>

<p>How to use micro-interactions </p>

<p>Too many objects: Reducing memory overhead from Python instances </p>

<p>Some UI trends for 2020 </p>

<p>Useful simple and small tips for developers: </p>

<p>Create UIs for prototyping your machine learning model, compatible with Jupyter Notebooks: </p>

<p>Why did a fix of two lines of code take two days to complete? </p>

<p>Things I Wish I’d Known About CSS: awesome straightforward list of CSS gotchas </p>

<p>There's no one right way to test your code: comparing the multiple testing styles </p>

<p>Deploys at Slack </p>

<p>12 Signs You're Working in a Feature Factory </p>

<p>The path to technical leadership: how to go from developer to team leader </p>

<p><em>Don’t lead by example</em> :eyes: </p>

<p>You can find bugs in your machine learning pipeline by checking how each feature interferes to the error of the model using XAI methods: </p>

<p>a statement on why done is better than perfect with a way to work with constraints to force less-than-optimal deliveries </p>