Weekly development links #4
Discussion on the advantages of TCP vs UDP (and vice versa) has a history which is almost as long as the eternal Linux-vs-Windows debate. As I have long been a supporter of the point of view that both UDP and TCP have their own niches, here are my two cents on this subject.
In the past few months I've spent quite a bit of time with ASP.NET Core 1, and this week I've been taking a deep dive into Windows Server 2016 and Nano Server. One thing is clear: for developers, how we deploy and run applications is going to change quite substantially when all of this makes its way into production.
I'm not much of a software guy, so while I'm pleased with the results I expect people will say this is a little bit hacked together. I found some raspberry pi telepresence or baby monitor projects on the web, but they were all missing at least one piece of the puzzle. In particular I couldn't find a simple script/program for two way audio streaming, which really surprised me since video is so easy.
If you're one of 500 million people who use Dropbox, it’s just a folder on your computer desktop that lets you easily store files on the Internet, send them to others, and synchronize them across your laptop, phone, and tablet. You use this folder, then you forget it. And that’s by design. Peer behind that folder, however, and you’ll discover an epic feat of engineering. Dropbox runs atop a sweeping network of machines whose evolution epitomizes the forces that have transformed the heart of the Internet over the past decade. And today, this system entered a remarkable new stage of existence.
Markov chains, named after Andrey Markov, are mathematical systems that hop from one "state" (a situation or set of values) to another.
Being a productive developer is something you can learn through experience, books, or trial and error. But, one of the best ways to become a productive developer is to learn directly from a developer who is already productive. I interviewed some of the most productive engineers at Facebook in order to find an underlying structure for how these developers operated at peak productivity.
I recently jumped back into frontend development for the first time in months, and I was immediately struck by one thing: everything had changed.