Issue #309

tl;dr: Typical white-boarding interviews are suboptimal. A better method is to have "the candidate read existing code and talk about what it does and how it works." Reading code is: (1) Probably 95% of what a developer does in their job. (2) Way more efficient than writing. (3) Puts the candidates at ease compared to writing code. The author shows us how to put this is into practice. 

tl;dr: Ask yourself why you need documentation e.g. making better decisions across the org, helping people get the right information, making onboarding more self-service. "If we’re deciding whether to write something, we should ask whether writing it will help us with one of those objectives." Paulo suggests pointing your team towards the "why" and also provides tips for maintaining the practice.

tl;dr: "Programming in Go, is the most in-demand skill; the cybersecurity talent shortage continues to intensify; and Silicon Valley companies continue to offer the highest salaries, even to their remote workers." And more.

tl;dr: "CSS tips and tricks you won’t see in most of the tutorials," such as creating the typing effect with no JS, using the drop-shadow filter function, smooth scrolling with one line of CSS and no JS. And more.