Due to NetworkManager you forgot how to setup an interface and the networking stack manually? Here is a good summary of the important steps.
Some powerful bullies want to make the life of editors impossible. Looks like the foundation has the right tools in store to protect those contributors.
This is an interesting way to frame the problem. We can't rely too much on LLMs for computer science problems without loosing important skills and hindering learning. This is to be kept in mind.
Surprising idea... I guess I'll mull this one over and maybe try. This is not a small change of habit though.
Alright, this piece is full of vitriol... And I like it. The CES has clearly become a mirror of the absurdities our industry is going through. The vision proposed by a good chunk of the companies is not appealing and lazy.
Of course it would be less of a problem if explainability was better with such models. It's not the case though, so it means they can spew very subtle propaganda. This is bound to become even more of a political power tool.
This is clearly pointing in the direction of UX challenges around LLM uses. For some tasks the user's critical thinking must be fostered otherwise bad decisions will ensue.
A good reminder that you should always bring several perspectives when teaching something. This a a simple framework which can be used widely in our field.
This is indeed something easy to get wrong. Also this misconception is very widespread, so it's good to debunk it.
Interesting comparison. Ada doesn't fare as good as I'd have expected as soon as pointers are in the mix... but there is a twist, you can go a very long way without pointers in Ada.
Nice and tiny estimation approach. I can see projects where this could work.
A good example of what can be done when you have a rich type system.
What do you want? Speed or safety? Ultimately you'll have to choose one.
A couple of interesting ideas. This fluid focus concept definitely require communication around it when applied.
Again it's definitely not useful for everyone... it might even be dangerous for learning.
Another reminder that you don't want reference to primitive types everywhere in Rust code. There's actually ways to handle this properly. This post gives a couple of simple guidelines to apply.
It shows unexpected results in its measurements. It also highlights the importance of proper settings for your database system.
Be wary of the unproven claims that using LLMs necessarily leads to productivity gains. The impacts might be negative.
Nice exploration of JIT based techniques in Python.
Indeed there is a tension between both approaches in package ecosystems.