A very important and unfortunately underestimated factor for a sane and welcoming culture.
Interesting dive into the implementation of a render graph system for a 3D engine.
Interesting set of challenges indeed. I think Rust is a bit at a crossroad now. The next few years will be crucial, either they will lead to further adoption or it will stagnate and slowly disappear.
Since I regularly Figma at customer's I really hope this will boost adoption on Penpot. A good open alternative you can even self-host.
This is a welcome list of options to clarify what we're talking about when we talk about "self-hosting". It's not a single concept but a range of approaches.
As if we still need people to be convinced... apparently we do. So just in case we need a well built argument about it, this post does it.
Interesting point of view. Indeed what might look like magic skills can simply be about having gathered more information. That thus depends on the organization.
Nice explanation on how QR codes are made. The most gritty details are left out so it's easy to follow.
Please this, I'd love to see more bikes everywhere.
Lots of truth in there. Indeed the proposed "practices" when they get in just kill the promises of things like Scrum.
Some good points in this list although I'm not in full agreement with everything (especially the one about the lack of usefulness for TDD). The importance and the impacts of the tooling is often underestimated indeed. The last two random opinions about mocking and overtesting are very much true as well.
Very interesting piece. Goes in length about the UNIX history and the evolution of POSIX. It also highlight its limitations and where the design needs to evolve.
If you want to get to the bottom of a problem and of why an accident happen, people need psychological safety. This is indeed necessary if you want them to share truthfully why the accident happened in the first place. Otherwise fear will drive the conversation and hide important facts.
A good reminder about the impacts of Goodhart's law, or even simply of measuring the wrong thing. I like the conclusion overall: it's fine to measure things but that shouldn't be the center of the decision taking and conversations need to take a larger role into it.
In our industry, we obsess too much over individual performance. In turn it means that the systems we put in place within or around our teams get neglected... this is a problem because it is what has the biggest impact on quality and performance.
Good points to keep in mind regarding team size. It's a delicate balance to strike in an organization.
Definitely a good list of places I'd love to visit and get lost into.
This has some interesting promises in terms of performance using Python. Looks a bit like a CUDA for Python... to be seen how it fares in practice.
Indeed, React is a bit too much of the default choice right now while clearly it shouldn't be that way. Let's hope it'll change and something else with more merit will take its place.
Python is making progress regarding portable binaries and it is welcome.