And yet another set of open source models. This is really democratizing quickly.

Truly open source models are pouring in. This is showing more transparency and I hope it will lead to better uses even though some of the concerns will stay true.

Excellent opinion piece. Sure, "A.I." is a tool, but who is wielding that tool currently? Whom needs is it designed to fulfill? This is currently very much of a problem. The comparison with McKinsey although surprising is an interesting thought.

Also I appreciate the clarification on the Luddites movement... they were not anti-technology.

Very interesting to see that move to owned hardware... turns out that not only the invoice is smaller in their case but the performances are much better as well.

Clearly a bit US centric but interesting trends nonetheless. We might see some of that reaching Europe (for good and for bad) fairly quickly. At least regarding hybrid work, flexible offices and more asynchronous communication, I've seen it globally spread already.

It's a bit a "yet another article" about estimates. Still there are a few good points in there, they're harder to apply than it sounds though.

Nice overview of WebGPU. Also does a decent job laying out the history of graphics APIs. With WebGPU bound to be more widespread and available outside of the browsers things will get very interesting.

Nice to see there are still people out there keeping in mind the "let's not put all our eggs in the same basket". This is especially important for systems with such vendor lock-in as GitHub. I'm a bit less convinced about replacing Git itself for now.

Looks like a promising linting tool for Python. Feature packed and faster than most other options out there.

Very nice explanation about TCP_NODELAY and its implications.

Nice resource to get started with this important and efficient practice.

Indeed, without deciding to put everything in the public domain, the face of the web would have been very different.

I must resist to redesign my blog I guess... In any case, this is a very nice style for content.

Looks like nice projects. After all these years I'm still amazed at what people manage to achieve in their spare time when they get together to solve a problem.

There are really many initiatives to make C and C++ safer lately. I wonder which one will see adoption and what will make its way to the standards.

Interesting approach. I did quite some of that but without really putting it together like this. It's a nice way to explain it.

Nice overview of what it takes to increase your uptime. It can get expensive quickly. This is also a good reminder that it's not only about software, it's a lot about people and administrative constraints as well.

What the title say. This is especially important for product development. This is not emphasized enough in the article I think but the "aligned autonomy" section is a crucial part of this. I very often see in teams either alignment or autonomy, it's rarer to see teams with both.

Interesting results. This gives a couple of insights in terms or adoption, perception of problems by people on C++ projects and tooling. It's definitely worth skimming through.

This is currently a real zoo. I knew about a few of them but not that many. I guess it will slowly converge toward a few major options.