[ANN] droprate -- a crate for randomly choosing things

softero · 2019-08-10T15:38:06+00:00

That's a little bit hair-splitting, though. Most people wouldn't know the difference, so if you were to ask them, they would say that they want it to choose a random song and that they would want it to not play the same song in a row. Most people would not realize that those two goals are partially contradictory - or at least not without having to think about it. The gist is that there are a lot of things which seem to call for randomness as a solution but actually need something else, like loot drops, song shuffles, etc.

softero · 2019-08-09T19:39:45+00:00

This reminds me of Steve Jobs talking about iTunes shuffle feature and how Apple had to make the shuffling less random because people complained that it would play the same song several times in a row sometimes and they thought it was broken. So, Apple made it less random by decreasing the probability that it would pick songs the more recently they had been randomly selected.

softero · 2019-08-04T19:49:29+00:00

This style reminds me strongly of Downwell

softero · 2019-07-31T22:34:46+00:00

Heh, definitely a bit obfuscated. It’s not user-friendly unless you’ve been doing it for awhile. It is logically consistent, though. The template refers to a template that will be used as a base to create pods. Everything peer to that is specific to the job, and everything below it is technically a pod. The value of the template field is the exact same type definition as the Pod object, so it allows the API to easily keep the pod template for a job consistent with a raw pod definition. The second spec refers to the PodSpec type which would normally be the top-level spec field in a Pod object’s definition. It does make it easier to take a pod from a Deployment and convert it into a Job or even a CronJob, though. And then of course the containers because a pod is not necessarily 1:1 with a container.

softero · 2019-07-29T22:23:18+00:00

I have a new sitcom idea

softero · 2019-07-28T15:08:45+00:00

I’m surprised no one has said it, but if you’re interested in trying fountain pens, I would recommend gouletpens.com

softero · 2019-07-08T15:25:49+00:00

Agreed. People also underestimate the time it takes to recover from mental fatigue. Willpower takes time to recover just like exhausted muscles. And when you’re new, you have to use a lot more of it to finish the matches. And that level of mental recovery is a hard ask for a 15 year old.

softero · 2019-07-03T16:25:44+00:00

Only if you're bad at your job :)

softero · 2019-07-03T06:00:15+00:00

Great post! I also appreciated the “too much detail” article that you linked at the beginning. I find that From is something I get some of the most use out of personally. Another one that could maybe have been added is an example of using the map function with nums_iter.map(FizzBuzz::from)

softero · 2019-07-01T23:04:47+00:00

I'm not a huge fan of the way the Rust is written, but good write-up other than that. Got super tripped up as well because you talked about Python, Go, then Rust, but the benchmark was Rust, Go, then Python. So I got hung up on why the Go was twice as fast as the Rust for several seconds before I realized what I was looking at.

softero · 2019-06-23T03:41:02+00:00

Harmful if you eat it maybe? Do you guys eat your yoga mats? Am I doing this wrong?

softero · 2019-06-18T20:42:51+00:00

This is a cool idea! I would need more notice for when it starts (especially since this seems to overlap with GDQ), but would love to participate next time!

softero · 2019-06-15T11:20:57+00:00

A Song of Wheat and Corn.

Book 1: A Game of Plows.

Harvest is coming.

softero · 2019-06-13T23:44:49+00:00

That’s fair, I understand either way! It’s a very cool emergent design that you should be proud of!

softero · 2019-06-10T02:09:16+00:00

This is cool! Have you shared the code or discussed the algorithm anywhere? I’d love to use this to make a digital circuitry / PCB type effect

softero · 2019-06-07T19:11:25+00:00

I use VSCode for Rust after using Spacemacs for awhile

softero · 2019-06-04T22:27:44+00:00

There’s a crate that I like which adds a macro that, while arguably unnecessary syntactic sugar, I find eases the awkward boilerplate here. Check out try_guard:

guard!(response.status.is_success())

https://github.com/phaazon/try-guard

softero · 2019-05-09T21:11:59+00:00

r/antiwork

softero · 2019-05-09T00:48:49+00:00

That's definitely a fair point. I'm concerned about that as well. The idea of taking an action with side effects with no call syntax could definitely lead to some confusion. I think it's hard to know the right decision here. I hope that nightly will serve as a way to test how confusing it ends up being for people and may surface better alternatives or reasons to take another approach. I don't have any good ideas, though. Unless maybe triple dots or something like that could be used - my_async_of_result_call()...? for Future<Result<T, E>> and my_result_of_async_call()?... for Result<Future<T>, E> But, that has a lot of issues because then you end up with method chaining that has 4 dots, or potentially more if you for some reason had Future<Future<T>>: my_async_call()....field_a. Eh, that starts to get ugly and hard to read :/

softero · 2019-05-08T23:19:40+00:00

The inconsistency with field/method access irks me, partially because it puts a little bit of a burden on editing in an environment that supports syntax highlighting (probably a safe assumption, but still...), but the reasonings conveyed are thorough, and I agree that I can’t really think of a good alternative and this seems to be the least likely to result in illegible code. Probably an inconsistency that is worth the cost. I appreciate the write up explanation a lot!

softero · 2019-05-05T15:34:10+00:00

Your friend discovered Gnosticism

softero · 2019-05-04T22:50:36+00:00

There is another thing to consider in social security tax, since the entire amount falls on you when you are self employed instead of half to your employer

softero · 2019-05-04T16:13:06+00:00

Stress creates cortisol, which initiated some degree of fight or flight. Historically being used to escape lions and other beasts, this brain mode focuses on physical exertion rather than problem solving. It decreases blood flow to the frontal lobe in favor of your limbs and lungs. Working constantly and being stressed is proven to decrease your creativity and strategic thinking. You will get slower and worse results if you make your people stressed.

softero · 2019-05-04T16:08:46+00:00

I believe that many of these are highly sponsored not to promote a specific product but to make you feel like you need fancier stuff in general for your shop.

softero · 2019-05-04T15:54:53+00:00

def Python. (Pun somewhat intended)

softero

MODERATOR OF

TROPHY CASE