Tech Insights

<p>Use the Rule of 100 to determine wether to represent discounts on a product price tag with percentages (20% off) or absolute values ($20 off) </p>

<p>High performance and SEO friendly lazy loader </p>

<p>hiring great people is not all it takes to build a great team. here are a few solid strategies: </p>

<p>the concept of “traveling through UI” and why we should always strive to make the user journey faster </p>

<p>Prototyping Forms and Inputs using Justinmind </p>

<p>Deep dive: How do React hooks really work? </p>

<p>RICE: Simple prioritization for product managers - </p>

<p>State of CSS 2019 </p>

<p>a lib that monkey patches React to notify you about avoidable re-renders.</p>

<p>The 4px Baseline Grid : How to use it and why is it important for UI design </p>

<p>Folder Structure in React Apps: </p>

<p>A list of articles about react-redux testing: </p>

<p>Best practices for unit testing with a React/Redux approach: </p>

<p>A repository with various templates and tips on writing high-quality documentation that people want to read </p>

<p>React component patterns: the best use practices to split the logic layer and the presentational layer: </p>

<p>Simple fixes for slow Django REST Framework serializers (not prefetch!): </p>

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

<p>Automating the boring stuff in Django using the check framework </p>

<p>good content about what metrics to look at when considering user behavior in a product company </p>

<p>Python Serialization Benchmark </p>

<p>A working guide of API design tips and trend evaluations </p>

<p>“The prudent debt example is deliberate because the team knows they are taking on a debt, and thus puts some thought as to whether the payoff for an earlier release is greater than the costs of paying it off. A team ignorant of design practices is taking on its reckless debt without even realizing how much hock it’s getting into.” </p>

<p>Copying and pasting with tmux 2.4+ on macOS </p>

<p>“Cruft has a quick impact, slowing down the very new features that are needed quickly. Teams who do this end up maxing out all their credit cards, but still delivering later than they would have done had they put the effort into higher internal quality.” </p>