The Making of Lemmings, a Whirlwind of Security News, and even more you can't miss

LinkedIn announced the Next Wave list (top professionals under 35) for 2016 this year, for the first time including Software professionals! Check it out here, and make sure to look at the Software list.

Around the Web

Starting our roundup with a healthy dose of outrage, Kabletown, er, sorry... Comcast announced that they're expanding their price increase, er... 'usage cap trials' to basically every market they serve. Capcast, er, sorry, Comcast customers now have a cap of 1 TB total data transfer per month after which they pay an extortionate $10 per 50 GB of additional transfer. (AWS, known for having wildly overpriced bandwidth, charges half this, by the way, and even then, only for outgoing traffic.) If you're unhappy with this, perhaps switch providers--ohhh, wait.

In happier news, Coursera wrote a great post explaining how their code executable blocks feature works. This feature lets Coursera instructors "extend the Coursera platform with a development environment exposed as an embeddable code editor." Read the post to see why this is cool, but it is super cool!

The always fantastic Charity Majors has been working on a new product called Honeycomb which is totally not Another Log Aggregator. She explains the differences and what makes Honeycomb unique in a really awesome product announcement blog series discussing their "observability" framework. It's absolutely worth checking out.

If you haven't played Lemmings, you've missed out on a fantastic game. It's completely worth playing, and this great post explains how a tiny studio made such a standout masterpiece. There were sequels, remakes, and it totally influenced game design for decades to come.

In our security corner this week: Yahoo! was basically running tail -f /var/spool/mail | grep stuff | mailx nsa, Apple made another security mistake in iOS 10 that compromises the security of URLs in Private Browsing, thin clients continue to have laughably easy-to-break security, Facebook finally offers strong encryption on Facebook Messenger, and Bruce Schneier writes a fantastic post about how 'fixing users' will never be the way to security and offering his advice on what we should do instead.

On LinkedIn

We saw some fantastic Software Engineering posts on LinkedIn this week, including a post from LinkedIn member Andrea Goulet discussing the founding of her business, code maintenance, and being perceived as "non-technical."

Additionally, a great interview of Bryan Inagaki by Stephen Northcutt discusses what it's like to participate in the SANS NetWars tournament and definitely helped pique my interest in the tournament.

Finally, Rob Russo gives us an overview of how AppLovin builds scalable applications, providing an extremely concise and correct overview of how to scale and make sure that your apps are functioning well at scale.

Samsung today announced that they are 'adjusting production' of the Galaxy Note 7, after a recall failed to stop their phones from spontaneously exploding. Most people seem to agree this is a euphemism for suspending production, and that Samsung may need to do significant work to resume producing the handset.

This story drives home the point that you can't patch hardware. Software Engineers have some luxury in that we can just wait for a patch if we make a mistake, but what if we couldn't? How would software change if we only got one shot at shipping a working version and couldn't make up for it in patches? Write about it and make sure to include #SWE and #NoPatches in your post for a chance for it to be distributed to our members.

Follow me on LinkedIn or Twitter (@LefflerGreg) to keep up with my posts. If you have suggestions for things you want to read about, write about, or that I should know about, please leave a comment.

Share this post with your networks so that they can get up to speed on what matters in the Software Engineering world: