danielvinson

5개월 전discuss

This is actually really interesting to me, but the way to determine if you should mulligan is if the 7 cards you are looking at is better than the average 6 cards in your deck. Given that games in most higher power formats end in the first 2-3 turns, the number of cards isn’t as important as the quality generally. So it’s really just math to determine what an “average” hand looks like.

danielvinson

5개월 전discuss

Hmm well, from my perspective, none of them are even really playing the game, they are just taking random actions. Any human, even a small child, would be much better.

And re: ages, it's worth noting that the youngest player to make Day 2 of a Grand Prix is 8 years old, and the youngest Pro Tour winner was 15 years old. I don't think it's realistic to get an LLM anywhere close to either of those players in skill level, though it's absolutely possible with a specialized model.

danielvinson

5개월 전discuss

As a former competitive MtG player this is really exciting to me.

That said, I reviewed a few of the Legacy games (the format I'm most familiar with and also the hardest by far), and the level of play was so low that I don't think any of the results are valid. It's very possible for Legacy they would need some assistance for playing Blue decks, but they seem to not be able to know the most basic of concepts - Who's the beatdown?.

IMO the most important pars of current competitive Magic is mulligans and that's something an LLM should be extremely good at but none of the games I'm seeing had either player starting with less than 7 cards... in my experience about 75% of games in Legacy have at least one player mulligan their opener.

danielvinson

8개월 전discuss

I can't see any movement, at any distance. How likely is it something weird with my vision vs. something weird with my monitor/computer? I'm on a 360hz monitor at 2k.

danielvinson

10개월 전discuss

I agree that maintaining web apps is an entirely different set of skills, though in my experience (mostly small and mid size companies) PMs come in with massive projects and huge changes constantly and management has to say yes to a few. I try my best to shield my devs as much as possible from the politics but usually my teams are still ending up with huge 4-5 sprint frontend projects. It's extremely hard to find devs who can create simple technical designs when there is absolutely any frontend complexity (especially things like wizards, why are wizards so hard for people...). My standard these days for a "good hire" is anyone who can handle these sorts of projects without a huge amount of help.

danielvinson

10개월 전discuss

I think this article discounts the reasons behind frontend decisions... priorities are absolutely fast execution time and ease of hiring. There is very, very little reason to care about optimizing frontend performance for a vast majority of apps. Users just don't care. It doesn't make the company more money.

If a framework is easy to use and everyone knows it, it's simply the best choice for 90%+ of teams.

danielvinson

11년 전discuss

If the past is any indication, Google will have really good support at first for this, similar to how it worked for Glass. Then once the product has been received well by early adopters (and received good publicity), they will layoff/downsize until everyone is unhappy.

comments