71–80 of 177 posts
> You probably won't pick a driver sitting on the edge of the frontier because you want some balance between speed and acceleration for super mario kart speedruns go with bowser/dk: https://www.speedrun.com/smk/runs/zp68nr8m That seemed to hold up for Mario Kart 8 too going with Bowser at the edge of their pareto frontier, https://www.speedrun.com/mk8 needing acceleration is a skill issue
On a tangent, I was a bit confused by the everyday examples given in this article. "We're often faced with similar trade-offs. You want a meal that's both cheap and delicious? A job that's both well-paid, easy, and fulfilling?" I really don't feel like "easy" is a dimension I wish to optimize for in a job. It almost feels opposite to what I've actually optimized for - since for me a fulfilling job usually means full…
This is a really important concept for developers. One aspect for developers that I see quite often is the assertion that "We can't have X without giving up more Y", most commonly "we can't have more security without giving up on user experience". With the Pareto idea in mind, we can see that that statement is true, if and only if you are in fact on the Pareto frontier of security and user experience already. However…
On a tangent, I was a bit confused by the everyday examples given in this article. "We're often faced with similar trade-offs. You want a meal that's both cheap and delicious? A job that's both well-paid, easy, and fulfilling?" I really don't feel like "easy" is a dimension I wish to optimize for in a job. It almost feels opposite to what I've actually optimized for - since for me a fulfilling job usually means full…
On a tangent, I was a bit confused by the everyday examples given in this article. "We're often faced with similar trade-offs. You want a meal that's both cheap and delicious? A job that's both well-paid, easy, and fulfilling?" I really don't feel like "easy" is a dimension I wish to optimize for in a job. It almost feels opposite to what I've actually optimized for - since for me a fulfilling job usually means full…
(And please note that I do not mean to imply that there are no challenges in manual labor or that software engineering is more important.)
On a tangent, I was a bit confused by the everyday examples given in this article. "We're often faced with similar trade-offs. You want a meal that's both cheap and delicious? A job that's both well-paid, easy, and fulfilling?" I really don't feel like "easy" is a dimension I wish to optimize for in a job. It almost feels opposite to what I've actually optimized for - since for me a fulfilling job usually means full…
This is a really important concept for developers. One aspect for developers that I see quite often is the assertion that "We can't have X without giving up more Y", most commonly "we can't have more security without giving up on user experience". With the Pareto idea in mind, we can see that that statement is true, if and only if you are in fact on the Pareto frontier of security and user experience already. However…
Excellent. This is some kind of 3D PowerPoint. How did he do that?
Author here. The source code is available at https://github.com/SuperMayo/mayerowitz.io . It’s called scrollytelling. For this particular project, I borrowed a lot from https://mlu-explain.github.io/ . For the 3D elements, I used Threejs and a custom vertex shader for the 3D plot.
I get that this form of presentation may be great for many people, but for my brain, it makes it extremely hard to engage with the content.