mwt

10 ms·

31.
by mwt 4y ago
Your explanation doesn't really distinguish high-level human play (not obvious cheating) from engine play (obvious cheating). There are probably plenty of games in which your first 20 moves (or 5-10 for me) are in GM databases and eva
32.
by mwt 4y ago
I see a lot of comments about the general topic, but none on the actual tool, which appears to have no (public-facing) updates in about three years. Presumably it could be a tool that incrementally improves over time with the explosion of d
33.
by mwt 4y ago
What time controls do you play? Cheating is much more prevalent in rapid than blitz, with correspondence probably being the worst of all. It's unlucky for people who don't like speed chess. The only solution to this problem I&#x27
34.
by mwt 4y ago
I'm not a lawyer or a smart individual but oh boy that's a red flag, just like several other details you offered. With the information available, it sure seems like that's a dependency that should never be brought into a proj
35.
by mwt 4y ago
What was the license of this package?
36.
by mwt 4y ago
I was also surprised to learn (years ago) BuzzFeed has a decently-sized investigative team
37.
by mwt 4y ago
That's not what motivates me, thanks, but it's clearly what motivates the industry
38.
by mwt 4y ago
I've never worked somewhere in which mentorship was formalized *and* something for which there was a clear relationship to promotion. Not saying that the only way to get me more into it is by paying me or threatening compensation, but
39.
by mwt 4y ago
I don't doubt there's some people like this, but if I cut my teeth on mainframes 2-3 decades ago and was nearing retirement, I'm not sure I'd have the patience needed to be a good mentor. (I'm sure I *should*, but a
40.
by mwt 4y ago
There's also an issue of community/people you'd work with. (Fair or not) there's a strong perception that the current COBOL devs are people that are close to retirement and not exactly eager to take a junior dev under th
41.
by mwt 4y ago
Outside the context of crime: loitering, yes, foot traffic, not really. It's possible this particular phrase is a euphemism used in crime reporting, I don't know, but if it is I don't know why they wouldn't just say &qu
42.
by mwt 4y ago
I'm with you, but I wonder if this is the sort of "only people on this site care and the vast majority of the readership wouldn't use it" thing ... I'm not sure it is, but it could be, and I wonder if somebody with
43.
by mwt 4y ago
You might be right but that isn't even what I'm saying here. Your description could apply to many sectors of the economy, most of which they have a some amount of presence in
44.
by mwt 4y ago
That is the design: business units that are not viable on their own are subsidized by a few cash cows but might gain market share and be profitable in the future
45.
by mwt 4y ago
I don't see any analysis?
46.
by mwt 4y ago
Folding@home would love to take a swing at a sliver of that compute
47.
by mwt 4y ago
Worth pointing out that this is dated Feb 22, 2022, when things in this space were a bit different.
48.
by mwt 4y ago
If this sort of thing was effective (and legal, I don't know) you'd think it would be seen regularly. I can't decide if it's better explained by the power of corporate(/political) PR or simply that people don't
49.
by mwt 4y ago
Are they adding costs? The baseline of ~3% to wire money seems already high.
50.
by mwt 4y ago
I'm pretty much listing off the subheaders, none of which I dispute nor seem to be disputed by the general consensus. What is still unclear, however, is how to draw an arrow from "I love working here" to "the product is
51.
by mwt 4y ago
What obvious truth is acknowledged here? - They pay extremely well and offer great benefits to their engineers. - They (not coincidentally) are able to hire great talent. - That their platforms offer as much reach as any other company None
52.
by mwt 4y ago
And on your blog you can choose to use common abbreviations like OS, BIOS, and GPS without spelling them out.
53.
by mwt 4y ago
It's pretty clearly automation gone wrong. I didn't specify if it's a matter of neglect or abuse.
54.
by mwt 4y ago
_They_ didn't _do_ it per se, it was done by a third party (probably for hire) and it seems to have been the result of automation gone wrong (not an excuse IMHO). Of course they bear responsibility for the work they contract out and t
55.
by mwt 4y ago
> You mean the entire developer's thought process behind a change will be represented by a single 12x16 picture? No, look at the log of FastAPI (or even gitmoji itself: https://github.com/carloscuesta/gitmoji )
56.
by mwt 4y ago
Honest question, do you really expect your history to be meaningful long-term? Or are you simply taking the approach that the commit message is meaningless and a developer instead use GitHub search to find a PR relevant to a change they&#x2
57.
by mwt 4y ago
Yeah, I mean my comment more as a criticism of universally squash-merging as a policy since, not so much an endorsement of it in general. I run into cases like you describe pretty often, and I doubt I'm alone. Switching to squash-mer
58.
by mwt 4y ago
> github's naive view of history where it shows things in a bafflingly obtuse linear This hits home, it pretty much describes how I visualize logs in my head (compared to the visualizations I see that are more 2-D, branching off and
59.
by mwt 4y ago
Yep, `--allow-empty` is my preferred solution. It's unfortunately not up to me how other people choose to do this
60.
by mwt 4y ago
This is from 2014, but I guess not much has changed since then.

More ›