chompychop

"The people that made the most money in the gold rush were selling shovels, not digging gold".

The formal definition in the link makes this precise. Yes, 100 sets which are pairwise disjoint (which makes any pairwise intersection empty) would make a sunflower. Your second example is not a sunflower, because the definition requires that if you take the intersection of any two sets from those 100, the resulting set should be the same. So if you pairwise take those sets with unique elements, you get the empty set as intersection, but if you pairwise take two sets with shared elements, you get a set of the shared elements as intersection. The pairwise intersection should always be the same for it to be a sunflower. And yes, a collection of two sets would always be a sunflower.

This is pretty cool! :) What resources did you find most helpful in your learning journey?

How do they definitively know it was used as a musical instrument? It could just have been something punched out on the bone just for fun, by the Neanderthal. Sure, you can make music out of it, but that's not scientific evidence to conclude that someone did use it to make music, is it?

Best thing I clicked today! Love it! I somehow expected "adding your personal message" to generate a level that would trace out my custom message though.

I wish projects like these would mention about the minimum GPU VRAM one needs, for inference or fine-tuning.

Could you go into more detail or provide references on where I could read up more on how banks do this? I've always wondered why we hear a lot about crypto exchanges getting hacked, but seldom about banks. What is it that banks are doing right (or crypto exchanges doing wrong) in terms of security?

The value of legality.

Could you share what resources you used to learn the essentials of WebGL enough to tackle WebGPU?

Do we need to toggle this feature somewhere in the settings? I use KeepassDX but I've never been asked by the app to auto-fill in passwords on websites or other apps.

Are there any constraints on the mapping? If no, then why not map each intensity value to the immediately next value, and then circle it around? For instance, 0 -> 1, 1 -> 2, 2 -> 3, ...., 255 -> 0.

I have a rather silly question - when designing UI features, how do UI designers test whether a design works as expected/is objectively good, and not just "Oh, this looks good to my eyes, others would probably feel the same way too!"? Off the top of my head, I can think of two ways - (i) have a private test audience, show various iterations to them, get feedback, and choose those features with highest scores given by the audience; (ii) get feedback from the end users, and make modifications as necessary. However, I'm guessing (i) is an expensive and time-consuming route, whereas (ii) could potentially lead to poor user experience and be detrimental for user retention. Is there a better way? In short, what's the "unit testing" equivalent in UI design?

Could you tell what resources you found the most helpful for optimising memory in the context of raytracing/rasterisation?

Another splendid resource which I've found to be in the same spirit is Jamis Buck's The Ray Tracer Challenge. It follows a language-agnostic test-driven approach to making a raytracer from scratch.

Thanks a lot for taking the time to list these resources (in this post as well as in the other Ask HN post)! This is really helpful for beginners like me. :)

Could you point me to any open source projects/references you've used for your platform that showcases this plugin architecture? I'm a junior developer and I'd really like to learn and incorporate this in my projects.