Bad actors will go to great length to try to compromise your supply chain.
Se might have dodged a bullet here... Until next time. Thanks to the coalition of countries which opposed this bill.
Clearly that's interesting progress around this kind of display. This should make it easier to create devices using them going forward.
Or how a problem is represented matters a lot. Going for a constraint solver might be what you want sometimes.
A few ideas to dig deeper into for better multi threaded throughput.
And a bunch of tool to use with it... But you can indeed do a lot with just SSH. This post gives a few good ideas.
Very fun an impressive experiment of making a Wayland compositor rendering in the terminal with surprising refinements. Now it feels totally useless too of course.
I think this effect is a usability nightmare. That said it's interesting to see which CSS and SVG tricks can be used to simulate it. This opens the door to other effects.
It's indeed surprising that this compromised npm account didn't lead to more damage. It's a good reminder that you better regularly audit what happens in your ecosystem.
OK, this is an interesting way for the Darwin Award to branch. Some of the 2025 nominees are indeed funny. Now I wonder which ones will win the award!
Nice and to the point little guide on how to evaluate source of information.
Want to scare yourself with what might happen when you completely let go of your infrastructure? Here is an aggregator for that.
This is nice to see the energy still bubbling in the traditional web. It's still there, next to the big mall pushed by search engines. You just need to know where to look and it's not that hard.
C++26 really looks like a step in the right direction in term of safety. Undefined behaviours are too often neglected in that conversation.
Maybe time to change habits on table naming? I'm still on the fence myself but there are interesting arguments there.
Very nice article on the Wikipedia success. Or why being boring and the ultimate process pettiness became the crucial part of the formula. This community really developed a fascinating culture which so far resists to mounting political pressure... But will the editors morale hold?
Sometimes, it's indeed better to not pull an extra dependency.
Need a refresher on how to write a parser? This is a good one. Also gives a few ideas of Rust libraries you can use to make the task easier.
Indeed, carefully reading larger chunks of code and looking for the historical context around it can go a long way in finding bugs.
This is indeed one of the core questions on you "agile" project management. If the feedback loops are very long, you're in for trouble.