Nice explanation of how graph search algorithms work. If you need to build some path finding feature this is for you.

A good reminder that "push it to the GPU and it'll be faster" isn't true. If you move a workload to the GPU you likely have to rethink quite a bit how it's done.

I like this article. Indeed, focus on building organisations and teams where it's easy to do the right thing bit hard to fail. This is much better than obsessing over mythical 10x engineers.

There are indeed fields where this matters a lot. It is far from being an easy problem to solve though.

We can expect this to be a game changer for the C++ ecosystem. A couple of examples are presented in this article.

Interesting comparison, indeed would a clock like this be useful?

It's indeed difficult to separate FUD from the real community issues around Matrix right now. We'll have to keep an eye on how things evolve.

Definitely this, as projects scale, keeping an eye on dependencies between teams is key to efficient allocation. This will happen by trying to eliminate said dependencies, reallocating between teams.

The Adaptive Model is a lesser known design pattern. Like any other pattern make sure you are in the right context to introduce it. Especially this one as it can get really verbose. This article shows a refactoring path for moving from imperative logic to adaptive model.

Since the movie became fashionable again, it might be interesting to go through this piece. The movie wasn't great, the article is a bit of a stretch... but at times it tells something about what's required to master a craft. It's a funny and short piece.

If you're behind on your updates, it's time to do it quickly.

What is premature optimization really? If you look at the full paper it might not be what you think. In any case we get back to: do the math and benchmark.

They both have their niches and it's welcome in my opinion. Now there are questions about the long term viability of Zig's ecosystem... the niche being smaller it's more at risk.

Nice move. It doesn't have to be about rewriting everything in Rust. Still there are some areas where we can benefit from the language and sandboxing.

Definitely a cool hardware hack. There are really many form factors and hardware options to explore for better XR experience.

And one more... it's clearly driven by an architecture pattern used by all vendors. They need to get their acts together to change this.

Since atomics are really a hard topic, this article is welcome. It does a good job explaining what memory ordering does. It helps to debunk some common misconceptions.

Friendly reminder that the term "server-side rendering" doesn't make sense. Also, you don't have to use React of the likes on the server side, it should be as simple as making string joins indeed.

I'd say this is a sane rant. Indeed, there's more progress to do, it will probably never stop. What could stop though is throwing crap at the people who quietly put effort into making our desktops more accessible.

I'd like to see the equivalent for Europe. Clearly in the US things aren't always great for Internet access. The latency is likely higher than you think, and the bandwidth lower.