Every Monday we will round up some of the last week's top posts, comments, and tweets. If you have any feedback, please leave a comment. ❤️
Sébastien Castiel provided the week's top post, where he lays out a number of tips for writing modern Javscript code. He first describes the value of using a linter, then makes a few recommendations along with rules suggestions. He also touches on the value of functional programming before offering a few closing tips. Will widespread adoption of a linter solve the tabs v. spaces debate?
Creating a plan for your team and project
These are two great articles that can be read in conjunction, both of which involve making good high-level decisions. Barry's post centers around the technical considerations in building a clean architecture, whereas James focuses on management principles for establishing a long-term and short-term framework for making progress as a team of software developers.
Fun, or not
Carl Hembrough kicked off an amazing discussion about imposter syndrome, dozens of community members chimed in to offer advice and encouragement. It's a great read that we can all truly identify with:
Thanks for sharing this, especially the advice. Comparing yourself only to yourself is so useful, it can seem like you're not making any progress at all if you're only focused on (the public image of) others. Reminding yourself of the progress you've made is encouraging to the future progress you can still make.
Who's at fault for Wannacry?
One of the most spirited conversations in recent memory concerned "who" was at fault for WannaCry. Mortoray outlined a case against Microsoft, while others came to the company's defense in the comments section. This was truly a fascinating conversation from a number of thoughtful and passionate security researchers.
This has been a conversation in many cybersec circles. A lot blame poor patching and a disregard for updates. I'm more inclined to blame un-patched machines and a slowness to update as well. A machine would have had to be two months behind on patches to be impacted (in regards to the SMB vuln specifically).
Blame an industry for running a 16 year old OS with support that ended 3 years ago. Still, an interesting perspective.
K. provided an awesome experience report for React Native. As React gains prominence and popularity within the web development community, we're beginning to see more and more programmers experiment with developing for mobile. React Native provides a good on-ramp and framework, and K. describes some potential pitfalls while providing a number of great tips.
Vicky Lai provided a quick overview for iterating over objects and arrays, using a breakfast spread for her set of examples. Even experienced developers can get tripped up when grabbing object properties, and this post provides a number of snippets to highlight some common mistakes.
That's it for our weekly wrapup! Keep an eye on Dev.to this week for daily content and discussions...and if you miss anything, we'll be sure to recap it next Monday!