Is there a way to control the mechanics of the animation? I poked around a bit and didn't see a way to configure what was sent down the arrows or how often - just some theming options.
For example, if you're visualizing a user flow, you might want rules about when new "objects" are sent down the pipe (example node rule: wait until received one item from each input), or how fast they travel, etc.
75% margin means they have around $79.2bn of potential revenue sitting in inventory. Next quarter revenue is projected to be $65bn, so 110 days of stock.
I don't have an opinion on whether it's correct or not. I see AI writing, I stop reading. When compared to human-authored prose, AI writing is much more likely to be convincing-but-wrong. I don't need to be ingesting stuff engineered to be believable, with correctness only as a secondary concern.
If it's correct, it's usually because a better source has already written it correctly, or because it's trivial to somebody who knows what they're talking about.
AI writing is a sign that the author either doesn't know the material, doesn't want to write it, or both. Because distinguishing "too lazy to write it" and "too stupid to fact-check it properly" is very difficult on my end as a reader, it's better to be safe than sorry. There's no sense in exposing my malleable wetware to slop of unknown provenance.
There has been no shortage of human authors writing about this topic. I don't know who "Philip Pieogger" is, so I have no reason to prefer him as a co-author.
Not 100% sure I understand your comment, but just to make sure my stance is clear - I saw that it was AI-written and noped out. Thought it was a little funny that they used an LLM to write an article about how LLMs are bad.
Self-hosting and bioinformatics are both great use cases for containers, because you want "just let me run this software somebody else wrote," without caring what language it's in, or looking for rpms, etc etc.
If you're e.g: a Java shop, your company already has a deployment strategy for everything you write, so there's not as much pressure to deploy arbitrary things into production.
Sort of. There are some things that a person entering a field is expected to know without needing to look them up, because if you don't know it you won't develop good intuition or be able to execute your work in a timely manner. Most of the stuff you learn in your freshman year is this type of thing, while the later years tend to have more open-book tests.
This is also the kind of thing that you check for in an interview - somebody who needs to look up how to write a for loop isn't going to get hired as a C programmer, and somebody who isn't familiar with Ohm's law will flunk their electronics interview. So there's a very pragmatic reason to make sure that students have the basics memorized.
TL;DR: Disability is not inherent in difference, but rather a combination of the difference and an environment in which that difference is not well-supported. For an analogy - a deep-sea fish is blind, but not disabled by their blindness. Similarly, a kid who "can't sit still" isn't disabled unless we put them in an environment where they have to.
For example, if you're visualizing a user flow, you might want rules about when new "objects" are sent down the pipe (example node rule: wait until received one item from each input), or how fast they travel, etc.
reply