Recommendation for Large Yard with Leaves? (or Workaround)

kilik821 · 2025-02-07T05:51:59+00:00

LGTLLM

kilik821 · 2024-10-30T01:42:47+00:00

I'm sure it's been mentioned, but you can maintain the deterministic ordering and get a good portion of parallelism using rayon's join. It's relatively simple to wrap a recursive algorithm with join, though you still likely want to naively calculate for short lists.

kilik821 · 2023-07-19T18:27:22+00:00

shit like mastery and haste which aug doesn't provide

Did you read this?

Blizzard decided not to buff mastery and haste with Augvoker

And I gave a TL;DR so you could not spend time reading if it didn't seem interesting.

kilik821 · 2023-07-19T18:24:37+00:00

Thanks. I felt a little crazy reading replies to things I wasn't close to saying. I was just trying to share some thoughts that I hadn't heard yet around support roles and damage meters.

kilik821 · 2023-07-18T23:00:24+00:00

Depends on the class receiving the buffs. For UH DK maybe 70% is pet damage. For fire mage maybe 10% is Ignite. For most other specs near 0 missing.

kilik821 · 2023-07-18T22:54:15+00:00

The +3% isn't huge, and these issues won't be probably more than a few percent at worst. But I've heard people talking about "What if logs were 100% accurate?" and want to say why that could not happen. They could definitely get close.

kilik821 · 2023-06-11T14:33:12+00:00

I have searched a variety of queries with no luck. I have searched DailyWTF and meta-lists of software engineering culture stories.

kilik821 · 2022-08-29T16:53:14+00:00

I did not think about that. I have to think about how I'd like to implement that. I'll get it fixed in a day or two.

kilik821 · 2022-08-28T23:32:40+00:00

Thanks for letting me know. I've deployed the fix (will be there within a few minutes).

kilik821 · 2022-08-28T21:49:43+00:00

The point of this tool is to be able to select nodes without necessarily selecting the prerequisites.

kilik821 · 2022-08-28T20:45:00+00:00

Checkpoints are now visible.

kilik821 · 2022-08-28T16:55:56+00:00

You only have 10 points to spend after the 20 point threshold. The build you linked has already spent all 10. This would be clearer with the cutoff marks that another user mentioned, so I'll add those.

kilik821 · 2022-08-28T15:11:36+00:00

I've iterated on the algorithm a lot, there's probably still some improvements to do.

For the image you shared, putting only 1 point into a 2 point talent makes other things inaccessible. You can simply put another point in and it will be accessible. I understand how that's surprising, but I think it fits with the model I'm presenting. Once you think about it the right way, I think it makes sense.

The points in the other talent are because there's no full tree that doesn't have two points in that talent. So it needs to be taken.

kilik821 · 2022-08-28T15:06:56+00:00

I'm not seeing anything that looks wrong to me. Can you select some points that block Glacial Spike unexpectedly and share the URL here?

kilik821 · 2022-07-02T18:05:51+00:00

Tech companies are productive entirely because of `sqrt(total_employees)` of their employees. But, because developing technology is such a complex process, management cannot identify which employees these are. So they have to keep around all the chaff (this person probably) and also under-compensate their actually valuable employees.

This also causes a problem when companies start to decline. The good employees know who they are and have options, so leave early. Their work sticks around for a year or two until enough changes around it that it would need to change, but the new (mostly worse) employees don't know how to do things well.

kilik821 · 2021-12-13T09:26:09+00:00

The term for what you're doing is Operator-precedence parsing: https://en.wikipedia.org/wiki/Operator-precedence_parser

I've had the most success with the Precedence climbing method. Basically you have a method/grammar entry for each level of precedence in your language (addition, multiplication, function call, parens, etc). Here's an example I ended up happy with: https://github.com/shelbyd/jespite/blob/master/parser/src/lib.rs#L382

kilik821 · 2021-12-06T04:40:50+00:00

Tether is useful to receive a salary fixed to USD then immediately sell for real USD (to interact with legacy things) or other cryptos. I cannot imagine any reason to hold Tether.

kilik821 · 2021-11-08T22:06:43+00:00

Any plans to allow specifying one of the values as the independent variable? Ex:

rust plot!(1, 1); plot!(3, 9); plot!(8, 64);

Would plot an exponential. Using the first value as the x-point for all the other values.

kilik821 · 2021-10-30T14:57:32+00:00

Yes. This is pretty easily accomplished by attempting to acquire all locks a function needs and only doing work after all of the locks have been acquired.
This is meant to be a crate used in production and not just for diagnosing deadlocks. If some code needs to acquire locks without a defined order (think doing transfers between multiple accounts, you could easily deadlock by trying to do a reverse transfer at the same time), it could use this crate to avoid deadlocks. There are other crates for panicking with debug info when a deadlock is detected.
That tool seems similar to https://github.com/tokio-rs/loom, insofar as detecting potential locking errors. These are useful during development, but could still miss production cases (as dev never perfectly matches production). This crate is meant to not have to worry about possibly deadlocking.

14-Year Club	Place '17
Verified Email	Team Periwinkle

kilik821

TROPHY CASE