This is a good praise for the work of maintainers. They're fighting off entropy and this should be well regarded.
You assumed you could deserialise in a zero copy fashion? Are you really sure about that? Think twice.
Unsurprisingly, this is mostly not related to the use of Rust. The design choices are what male uv so fast.
Looks like a neat option for quick party games.
Interesting tool and I like the underlying approach. I wish we'd have good equivalent tools for other ecosystems.
I think this is a good pick at a core skill for senior developers. Indeed removing ambiguity for the rest of the team is an important factor.
Interesting tool. Indeed very often people send PDFs with useless redaction in them. Better check first.
A good explainer on what metastable failures are and how to try to mitigate them.
Indeed I wish our profession would have a strong and binding set of ethics like doctors or lawyers. That wouldn't prevent all problems, but that'd tame some of the issues of our time.
Indeed, people getting into lean processes tend to obsess over "eliminating waste". Sure there might be some waste to clean up but it's pretty much useless if you don't focus on the flow of work.
Pipelines are very widespread nowadays, still I don't see them used much. Having a few refactoring ideas under our belt to replace loops with such pipelines might help.
Where are acceptance tests coming from? They're generally the result of a conversation.
It's not the only factor leading to troublesome architectures of course. Still, if state and thus data is wrongly handled, you're indeed on the wrong track.
There are just too many of those cameras deployed. The fact that they are badly secured are compounding the negative effects.
Interesting historical work. It indeed went through a fast paced evolution cycle.
Martin Fowler obviously wrote a lot on the topic. This is a nice guide pointing to some of the most interesting resources on his blog around the agil topic.
Another explanation for the rule of zero in C++. We should definitely stick to it.
Always hated this notarization with a passion when I had to target Macs... One reason being that it felt fairly useless, and it's confirmed: it is pretty much useless.
An oldie now but still the best way to create a passphrase.
The definition of legacy code is ambiguous enough. We generally mean "bad code" (the wrong definition to me...). What about seeing things differently and trying to leave a great legacy behind us?