Nice trick for numbers formatting as strings in Python.

A bit dated perhaps, and yet most of the lessons in here are still valid. If performance and parallelism matter, you better keep an eye on how the cache is used.

An honest attempt at "vibe coding"... but once again the conclusion is "when it grows to non-trivial size, I'm glad my experience allowed me to finish the thing myself".

For studying it makes sense. But don't shun other's work away only because of trust or ego issues.

Good reminder that refactoring isn't necessarily the end of a cycle. It can also be before you add a feature.

This is indeed an excellent way to understand all the roles and the work behind creating a game.

Nice approach, especially useful if you need to split work to distribute it to threads.

Somehow not surprising... There's an area where it works OK. That said, I think we don't have the right UX to exploit it safely and productively. The right practices still need to be found. This isn't helped by all the hype and crazy announcements.

There are options indeed. Some of them can be maybe surprising. It of course depends the type of game you're making.

Another trick in Rust to avoid unwrap() calls. The let-else option is indeed particularly elegant.

Apparently this needs pointing out but there's more than async/await out there. Sometimes what you want is a simple event loop. Here illustrated in the Rust ecosystem.

Friendly reminder that in C++ that case evolved quite a bit all the way to C++23. Please use the more recent constructs in new code. This definitely leads to better patterns.

Unicode in source code can come with unwanted consequences. Tooling might be required.

Yes... definitely is too complex. This standard seriously needs a pass of simplification, I'm not at all convinced profiles would be enough to help for cases like this.

Unsurprisingly it works OK when it's about finding syntax errors you made or about low stakes mechanical work you need to repeat. The leash has to be very short.

Looks like a good list of pointers to understand languages and compilers... More reading ahead!

This remains the best explanation of why we should have more use of auto in C++ code.

I wonder how much the focus on Python biased that study... Still, maybe we've been wrong at so much emphasis on math skills for computer science and computer engineering curricula.

A good in-depth article about pair programming. Shows well the pros and cons.

Of course, we'd like more to go away... But that's already something.