Follow us in building better services and stronger teams at scale.
Today I found something surprising - a piece of code in C# which awaited a new Task(...)
and which achieved its goal, but did the opposite of what I expected. Indeed, instead
of the task running to completion, it instead never completed. In this post I'll share
some interesting empirical observations about how this works and talk about how this
differs from asynchronous execution systems in other languages.
The Prusa XL is a high-end Core-XY 3D printer from Prusa Research, the technical specifications of which you can find on their product page. I was recently looking add another printer to my home lab, alongside my trusty Voron 2.4R2, and the Prusa XL was one of several printers I considered - it is also ultimately the one I chose to purchase based on its unique set of trade-offs.
The biggest challenge I faced making this decision was the lack of any deep technical reviews of the Prusa XL, so I'm going to try and close that gap here by sharing my thoughts and experiences through the lens of someone who has spent the last couple of years diving into the guts of what makes for a reliable 3D printer.
The tech world is filled with people who have strong views and are more than happy to share them. An unreasonable number of them are priviledged white males. Many of them see the world through the lens of their own personal experience and don't bother much with external perspectives. Far too many are eager to start a fight over their religion of choice (be that a language, a technology, a "thought leader" whose message they subscribe to, or a topic they have precious little familiarity with).
I'm many of those things, I'd really like to avoid being all of them. Let's talk perspective and trying to see the big picture. Let's talk about how to be wrong, and be okay with that.