Obvious advice perhaps, but so easily forgotten somehow...
One of the most important projects out there in my opinion. Happy birthday!
What a bad idea. From the information at hand I don't see how this can go well.
Looks like an interesting tool to manage user environment when they join a project.
This advice makes sense. People performance fluctuate you need to know where the extremes are before hiring them. Easier said than done though.
Clearly very much inspired by the science peer review system. Having experienced it, indeed I wish more business decisions would be made that way.
Very good points. Picking a particular language is likely not the right approach. Trying to apply the main principles of functional programming on the other hand is more likely to bear fruits.
Long post but worth the read in my opinion. It lays out good reasons for reducing the dominance of React and move beyond it. There are good reasons to do so, and they're piling up with the time passing.
Experience the gruesome work of being an operating system. Now show some respect!
A bit C++ and game engine focused (to be expected since this is were this kind of techniques originate from), bit very good explanation on how to have packed layouts for your objects and reduce pressure on memory allocation for data intensive tasks.
Good thinking about abstraction levels on top of a platform. It's very much focused on the Web platform but applies more generally. Good food for thought on the libraries vs framework debate, why escape hatches matter and why you want a layered architecture.
Illustrated with Rust in this case, but definitely one of the big advantages of having type systems. Adding constraints (even runtime ones) to your types make it harder for bugs to hide.
Excellent points. Don't be fooled by alluring architecture changes. Always keep the complexity in check and favor tuning what's already here or changing your use patterns to meet the performance you need.
Good reminder on how the W3C works and what it evaluates. If Web Environment Integrity would become a "standard" it'd likely be more of a "de facto" thing because a major player shoved it everyone's throat.
A good reminder on how the "five why" are just a starting pont. For proper investigation and risk management you need to go deeper.
Not as detailed as I would like on the proposed solution. A good starting point for inspiration though. Should help with geospatial and fleet management problems.
Nicely explain how to secure your webhooks step by step.
Beware of the problems coroutines might bring. Some are "obvious" and related to concurrency in general, but some are running deep in their design in C++.
Very good advice. Don't waste time believing false business claims and trying to replicate them. Easier said than done though, most people don't have the privilege of insiders knowledge.
Doesn't go much in depth, but this is a nice resource with interesting references to follow to dig deeper and learn mDNS.