Indeed, it's hard. You need to put in the work but it's hard to predict where the real value will come from.
A good reminder that the JavaScript Date API is very error prone.
It's a very important threshold to cross. Let's hope this momentum stays long enough.
And it's not necessarily a problem. It all depends on the goal and context of the API you're building.
This is a lovely idea I think. Good way to pay homage to lost ones.
Excellent news on the PNG standard front!
Dealing with temporaries is always complicated it seems, whatever the language.
Very interesting bug hunt prompted by some mysterious character in some strings and leading all the way to PDF viewers.
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.