This is early research of course but still the results are interesting. Once again, we're much easier to influence than we'd like.
This is an excellent and needed work of contextualization. Ten years after, looking back at how the Snowden Revelations impacted the internet and the work done by the IETF. It also shows there is plenty more to do...
Who would have thought there are so many ways to make paper airplanes?
Clearly the UI design matters quite a bit in term of how addictive all those social network systems are. The alternative proposed here is interesting, I wish it'd be more widely implemented.
Very interesting explorations of the early days of automation and computation. This shows another face of Babbage which is often ignored. It is a cruel demonstration on how his machine were first and foremost encroached on division of labor as inspired by plantations.
The fascinating world of micromice competitions. There's a lot of thinking leading to those really smart designs.
Indeed, the story of integrating C and C++ with Rust isn't a simple one right now. It might introduce larger attack surfaces. Some improvements are proposed in this paper.
Everything you always wanted to know but didn't dare asking about memory allocators. OK, maybe not "everything everything" but this gives a very good overview on how they work and the trade-offs they have to make.
Doesn't give the whole picture (memory isn't the only important parameter) but interesting results nonetheless. A few surprises in there, Java and C# do much better than one might assume for instance.
Nice list of patterns leveraging the Python type hints for richer and safer interfaces.
Definitely something I learned way to late. I wish I had started with such summaries and book notes earlier.
Very thorough overview on how registers are used when you get closer to the hardware. Very good resource to use as reference.
Interesting insights about the minutiae of the CTO role.
Looks like a smart and interesting little tool. I definitely needed something like it more than once.
Indeed, the times when we could pretend one was a superset of the other are long gone.
Updating database schema or interfaces between services should take time if you want to limit the downtime. The extra work involved might mean you should accept a little downtime instead. It probably should be on a case by case basis rather than a blanket policy.
Interesting list. Definitely to keep in mind when developing and deploying a web application.
Interesting take. Will it lead to paying more attention to performance in software? Will it be the rise of the specialized CPUs? Time will tell.
A good counterpoint to the "choose boring tech" which I tend to agree with. Sometimes you need to look into unusual tech and it's fine. Just have to do it rarely and responsibly. The context matters.
Interesting take... Is it really practical? Until which size is it viable? What are we loosing by aggregating? Also makes me wonder about alert fatigue... It clearly raises extra questions.