Changelog

Would you fire your top contributor — someone with a deep understanding of your product’s architecture and a ton of domain-specific knowledge? Jonathan Solórzano-Hamilton writes on the freeCodeCamp blog about this exact scenario... “You will never be able to understand any of what I’ve created. I am Albert F#@$ing Einstein and you are all monkeys scrabbling in the dirt.” He declared this in front of the product design team, developers, management, and pre-launch customers. One of our project sponsors had the temerity to ask when the problem crippling our product would be fixed. No one gets a pass on being a jerk. I personally subscribe to the "no asshole rule," and do my best to purge the assholes as soon as possible. The sooner the better, for everyone. Have you heard of the book on the subject? Here's why Robert Sutton wrote 'The No Asshole Rule'

All you ever wanted to know about Flexbox, explained visually. 👇 is just a sample of what you'll find when you follow the link.

Tigran Hakobyan, remote software engineer at Buffer, writes on the freeCodeCamp blog: Working remotely is very different from working in the office. I don’t think you fully grasp the difference until you actually start being remote. For someone like me who never worked in a remote environment, the beginning wasn’t smooth and it came with challenges. I can clearly remember my very first day at Buffer... Tigran also shares a pretty comprehensive breakdown of a typical workday.

Quincy Larson: Dozens of contributors worked on the new curriculum for more than a year. It features 6 new developer certifications - all of which are 100% free. This looks top notch. Great work to all involved!🥇

You can screenshot a single element?!! 😱 Select an element and press cmd-shift-p (ctrl-shift-p on Windows) to open the Command Menu then select Capture node screenshot. There are 11 more tips just like this. Some I'm sure you know. Others you likely don't.

Manuel Vila: We are using more and more command-line tools, and while many of them are really good, I think they could be even better if they were based on more modern foundations. Because our tools are based on ancient paradigms (*nix, Bash, etc.), it's difficult for them to be both customizable and easy to use. After working for a year trying to solve this problem, he came up with "resources", which he says: brings an object-oriented interface to the command-line tools, making them a lot more flexible, composable, and user-friendly. The curmudgeon in me immediately thought, "old dog ... new tricks", but Manuel has a reply ready: I am well aware that I am not going to change 50 years of old practices by myself. It has to be a collective effort. So I'm trying to communicate as much as I can to find the few people crazy enough to join the adventure. Are you "crazy enough" to go on the adventure with him? Click through to find out more.