Looks like we're stuck in the middle of the bridge. Also looks like the motivation to finish the transition isn't high.
Indeed a good way to reason about tests and the value they bring.
Another example of why pytest is really a nice test runner. I really miss it on projects which don't have it.
More signs of the current bubble being about to burst?
Another good set of advices. They're not all technical which is to be expected.
Ah I wise MarkNotes or KleverNotes would work like this. I wish we'd have a reusable component in KDE Frameworks too. This is quite some work of course, too bad this isn't FOSS.
This is just insane, claiming two opposite things to different demographic groups for political gains. And if you try to stop this kind of manipulative stunts they'd probably cry wolf about free speech...
Now this is an interesting paper. Neurosymbolic approaches are starting to go somewhere now. This is definitely helped by the NLP abilities of LLMs (which should be used only for that). The natural language to Prolog idea makes sense, now it needs to be more reliable. I'd be curious to know how many times the multiple-try path is exercised (the paper doesn't quite focus on that). More research is required obviously.
Cloudflare indeed needs to do better to accommodate RSS readers. They're not malicious bots and shouldn't be flagged as such.
Excellent introduction to sync engines and how they work. The concept is indeed coming from the gaming industry and we see it more in web applications nowadays due to the user demands for working offline and real time collaboration.
Wow, the atmosphere looks fairly toxic at Automattic right now. It felt like it was just about the trademark dispute but clearly the craziness is running much deeper. This is concerning for WordPress future I think.
This is an important trait to have for a developer. If you're content of things working without knowing why and how they work, you're looking for a world of pain later.
Definitely this. Our cognitive capacity is limited, we'd better not deplete it due to complexity before we even reach the core of the problem at hand.
Nice article showing the steps to port Rust code to run on deeply embedded systems. It highlights the difficulties and caveats of such a task.
It's actually unsurprising, all those tech and crypto bros have assets in jeopardy if some regulation is applied to their industry. No wonder they'd support the one with the most libertarian agenda after the current administration which did look into antitrust cases and increased regulation (even though marginally).
Want to put an end to the social media platforms weight on our lives? For once there's an individual solution which might work. This is a chance because as he rightfully points out individual solutions are generally too complicated to bring systemic change. Here this is actually doable.
It's tempting to use uv. It's probably fine on the developer workstation at this point. It looks a bit early to use it in production though, it's a bit young for that and carries questions regarding supply chain security still.
Nice graphic tricks when the hardware was harder to work with. It's amazing how much we could fit back then out of sheer motivation.
Our craft is based on shifting sands. This brings interesting philosophical questions, like why do it at all? I think the answer proposed in this short article is spot on. It can help bring new ideas on how to be in the world. This is more important than the code itself.
Definitely a funny hack. Not usable for compute workloads though.