If it's too complicated to find a good name, use a comment indeed. As simple as that.

Interesting article about expert generalists (also called "paint drip people" by Kent Beck). This is definitely a skill to foster in teams. The article is long enough that I'm not in agreement with everything in it. That being said there's a lot of food for thought here.

Better not trust ZIP files you receive...

OK... This is weird and funny. I definitely like the idea of an actor reading this important RFC aloud.

Nice pattern to workaround limitations of the Rust trait system preventing blanket implementations.

Looks like an interesting vector editor.

It's indeed another possible point of view about caching.

So, you derailed and the joy is long gone in your team. This second part shows a possible way forward. Although it's probably not widely applicable (YMMV), the proposed end goal is what matters... If you stop fussing over labels but focus on what matters you're likely on the right track.

Hear, hear! If you go through rituals without understanding the values and principles... It's not Agile anymore so stop pretending. Another certification isn't going to save you at this point.

There are indeed other options beyond the model with "one enum with all the errors".

Both approaches have their pros and cons of course. Whatever you pick, it has to start with a care for quality shared within the team.

I think this is indeed something still easily overlooked. You can deal with this kind of intertwined lifetime issues using shared_ptr.

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.