Learnings

<p>Library for safety first markdown rendering: </p>

<p>Use git --ours or --theirs to easily discard or accept pulled/rebased/merged/cherry-picked changes on files: </p>

<p>12 factor for cli apps </p>

<p>Which Podcasts Should Web Designers And Developers Be Listening To? </p>

<p>how to get notifications right for a better UX </p>

<p>GitHub will launch two cool new features: changes suggestion on pull request reviews and workflows (called GitHub Actions) </p>

<p>good study about factors that might influence the conversion of a sign-up flow </p>

<p>How to write git commit messages #messages</p>

<p>Using Google Optimize to setup a A/B test: </p>

<p>designing organic notifications </p>

<p>Document notable changes between each release (or version) of the project. </p>

<p>You might not need jQuery. At the very least, make sure you know what jQuery is doing for you, and what it's not. </p>

<p>The role of grid systems in component-based front-end builds </p>

<p>how to create a front-end style guide </p>

<p>Why rewrite everything from scratch is bad. </p>

<p>why we should be using atomic web design </p>

<p>Raising the culture of using and maintaining a design system in a team. </p>

<p>Using All Caps on UI: Good or Bad? </p>

<p>IPython 7.0 released with asyncio integration </p>

<p>nice post about how Product Managers should look at more conversations and balance them out with metrics </p>

<p>An awesome collection of spinners </p>

<p>Great guide about statistical significance in A/B tests </p>

<p>common assumptions about coding practices that research states that they can help but need some pinches of salt. Approaching very different areas, from microservices to agile </p>

<p>VSCode team has launched an extension to access pull requests directly from the editor </p>