This is a difference which needs to be reminded. Using precise language obviously helps.

Nice new tool to investigate code generated by macros in Rust. Indeed you can quickly add lots of lines to the compiled code without even realizing, in large code bases it's worth keeping in check.

If your team is solely in "pushing tickets out" mode, there's indeed a problem. Teams needs more agency and care for the output to actually strive long term.

More details one how the new C++ reflection features can be used. This is a really nice feat here to parse a JSON at compile time to make an object.

Nice exploration which shows the many levers one can use to impact Rust compilation times. They all have their own tradeoffs of course, so don't use this just for the sake of reducing time.

Good followup to a similar piece from someone else about React. Frameworks with a short half-life are not worth the hassle to learn, focus on more fundamental skills instead.

The whole Scrum training and certification industry has a problem... and it's been going on for a long time.

Good advice. Since I got to review quite a few... I'd like to see them more like that. The worst part is when one also fails to point his accomplishments during the interview. I ask specific questions about this and most time get nothing meaningful in return.

A bit of a forgotten approach I think. A good way to quickly gauge projects, show the amount of work and spot the dependencies.

You like weird bugs involving shell implementations, syscalls and filesystems? Somehow I do, this was an interesting one.

I like this kind of oddities in languages. This is nice to see such a list for Rust at a single place.

This piece is a bit too much written as Rust zealotry for my taste. That being said, there's in my opinion an interesting core truth hidden in there: for now it seems to better foster "expert generalists" when investing in it. Now it might be just for now and might stop later... time will tell.

Yes, tests can follow patterns as well... and antipatterns too. It's good to name those antipatterns, let's avoid them shall we?

Interesting framework to reason about lock-ins. It's not only about depending on a vendor, there are other factors to keep in mind. Now obviously I'd see the risks around cloud hosting in particular in a different way than the author... but I guess we're biased differently there.

A bit old perhaps, but shows quite well the various options to pass a function around in C++.

This is a model which seems to work for donation campaigns for FOSS projects. I wonder how much this scales though... if everyone does that, is there a point where users will be fed up with it?

uv really opens the door to nice features for Python. Now with a standardized PEP to help the configuration it's getting even better.

Nice! At last a Makefile linter. It has some interesting features, I especially like the automated .PHONY target management.

The situation around OpenSSL and its fork is rather confusing... And there's no indication this would improve.

Nice explanation of how graph search algorithms work. If you need to build some path finding feature this is for you.