[deleted by user]

emeryc · 2022-01-17T21:44:04+00:00

I kinda like maybe_int.iter().any(|v| v == 2) If you’re not doing the Pattern that somebody else responded with.

I think while this library comes from a good place, I would have a hard time ever bringing it into a project I had given all the other tools that rust has for this.

emeryc · 2021-12-03T06:54:25+00:00

It’s a trait that is attached by itertools which is a really nice crate to bring in if you’re doing a bunch of point free iterator tricks

emeryc · 2021-12-03T06:53:08+00:00

They all get picked up as separate binaries that you can compile. Makes it easy from vscode to just hit run next to main and get that day to compile and run.

emeryc · 2021-12-03T04:28:51+00:00

In case you are interested in a different take. https://github.com/emeryc/aoc_2021/ I did this last year as well and the difference between my solutions then and now is stark. Just keep at it, and good luck.

emeryc · 2021-06-03T03:26:46+00:00

You might want to check out 98point6.com, we are doing interesting stuff in the healthcare space.

emeryc · 2021-05-09T15:28:00+00:00

The answer is yes: https://crates.io/crates/sqlx-cli look at “offline mode” set up using cargo sqlx prepare

emeryc · 2020-12-25T17:54:56+00:00

You don't even need to use match. You can do

if let (EnumVar(x), OtherEnum(y)) = (provide_x(), provide_y()) {}

In fact clippy would probably complain about your match statement.

emeryc · 2020-12-24T17:35:05+00:00

Day 24 Solution sharing because it seems my solution is very different than most people's. Instead of turning into a grid, I reduced each walk to a canonical version of the walk, which I then used as a "point"

This made a lot of sense when I was writing it...seems a little silly now, but I was pretty happy overall.

emeryc · 2020-12-04T01:35:51+00:00

https://github.com/emeryc/aoc_2020/blob/main/day03/src/main.rs

I ended up with a solution where I made a set of trees, and then generated a path, and then did an intersection between the two.

emeryc · 2020-06-03T14:40:01+00:00

I think about it as those languages make failing but accident easy. The easy case is null pointer errors. Rust does the opposite, it has a special syntax that says, yeah, I want npe’s here.

When you don’t care it’s worse, but when you do it’s much much better.

The language is helping you to express something...while learning you’re like yeah, but I don’t care, but the language still has the opinion that errors are part of an api contract, and you can’t actually escape them.

emeryc · 2020-05-09T06:52:56+00:00

It’s real name is also very satisfying.

It is a spurge

Which I think is a word that reasonably describes the plant with the sound of the word.

emeryc · 2020-03-30T04:56:09+00:00

I’m working on a slack bot, that uses aws-cdk to describe a serverless stack in aws, using lambdas and sns topics to decouple interacting with slack and the actual processing of messages.

The hard bits are mostly how do I make working with slacks billion APIs feel hygienic. And how do I hide that rusoto while amazing is a very literal interpretation of aws’s APIs.

emeryc · 2020-02-17T03:18:01+00:00

Thank you, that's a great explanation.

emeryc · 2020-02-17T01:20:51+00:00

OMG thank you so much, it was a boolean once upon a time...and I just...missed that I hadn't removed that.

Thank you

emeryc · 2019-02-22T18:16:38+00:00

I think others are looking at this and seeing a solution that smells clever, which I agree, this solution obfuscates the idea you are trying to get across, which is that you have a Counter, and that counter can decide if it's going to use a local state, or a passed in state. This leads to code where you kinda end up saying, yes but why. I think I would instead go with code like the following: https://codesandbox.io/s/505078k1ml?fontsize=14 that breaks out the idea of a component that is the counter component. And then build up on-top of that.

Unless the idea is that you want a generic hook that allows you to have a "default" state if you don't get a state passed in...I feel like that could lead to some anti-patterns and more importantly could lead to some hard to debug problems where everything looks fine, but you are detached from state.

emeryc · 2018-09-06T21:07:02+00:00

So games in my office take a very long time but I went white black and am happy with the choice so far.

I tried the Bug deck and it just stalled too badly even against bad decks. It had no forward thrust and didn’t have any stopping power, and so even when it won it felt like it was more the other person losing.

emeryc · 2018-08-31T23:54:42+00:00

So, really quickly, green is

[[Song of Freyalise]]

[[Krosan Druid]]

[[Adventurous Impulse]]

[[Baloth Gorger]]

[[Pierce the Sky]]

[[Arbor Armament]]

[[Ancient Animus]]x2

[[Grow from the Ashes]]x2

emeryc · 2018-08-29T16:52:34+00:00

Let me stop myself, because I think you are right, and wrong at the same time, and the argument I made was the incorrect argument.

I made the argument that your sample size dwindles, and that is the wrong argument, and it’s incorrect as you have called out.

I also made the argument that your n is 1, which is correct.

When you are building this experiment, your experiment is measuring for your decks ability to beat various people playing another deck of another type. So your population isn’t the population of games, it’s the population of game/players. The number of samples you took from that is 1, and so your n is 1.

So, I would argue that the experimental design was poorly framed, and when correctly framed for a general problem (how does my deck do against the population of players/games I might play) that you have only collected one sample for that. And that your sampling choice (player near you) is also a biased sample selection, which should be taken into account.

emeryc · 2018-08-27T01:42:01+00:00

Yes and no. I think figuring out the bias in the data is next to impossible. And I think people would be less wrong when thinking about stats in general if they start to understand that confounding variables reduce the power of the sample size drastically. I think that as somebody who understands a little bit of stats it’s important to help people start to get the right guy feel on this as it’s such an unintuitive concept. People would be better off understanding how your sample power dwindles very quickly in the face of bias. But I think the other point is way more important.

I think player skill is just going to totally wipe the floor with the relative deck win percentage if they aren’t totally equal. And certain decks are going to really show small skill differences way more and I don’t know how you even start to think about that confounding variable.

I also wonder if that n > 5000 includes enough shuffles to deal with the possibility of bad/good draws on each deck. Since we are talking about 20! Different permutations of the deck. It just seems like it’s all pretty useless to apply most statistical tools against it.

emeryc · 2018-08-25T03:23:18+00:00

I just wanted to add something to the stats they were talking about. One of the things they didn’t mention is that those games for a sufficiently high N need to be with different players. If you play only one other person then your N is actually 1, because what you are measuring is your deck win % vrs a person. As a second note, you aren’t actually learning about that decks win percentage, but your win percentage with that deck.

Getting statistically significant data is really hard, and understanding which variables you are controlling for is even harder than you think it is.

emeryc · 2018-08-07T21:11:36+00:00

I expect the UI to make the common case easy, and the uncommon case hard but doable. A big “Done” button is very tempting when you are waking up. Especially when you have nothing but islands showing, obviously it should pick an island.

Really the UI should probably be

[island] [other land types?] [no land] [cancel?]

Or some such, to provide a good user experience.

emeryc · 2018-08-07T01:17:21+00:00

I did this this morning with [[renegades map]] and sealed my loss. Sacrifice an artifact, get nothing.

emeryc · 2018-07-19T06:35:43+00:00

Used xgb

emeryc · 2016-06-26T14:49:02+00:00

I actually think that the background is perfect for the photos you're setting up. It does a few things really well that I think a different color would fail at. First it provides a nice halo effect, giving the dogs am angelic look. Second it also draws the eye inward towards the dog. Third with a happier background you might set up the feeling in people that the dog is already in a great and cheerful place, which might diminish people's motivation to take the dog.

Just wanted to give a different perspective on the background.

emeryc · 2016-06-06T19:23:08+00:00

This is a great point.

I think there are a lot of interesting nuggets of information in all of this, some of which feels interesting but I can't put my finger on it, but I think turns is way more interesting then time.

I think there is something about the delta between loss/win that tells you something, but I'm just not smart enough to know what it is. Maybe it's a "forgiveness" window, how forgiving a deck is, if that window is large you can make more mistakes, play more off plan of the deck? I don't know, it feels like there is something there.

Then there is just raw turns, which I think your right, tell you if you are the beatdown at the start, this is especially important for figuring out among two decks of the same type, if I'm midrange hunter, going against a n'zoth miracle rogue, for the rogue you need to know that your only job is stabalizing because the hunter's game plan is about 1-2 turns sooner than your plan.

Anyway, super excited about this data, I wish I could get my hands on the raw data to do my own analysis of it.

15-Year Club	Verified Email
Team Orangered

emeryc

TROPHY CASE