5 ms·
Ending an Ugly Chapter in Chip Design
- ok_dad 4y agoJust wanted to mention this site is cancer for your back button, open it in a new tab.
- dang 4y ago"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- deleted 4y ago[deleted]
- ok_dad 4y agoI get it, I do, and I'm a good boy around here as much as humanly possible, but this ain't no ordinary level of back-button-evil. There were hundreds of back-button edits. It was quite uncommon and interesting, IMO. Thanks for what you do here, too, btw.
- causi 4y agoThe question is, at what point does user-hostile site behavior become more than tangential? Surely if, for example, a page contained malware that would warrant at least a mention in the comments. Personally I appreciated your warning.
- Flockster 4y agoTrue, I did not interact with the page yet (did not scroll, klick or else and uBlock origin activated) and have as of this point 6 back entries in my Firefox-Tab for the page.
- auggierose 4y agoInteresting, this comment appeared collapsed, although I didn't open this topic before. I guess that was an administrative intervention.
- causi 4y agoYep. When that happens without users flagging the comment it doesn't get a [flagged] tag. It's unfortunate, because you can end up temporarily muted from commenting with a history full of nothing but positive-scored unflagged comments and have no idea how you angered the powers-that-be.
- FeepingCreature 4y agoThanks, this comment was very helpful.
- aaron695 4y ago[flagged]
- piyh 4y agooof
- titzer 4y agoIt seems to be quite the contrary to what you state: I hear from female colleagues (professors at CMU no less) all the time that their work is subjected to much greater scrutiny and harsher criticism than work by their male counterparts. To withstand a much greater volume and abrasiveness of attacks, work by women has to be higher quality and nearly unassailable. That the article might have amped up a sexism angle for buzz is one issue, but the underlying dynamic frankly isn't talked about enough. Was it the case here? Hard to know. > I'll assume from this sentence they are imposter women who shouldn't be in computer science. I honestly don't know if you meant that ironically or sarcastically, but holy flippety bippity, we need no such attitudes and certainly no such comments to mess up the culture even more. At all. If you think it's funny or insightful, it isn't.
- rowanG077 4y agoThat's what happens if you allow positive discrimination. People no longer trust the system since someone might have come into a position without being capable. People are forced to start scrutinizing members of the positively discriminated group more.
- titzer 4y agoHaving been a part of many hiring processes, positive discrimination is a complete mirage. Hiring unqualified, below-par candidates for diversity is something that I have never seen happen. Done right, hiring for diversity means better outreach and actively fighting cognitive biases (ironically) like the one you're alluding to, and the OP has gone all-in on. It's an utter fallacy that minority groups are imposters by default.
- causi 4y agoThis dispute has certainly had consequences, most of them negative. There's an enormous amount of relevant details missing from this article and I don't know why. Why is there no response from Kahng to G&M's rebuttal of his experiments? What did G&M say when told their Github posting wasn't reproducible? Did they agree it was a problem or not? Why did G&M leave Google if the person who was personally undermining them was fired? What exactly did Chatterjee do to personally undermine G&M, and why?
- aaa_aaa 4y agoAlso why emphasis that G&M are women? This sounds like creating an unnecessary protectional bias for them.
- causi 4y agoThat's how you get attention in modern times. Marginalized groups are inherently heroic and non-marginalized groups are inherently villainous.
- xbar 4y agoI was immediately thrown into the weeds on that, too. ieee.org's editors are not doing a service to their members by making a chip design argument about AI a gender issue.
- red-iron-pine 4y agoIn 2023 all issues are gender issues. The tangents people, even here at HN, take viz-a-viz these topics, are often mind-boggling. And HN generally has less bot protection than places like reddit, too.
- rubylark 4y agoThe only reasonable explanation I can think of is that Chatterjee's motives and subsequent termination (which is not elaborated on) was related to gender discrimination. Otherwise I can't see what relevance anyone's genders has on the issue at hand.
- deleted 4y ago[deleted]
- ipso_facto 4y agoKahng's group has a FAQ responding to the questions that were raised: https://github.com/TILOS-AI-Institute/MacroPlacement#new-faqs-after-the-release-of-our-ispd-2023-paper-here-and-on-arxiv https://github.com/TILOS-AI-Institute/MacroPlacement#new-faq... The ACM article also has some relevant details: https://cacm.acm.org/news/271439-more-details-but-not-enough/fulltext https://cacm.acm.org/news/271439-more-details-but-not-enough...
- warbaker 4y agoUltimately, what they needed to do was train to convergence, and they didn't do that. They should have made it extremely clear in their original manuscript their CT results are against a non-pretrained version that was not always trained to convergence, and so the CT results presented are a just a lower bound on performance. They got confirmation from a Google engineer on only one block, which they trained for 1 million steps. For the other blocks, they didn't train anywhere close to that many steps, and their tensorboards don't show convergence on total cost. ML is difficult! It's not enough to confirm that your implementation and installation are correct - you also need to train to convergence. You are free to complain that this is onerous or expensive. It's a common problem in academia vs industry in other areas of ML -- ML takes a lot of compute, and academic budgets are extremely tight. That said, CT is still orders of magnitude smaller / cheaper than most modern ML models (not surprising! CT is pretty old at this point by ML standards (3 years is a long time in this field)). Kahng's FAQ admits that pre-training led to a better final proxy cost in the Nature paper, and that it significantly reduced compute time, and that this is the method that the Nature authors recommend and used in their Table 1 evals. This whole situation is such a shame. Prof Kahng wrote a really great article on CT a few years back, and it gave me hope that the whole field was going to embrace ML and really take chip design to the next level: https://www.nature.com/articles/d41586-021-01515-9 https://www.nature.com/articles/d41586-021-01515-9 Most of the field in fact has, but Kahng himself seems to be backsliding here. Unfortunately, I suspect that Kahng's been listening to some pretty toxic people (the same day his paper was posted to arxiv, it appeared in an SB author's court filing). It seems like his group ran into some difficulties jumping into machine learning, and rather than take that as an opportunity to grow and learn, they took that as an opportunity to attack. While I'm glad that others in the field have built on the work successfully (see Appendix of https://www.annagoldie.com/home/statement https://www.annagoldie.com/home/statement ), it would be really tragic for Kahng himself to get left behind here, and so so unnecessary!
- warbaker 4y agoStatement from the Nature authors on this: https://www.annagoldie.com/home/statement https://www.annagoldie.com/home/statement