Straight from the uutils rewrite. This is interesting both for the class of bugs which made it (very system integration oriented, unsurprisingly) and the ones which didn't appear at all (anything to do with memory).
A bit of a stretched metaphor in here, but indeed being individually faster doesn't automatically make the team faster. Sometimes quite the contrary in fact.
A good illustration that you can beat classical algorithms by taking into account how modern CPUs are designed.
Want a primer on email routing? This is pretty much it.
It all changed so much! That's quite a journey for our field. Of course it's not over yet. At some point we'll be real engineers I guess. 😉
This is a good illustration of how flexible and expressive Lua can be. Gives ideas to make DSLs.
C++ too can have its own supply chain disasters with enough effort!
Another post which shows that the right technical job interviews are the ones creating a real conversation. It's the only way to have a chance to figure out what the candidate is made of.
This could be a piece full of nostalgia. There is a bit of nostalgia of course, but it's also a path to use what we got in a more valuable and humane way.
This part of the industry is struggling more and more (or more likely silently taking more risks to hide the struggle). It has no path to sustainability and it starts to show.
Indeed, the memory layout of your structs can matter. Be it Rust or not, but in the case of Rust the use of Option might give the wrong feel about the resulting layout.
More in depth look at the launch white paper and the issues covered in the PR. Not much survives scrutiny... there's nothing special with this model.
A reminder that path based APIs and security don't go well together to manage files.
Interesting piece which gives some perspective on the path which led to async/await. It seems to omit some pieces of the history to me but that's a minor issue. I like how it points that it indeed led to gradual improvements locally for developers writing their functions, but is overall leading to larger issues in the involved ecosystems.
A single CLI tool for any Git forge? This sounds appealing.
Another one on the commodification of travel, it exemplifies what real travel is.
Indeed, and it's going to get even crazier at some point. I guess somewhat soon but who knows...
Interesting insights, or how listening helps finding risk or making sure delegation will go well. It's indeed also a good illustration that story telling works often betterthan explaining abstract concepts.
Yes, I'm definitely bummed by this behavior as well. Best travel is when you take your time and enjoy the place, definitely not running around to take pictures for vanity reasons.
Architecture work is not only technical, you need processes to put the architecture of a project in place. That said, you can make things easier with standards to smooth the path toward the preferred types of architectures in your organisation.